Observed topology
AS56534 COMFORTEL Comfortel, St.Petersburg, Russia
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS56534: 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 |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 1,579 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,204 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 539 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 459 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 288 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 74 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 70 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 68 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 68 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 67 |
Transit
Downstream networks
Networks for which AS56534 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209367 | LLC HAPOTELE | Unclassified | IPv4 | 1,199 |
| AS57010 | IT House, Ltd | Unclassified | IPv4 IPv6 | 427 |
| AS47441 | Comfortel Ltd. | Residential | IPv4 | 300 |
| AS52007 | LLC AdRiver | Hosting | IPv4 IPv6 | 296 |
| AS201848 | Trader soft LLC | Unclassified | IPv4 IPv6 | 291 |
| AS201738 | UFO TECHNOLOGIES LIMITED | Unclassified | IPv4 | 240 |
| AS51783 | The Center of Dedicated Servers LLC | Unclassified | IPv4 IPv6 | 183 |
| AS212165 | Alex Group LLC | Unclassified | IPv4 | 180 |
| AS211892 | WaveAccess Nordics ApS | Unclassified | IPv4 IPv6 | 122 |
| AS202689 | Baltiyskiy Lizing LLC | Unclassified | IPv4 | 119 |
Adjacency
Adjacent networks
Every AS seen directly next to AS56534 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 4,357 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 2,309 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 1,201 |
| AS209367 | LLC HAPOTELE | Unclassified | IPv4 | 1,200 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,015 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 620 |
| AS57010 | IT House, Ltd | Unclassified | IPv4 IPv6 | 427 |
| AS47441 | Comfortel Ltd. | Residential | IPv4 | 300 |
| AS52007 | LLC AdRiver | Hosting | IPv4 IPv6 | 296 |
| AS201848 | Trader soft LLC | Unclassified | IPv4 IPv6 | 291 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.