Observed topology

AS40633 LAIX

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40633: 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	108
AS174	Cogent Communications, LLC	Transit	IPv4	12
AS29838	Atlantic Metro Communications II, Inc.	Hosting	IPv4	10
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS4775	Globe Telecoms	Unclassified	IPv4	1,656
AS23988	PLDT GLOBAL Corp. Internet-based Services AP	Unclassified	IPv4	66
AS29838	Atlantic Metro Communications II, Inc.	Hosting	IPv4	2
AS54994	Meteverse Limited.	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS29838	Atlantic Metro Communications II, Inc.	Hosting	IPv4	4,562
AS4775	Globe Telecoms	Unclassified	IPv4	4,235
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	992
AS174	Cogent Communications, LLC	Transit	IPv4	638
AS6939	Hurricane Electric LLC	Transit	IPv4	217
AS23988	PLDT GLOBAL Corp. Internet-based Services AP	Unclassified	IPv4	66
AS33548	Unwired Broadband, LLC	Residential	IPv4	1
AS54994	Meteverse Limited.	Unclassified	IPv4	1

Provenance

Where this comes from

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