asn.dev

Observed topology

AS22284 AS22284-DOI-OPS - U.S. Department of the Interior

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22284: 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, LLCTransitIPv4 IPv611,574
AS8047GENERAL COMMUNICATION, INC.ResidentialIPv41,042

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS3549Level 3 Parent, LLCTransitIPv41,704
AS5663Department of Interior United States Geological SurveyUnclassifiedIPv4240
AS1842Department of Interior United States Geological SurveyUnclassifiedIPv4120
AS21633U.S. Department of the InteriorUnclassifiedIPv4120

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv613,924
AS3549Level 3 Parent, LLCTransitIPv41,870
AS8047GENERAL COMMUNICATION, INC.ResidentialIPv41,042
AS5663Department of Interior United States Geological SurveyUnclassifiedIPv4240
AS1842Department of Interior United States Geological SurveyUnclassifiedIPv4120
AS21633U.S. Department of the InteriorUnclassifiedIPv4120

Provenance

Where this comes from

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