asn.dev

Observed topology

AS395823 DOOF - doof.net

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395823: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6240
AS1299Arelion Sweden ABTransitIPv4 IPv640
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS3130RGnet OUUnclassifiedIPv43
AS34927iFog GmbHHostingIPv43
AS58057Securebit AGUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398960Cryoflesh IncUnclassifiedIPv4 IPv6265
AS47689Pudu, LLCUnclassifiedIPv455
AS32150DANGA INTERACTIVEUnclassifiedIPv450
AS54429Local Connectivity LabUnclassifiedIPv448

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6687
AS398960Cryoflesh IncUnclassifiedIPv4 IPv6265
AS54429Local Connectivity LabUnclassifiedIPv4166
AS1299Arelion Sweden ABTransitIPv4 IPv6123
AS47689Pudu, LLCUnclassifiedIPv455
AS32150DANGA INTERACTIVEUnclassifiedIPv450
AS24482SG.GSHostingIPv4 IPv67
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv66
AS3130RGnet OUUnclassifiedIPv44
AS34927iFog GmbHHostingIPv43

All 11 adjacent →

Provenance

Where this comes from

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