Observed topology
AS8728 Infonet
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS8728: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 188 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 84 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 61 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 7 |
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 | 6 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 6 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 6 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 6 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS8728 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207408 | servinga GmbH | Unclassified | IPv4 IPv6 | 211 |
| AS210671 | Virtuaalinfra OU | Unclassified | IPv4 IPv6 | 210 |
| AS214719 | LLC DZHIBIEN HOST | Unclassified | IPv4 IPv6 | 208 |
| AS61307 | AS STV | Residential | IPv4 | 190 |
| AS207872 | OU CSC Telecom Estonia | Unclassified | IPv4 | 54 |
| AS211494 | Narayana OU | Unclassified | IPv4 IPv6 | 42 |
| AS51103 | EDS SYSTEMS OU | Unclassified | IPv6 | 37 |
| AS205950 | INFONET DC OY | Unclassified | IPv6 | 37 |
| AS208440 | GmhostGrupp OU | Unclassified | IPv6 | 36 |
| AS25152 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv6 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8728 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 557 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 446 |
| AS207408 | servinga GmbH | Unclassified | IPv4 IPv6 | 211 |
| AS210671 | Virtuaalinfra OU | Unclassified | IPv4 IPv6 | 210 |
| AS214719 | LLC DZHIBIEN HOST | Unclassified | IPv4 IPv6 | 208 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 201 |
| AS61307 | AS STV | Residential | IPv4 | 190 |
| AS207872 | OU CSC Telecom Estonia | Unclassified | IPv4 | 54 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 52 |
| AS211494 | Narayana OU | Unclassified | IPv4 IPv6 | 42 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.