TELEPORT-MAGDEBURG-NET
Data as of 2026-09-20
BGP inherited
This organisation
| Netblocks | 13 |
| IPv6 | 6 prefixes (largest 2003:100:8024::/48) |
| Record ID | 241084591 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (13)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.155.143.152/29 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 87.129.239.216/29 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 87.130.48.48/29 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 91.26.227.64/28 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 93.240.233.56/29 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 93.240.254.136/29 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 217.239.193.128/29 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED PA | ● low |
| 2003:61:52::/48 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:c9:b818::/48 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:c9:b82d::/48 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:dd:8813::/48 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:100:8024::/48 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:103:4817::/48 | TELEPORT-MAGDEBURG-NET | RIPE | ASSIGNED | ● low |
IPv6 ranges (6)
Footprint over time
13 weekly snapshots · JSON
13
0 netblocks since 2026-07-05
2026-07-05
peak 13
2026-09-20
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(13 of 13)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE