asn.dev

Observed topology

AS6 BULL-HN

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6: 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
AS3356Level 3 Parent, LLCTransitIPv41,320
AS16128AGARIK SASUnclassifiedIPv4360
AS22773Cox Communications Inc.ResidentialIPv4177
AS197251FOP TERESHCHENKO OLEKSANDR TROHUMOVICHUnclassifiedIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328527PDS Networks Nigeria LimitedUnclassifiedIPv628
AS37495Eko-Konnect Research and Education InitiativeUnclassifiedIPv626
AS328107GUILAB SAUnclassifiedIPv66
AS138115PT DenevaHostingIPv45
AS328259WAW SASResidentialIPv65
AS37521Internet Solutions Nigeria LimitedHostingIPv64

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv41,320
AS16128AGARIK SASUnclassifiedIPv4360
AS22773Cox Communications Inc.ResidentialIPv4177
AS37613DOLPHIN TELECOMMUNICATION LIMITEDUnclassifiedIPv682
AS328527PDS Networks Nigeria LimitedUnclassifiedIPv628
AS37495Eko-Konnect Research and Education InitiativeUnclassifiedIPv626
AS328107GUILAB SAUnclassifiedIPv619
AS138115PT DenevaHostingIPv410
AS197251FOP TERESHCHENKO OLEKSANDR TROHUMOVICHUnclassifiedIPv410
AS328259WAW SASResidentialIPv65

All 11 adjacent →

Provenance

Where this comes from

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