asn.dev

Observed topology

AS400687 SOLYTRO-LTD - Solytro LTD

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS400687: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6153
AS174Cogent Communications, LLCTransitIPv459
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv656
AS3257GTT Communications Inc.TransitIPv4 IPv647
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS1403EBOXResidentialIPv4 IPv610
AS22652Videotron LteeResidentialIPv4 IPv68
AS5511Orange S.A.TransitIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215853Bonfortuna LtdUnclassifiedIPv4275
AS51582Cifrova Kabelna Korporacia EOODResidentialIPv499

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6509
AS215853Bonfortuna LtdUnclassifiedIPv4275
AS51582Cifrova Kabelna Korporacia EOODResidentialIPv499
AS174Cogent Communications, LLCTransitIPv459
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv656
AS3257GTT Communications Inc.TransitIPv4 IPv647
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS5511Orange S.A.TransitIPv4 IPv623
AS1403EBOXResidentialIPv4 IPv610
AS22652Videotron LteeResidentialIPv4 IPv68

All 13 adjacent →

Provenance

Where this comes from

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