Observed topology
AS51178 AVANTEL-SPB-AS St.Petersburg branch
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS51178: 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 |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 146 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 113 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 94 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 81 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 80 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 71 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 71 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 36 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 28 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS51178 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204891 | LLC Crystal Service Integration | Unclassified | IPv4 | 85 |
| AS59399 | FAI Russian Maritime Register of Shipping | Unclassified | IPv4 | 69 |
| AS202537 | Feniks JSC | Unclassified | IPv4 | 47 |
| AS204272 | ASARTA LLC | Unclassified | IPv4 IPv6 | 47 |
| AS210787 | CDEK-Global LLC | Unclassified | IPv4 | 39 |
| AS202082 | LLC ILOT | Unclassified | IPv4 | 35 |
| AS197303 | OCS Group Limited | Unclassified | IPv4 | 29 |
| AS62330 | ASH Ltd | Unclassified | IPv4 | 27 |
| AS203597 | STEK LLC | Unclassified | IPv4 IPv6 | 27 |
| AS199072 | "Center of Computor Research" JSC | Unclassified | IPv4 IPv6 | 25 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51178 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 252 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 212 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 157 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 144 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 137 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 89 |
| AS204891 | LLC Crystal Service Integration | Unclassified | IPv4 | 85 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 81 |
| AS59399 | FAI Russian Maritime Register of Shipping | Unclassified | IPv4 | 69 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.