Observed topology

AS273458 DEBORA AMANDA DA SILVA LEAL

Unclassified ARIN

Upstreams 0 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271137	diego fernando sales feitosa	Unclassified	IPv4 IPv6	95
AS262579	GE Network Provedor de Internet LTDA	Unclassified	IPv4	62
AS270304	FIBRAVELOZ PROVEDOR DE INTERNET LTDA	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS271137	diego fernando sales feitosa	Unclassified	IPv4 IPv6	95
AS265269	MEGA TELE INFORMATICA	Unclassified	IPv4 IPv6	88
AS52965	1TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDA	Unclassified	IPv4	76
AS262579	GE Network Provedor de Internet LTDA	Unclassified	IPv4	62
AS270304	FIBRAVELOZ PROVEDOR DE INTERNET LTDA	Unclassified	IPv4	60
AS271612	LOGO Telecom	Unclassified	IPv4 IPv6	53

Provenance

Where this comes from

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