asn.dev

Observed topology

AS1100 NUDAY

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS1100: 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
AS6461Zayo BandwidthTransitIPv4 IPv6609
AS1299Arelion Sweden ABTransitIPv4 IPv6473
AS6939Hurricane Electric LLCTransitIPv4 IPv6331
AS174Cogent Communications, LLCTransitIPv4 IPv6328
AS3257GTT Communications Inc.TransitIPv4 IPv6250
AS22652Videotron LteeResidentialIPv4 IPv675
AS24482SG.GSHostingIPv4 IPv640
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv640
AS1403EBOXResidentialIPv610
AS20473The Constant Company, LLCHostingIPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS399275Solid Systems LLCUnclassifiedIPv4 IPv6147
AS393612Tamilsoft CorporationUnclassifiedIPv457
AS25948Datablocks, IncHostingIPv47

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6650
AS1299Arelion Sweden ABTransitIPv4 IPv6531
AS6939Hurricane Electric LLCTransitIPv4 IPv6366
AS174Cogent Communications, LLCTransitIPv4 IPv6361
AS3257GTT Communications Inc.TransitIPv4 IPv6276
AS399275Solid Systems LLCUnclassifiedIPv4 IPv6147
AS22652Videotron LteeResidentialIPv4 IPv682
AS393612Tamilsoft CorporationUnclassifiedIPv457
AS24482SG.GSHostingIPv4 IPv644
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv644

All 13 adjacent →

Provenance

Where this comes from

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