asn.dev

Observed topology

AS8285 Versija SIA

Hosting RIPE

Upstreams 3 carry this network
Downstreams 9 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 6
Upstream graph Who carries AS8285, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS8285 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8285: 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.

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6762
AS174Cogent Communications, LLCTransitIPv4 IPv6286
AS12578SIA TetResidentialIPv4 IPv6254

Transit

Downstream networks

inferred

Networks for which AS8285 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS56971CGI GLOBAL LIMITEDHostingIPv4 IPv61,902
AS41745Ilia BaikovUnclassifiedIPv4812
AS50053Anton LevinUnclassifiedIPv4 IPv6616
AS199152Virtual Data Center IncUnclassifiedIPv4 IPv6612
AS211273FZCOUnclassifiedIPv4294
AS43162SkyGroup SIAUnclassifiedIPv459
AS51763IntechSystems SIAUnclassifiedIPv457
AS51548SIA "DOLPHNET"ResidentialIPv426
AS210817Carmine Red IT, SIAUnclassifiedIPv45

Adjacency

Adjacent networks

All 13

Every AS seen directly next to AS8285 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv62,856
AS9002RETN LimitedUnclassifiedIPv4 IPv62,520
AS56971CGI GLOBAL LIMITEDHostingIPv4 IPv61,929
AS199152Virtual Data Center IncUnclassifiedIPv4 IPv61,926
AS12578SIA TetResidentialIPv4 IPv61,611
AS41745Ilia BaikovUnclassifiedIPv4812
AS50053Anton LevinUnclassifiedIPv4 IPv6616
AS211273FZCOUnclassifiedIPv4294
AS6939Hurricane Electric LLCTransitIPv4156
AS43162SkyGroup SIAUnclassifiedIPv459

All 13 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.