HI3G Access AB
Hi3G Access AB
Data as of 2026-07-26
GLEIF verified
LEI
5493008U77SYPDCUTJ48
Registered name
HI3G Access AB
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 37 · 1,007,628 IPv4 addresses |
| IPv6 | 15 prefixes (largest 2a02:aa0::/29) |
| Registered in | Sweden (29) · Denmark (2) · Netherlands (1) |
| Cluster ID | 213663883 |
| Registry | BGP |
| Owner jurisdiction | SE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 5493008U77SYPDCUTJ48 |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
48
0 netblocks since 2026-07-05
2026-07-05
peak 48
2026-07-26
IP Ranges (37)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2.64.0.0/13 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 37.250.0.0/16 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 77.241.128.0/20 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 78.156.192.0/19 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 79.138.128.0/17 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 80.249.210.213/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 80.251.192.0/20 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 94.191.128.0/17 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 95.209.0.0/16 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 109.56.0.0/14 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 185.1.88.41/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 185.1.215.29/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 192.38.7.89/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 192.38.7.90/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 192.121.80.231/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 193.110.12.138/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 193.110.13.138/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.166/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 194.68.128.166/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 212.27.0.0/19 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 212.237.192.166/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 212.237.193.166/32 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a504:4034:1/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:fe::166/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::166/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:202::166/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:203::166/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1f:0:4:4034:89:0/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1f:0:4:4034:90:0/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:21:9::138/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:21:10::138/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:3e:0:a500:4:4034:1/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b0::4:4034:1/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:117::4:4034:1/128 | Hi3G Access AB | PEERINGDB | ASSIGNED | ● high |
| 2a02:aa0::/30 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 2a02:aa0::/29 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
| 2a02:aa4::/30 | Hi3G Access AB | BGP | ANNOUNCED | ● high |
IPv6 ranges (15)
Domains hosted in this network
what's this?Network trust
what's this?
RPKI hygiene: C
how networks compare →
79.2%
of checked blocks have valid RPKI ROA coverage
(38 of 48)
No discrepancies found among checked blocks.
NIC Handles
AS44034
AS44034
DUMY-RIPE
DUMY-RIPE
HI3GACCESS-MNT
HI3GACCESS-MNT
ORG-HAA1-RIPE
RIPE-NCC-HM-MNT