Observed topology
AS212024 RISSON Marc Schmitt
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS212024: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6206 | Netrouting B.V. | Hosting | IPv4 IPv6 | 91 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 8 |
| AS12859 | BIT BV | Hosting | IPv4 IPv6 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 3 |
| AS44393 | Securebit AG | Unclassified | IPv4 IPv6 | 3 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv6 | 2 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv6 | 2 |
| AS56662 | Marcin Gondek | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS212024 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7552 | Viettel Group | Mobile | IPv4 IPv6 | 3,903 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 IPv6 | 2,826 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 1,296 |
| AS18403 | FPT Telecom Company | Residential | IPv4 IPv6 | 808 |
| AS8881 | 1&1 Versatel GmbH | Residential | IPv4 IPv6 | 620 |
| AS8764 | Telia Lietuva, AB | Residential | IPv4 IPv6 | 612 |
| AS9381 | HKBN Enterprise Solutions HK Limited | Hosting | IPv4 | 515 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 458 |
| AS8560 | IONOS SE | Hosting | IPv4 IPv6 | 436 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 397 |
Adjacency
Adjacent networks
Every AS seen directly next to AS212024 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44393 | Securebit AG | Unclassified | IPv4 IPv6 | 120,343 |
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 5,262 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 5,230 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 IPv6 | 4,838 |
| AS7552 | Viettel Group | Mobile | IPv4 IPv6 | 4,768 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 IPv6 | 4,763 |
| AS4651 | National Telecom Public Company Limited | Unclassified | IPv4 IPv6 | 4,731 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 IPv6 | 4,475 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 4,241 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 3,158 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.