a-net Liberec s.r.o.
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 15 · 5,121 IPv4 addresses |
| IPv6 | 12 prefixes (largest 2a06:8080::/29) |
| Cluster ID | 213590555 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 9 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
18
0 netblocks since 2026-07-05
2026-07-05
peak 18
2026-07-26
IP Ranges (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.201.16.0/20 | a-net Liberec s.r.o. | BGP | ANNOUNCED | ● high |
| 91.210.16.176/32 | a-net Liberec | PEERINGDB | ASSIGNED | ● high |
| 185.185.128.0/22 | a-net Liberec s.r.o. | BGP | ANNOUNCED | ● high |
| 2001:7f8:14::9a:1/128 | a-net Liberec | PEERINGDB | ASSIGNED | ● high |
| 2a06:8080::/29 | a-net Liberec s.r.o. | BGP | ANNOUNCED | ● high |
| 2a06:8084::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:1000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:2000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:4000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:5000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:6000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:a000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:b000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8084:c000::/36 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a06:8085::/32 | a-net Liberec s.r.o. | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (12)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
Possible discrepancies (12)
These blocks are registered to a-net Liberec s.r.o. but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a06:8080::/29 /29 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8080::/29 /29 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8085::/32 /32 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:1000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:2000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:4000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:5000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:6000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:a000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:b000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
| 2a06:8084:c000::/36 /36 | authorized for AS5588 — T-Mobile Czech Republic a.s. |
NIC Handles
AS31349
AS31349
DUMY-RIPE
DUMY-RIPE
GTSCZ-MNT
MNT-ANETLB
MNT-ANETLB
ORG-aLs1-RIPE
RIPE-NCC-HM-MNT