asn.dev

Observed topology

AS267347 PEGASUS TELECOM

Unclassified ARIN

Upstreams 3 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 1
Upstream graph Who carries AS267347, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS267347 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6217
AS265205UnoNet Telecomunicacoes LTDAResidentialIPv460
AS24482SG.GSHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264861HIGH TELECOM SERVICOS DE MULTIMIDIA LTDAUnclassifiedIPv4186
AS270792luciano comin cardozo-meUnclassifiedIPv451

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6451
AS264861HIGH TELECOM SERVICOS DE MULTIMIDIA LTDAUnclassifiedIPv4186
AS265205UnoNet Telecomunicacoes LTDAResidentialIPv460
AS270792luciano comin cardozo-meUnclassifiedIPv451
AS24482SG.GSHostingIPv46

Provenance

Where this comes from

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