Observed topology

AS267199 AS267199 - REDEMETRO TELECOMUNICACOES LTDA

Unclassified APNIC NSP

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267199: 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
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	132
AS28283	Adylnet Telecom	Residential	IPv4	24

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268516	Midia Net Telecom	Unclassified	IPv4 IPv6	643
AS28590	Directnet Prestacao de Servicos Ltda.	Unclassified	IPv4	181
AS269463	INTER-K Internet Service	Unclassified	IPv4	181
AS263320	Sansara Telecom	Unclassified	IPv4 IPv6	77

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	1,121
AS268516	Midia Net Telecom	Unclassified	IPv4 IPv6	643
AS28590	Directnet Prestacao de Servicos Ltda.	Unclassified	IPv4	181
AS269463	INTER-K Internet Service	Unclassified	IPv4	181
AS28283	Adylnet Telecom	Residential	IPv4	117
AS263320	Sansara Telecom	Unclassified	IPv4 IPv6	77

Provenance

Where this comes from

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