Observed topology

AS400282 UPX

Unclassified ARIN Content

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS400282: 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
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	126

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52863	UPX TECNOLOGIA LTDA	Unclassified	IPv4 IPv6	270
AS263009	FORTE TELECOM LTDA.	Hosting	IPv4	62
AS262926	BRADESCARD MEXICO S DE RL	Unclassified	IPv4	48
AS53107	EVEO S.A.	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	10,579
AS52863	UPX TECNOLOGIA LTDA	Unclassified	IPv4 IPv6	9,900
AS263009	FORTE TELECOM LTDA.	Hosting	IPv4	607
AS3223	Voxility LLP	Hosting	IPv4	102
AS262926	BRADESCARD MEXICO S DE RL	Unclassified	IPv4	48
AS6453	TATA COMMUNICATIONS (AMERICA) INC	Transit	IPv4	1
AS53107	EVEO S.A.	Unclassified	IPv4	1

Provenance

Where this comes from

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