Observed topology

AS23265 POCKETINET

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

Upstream graph Who carries AS23265, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS23265 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23265: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	236
AS25899	LS Networks	Unclassified	IPv4	12
AS3130	RGnet OU	Unclassified	IPv4	4
AS24482	SG.GS	Hosting	IPv4	4
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS13438	Vivio Technologies	Hosting	IPv4	490
AS14940	LIGO Livingston Observatory	Unclassified	IPv4	65
AS11436	Benton County Emergency Management	Unclassified	IPv4	30
AS396384	Baker Boyer Bancorp	Unclassified	IPv4	4

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	798
AS13438	Vivio Technologies	Hosting	IPv4	490
AS14940	LIGO Livingston Observatory	Unclassified	IPv4	65
AS11436	Benton County Emergency Management	Unclassified	IPv4	30
AS3130	RGnet OU	Unclassified	IPv4	16
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	16
AS25899	LS Networks	Unclassified	IPv4	12
AS24482	SG.GS	Hosting	IPv4	6
AS396384	Baker Boyer Bancorp	Unclassified	IPv4	4
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	1

Provenance

Where this comes from

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