asn.dev

Observed topology

AS400810 BREEZETECH

Unclassified ARIN Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS400810: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6692
AS46475Limestone Networks, Inc.HostingIPv4662
AS13335Cloudflare, Inc.HostingIPv4282
AS30456Cosmic Global NetworksUnclassifiedIPv4160
AS2914NTT America, Inc.TransitIPv4104
AS6939Hurricane Electric LLCTransitIPv460
AS971PureVoltage Hosting Inc.UnclassifiedIPv46
AS14907Wikimedia Foundation Inc.HostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397968SIMPLE CLOUD SOLUTION LLCUnclassifiedIPv4 IPv6122
AS402629TAIPEI101UnclassifiedIPv4 IPv690
AS402981CodeUnclassifiedIPv458
AS22603SharkBackup LLCUnclassifiedIPv457
AS401170HBG Inc.UnclassifiedIPv4 IPv64
AS18636ONDRYA LLCUnclassifiedIPv61

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,012
AS46475Limestone Networks, Inc.HostingIPv4662
AS13335Cloudflare, Inc.HostingIPv4282
AS30456Cosmic Global NetworksUnclassifiedIPv4160
AS397968SIMPLE CLOUD SOLUTION LLCUnclassifiedIPv4 IPv6122
AS2914NTT America, Inc.TransitIPv4104
AS402629TAIPEI101UnclassifiedIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv470
AS402981CodeUnclassifiedIPv458
AS22603SharkBackup LLCUnclassifiedIPv457

All 14 adjacent →

Provenance

Where this comes from

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