Observed topology
AS202425 INT-NETWORK IP Volume inc
Unclassified Spamhaus ASN-DROP RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS202425: 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 |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 991 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 776 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 331 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 222 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 56 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 56 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 56 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 56 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 55 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 55 |
Transit
Downstream networks
Networks for which AS202425 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS210848 | Telkom Internet LTD | Unclassified | IPv4 | 545 |
| AS140057 | IPv4 Superhub Limited | Unclassified | IPv4 | 183 |
| AS215206 | KHOMUTOV ARTEM SERGEEVICH | Unclassified | IPv4 IPv6 | 159 |
| AS60387 | FATCAT NETWORK S.A. | Unclassified | IPv4 | 80 |
| AS204708 | ANGEL CLOUD LIMITED | Unclassified | IPv4 | 62 |
| AS200195 | Verasel, Inc. | Unclassified | IPv4 | 61 |
| AS207616 | Altrosky Technology Ltd. | Hosting | IPv4 | 61 |
| AS211486 | Alferov Aleksey Aleksandrovich | Unclassified | IPv4 | 61 |
| AS213388 | IIC RAIL LIMITED | Unclassified | IPv4 | 61 |
| AS215402 | Asadov Ruslan Rafaelevich | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS202425 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 1,581 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,203 |
| AS210848 | Telkom Internet LTD | Unclassified | IPv4 | 545 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 533 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 397 |
| AS140057 | IPv4 Superhub Limited | Unclassified | IPv4 | 183 |
| AS215206 | KHOMUTOV ARTEM SERGEEVICH | Unclassified | IPv4 IPv6 | 159 |
| AS57717 | FiberXpress BV | Unclassified | IPv4 IPv6 | 126 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 97 |
| AS5511 | Orange S.A. | Transit | IPv4 | 94 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.