Observed topology

AS133968 LOGON-AS-IN Logon Broadband

Residential ARIN

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133968: 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
AS18229	CtrlS	Hosting	IPv4 IPv6	627

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS150635	DURGA WI FI OPC PVT LTD	Unclassified	IPv4	236
AS149214	OM SHIV SAI INTERNET SERVICE OPC PVT LTD	Residential	IPv4	228
AS141574	St Broadband Cable Service	Unclassified	IPv4 IPv6	155
AS135207	Cloudnet Communications Pvt Ltd	Unclassified	IPv4	116
AS136316	PRATHAMESH BROADBAND PRIVATE LIMITED	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS18229	CtrlS	Hosting	IPv4 IPv6	1,336
AS150635	DURGA WI FI OPC PVT LTD	Unclassified	IPv4	236
AS149214	OM SHIV SAI INTERNET SERVICE OPC PVT LTD	Residential	IPv4	228
AS141574	St Broadband Cable Service	Unclassified	IPv4 IPv6	155
AS135207	Cloudnet Communications Pvt Ltd	Unclassified	IPv4	116
AS136695	Zeroshell Networks Private Limited	Unclassified	IPv4	116
AS136316	PRATHAMESH BROADBAND PRIVATE LIMITED	Unclassified	IPv4	59
AS150593	Dataexpress Pvt Ltd	Unclassified	IPv6	31

Provenance

Where this comes from

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