Observed topology

AS273453 R G DE SOUZA INFORMATICA

Unclassified AFRINIC

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273453: 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
AS7738	V tal	Unclassified	IPv4 IPv6	142
AS61614	67 TELECOM LTDA	Residential	IPv6	33
AS268625	NETFAST TELECOMUNICACOES E MULTIMIDIA LTDA	Unclassified	IPv4	25

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268633	73s Telecom	Unclassified	IPv4	63
AS271651	D P DOS SANTOS SERVICOS DE INTERNET	Unclassified	IPv4	63
AS273446	DBR TELECOMUNICACOES LTDA	Unclassified	IPv4	63
AS263519	Minas Nova Telecom LTDA	Unclassified	IPv4	25

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS7738	V tal	Unclassified	IPv4 IPv6	305
AS268625	NETFAST TELECOMUNICACOES E MULTIMIDIA LTDA	Unclassified	IPv4	76
AS268633	73s Telecom	Unclassified	IPv4	63
AS271651	D P DOS SANTOS SERVICOS DE INTERNET	Unclassified	IPv4	63
AS273446	DBR TELECOMUNICACOES LTDA	Unclassified	IPv4	63
AS61614	67 TELECOM LTDA	Residential	IPv6	33
AS263519	Minas Nova Telecom LTDA	Unclassified	IPv4	25

Provenance

Where this comes from

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