asn.dev

Observed topology

AS266374 Ponte Digital

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266374: 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
AS263073DTEL TELECOMResidentialIPv4 IPv6101
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268585JULIANA N CORDEIRO DE LIMA SERVICOS DE COMUNICACOUnclassifiedIPv4 IPv6214
AS28188Pronto Net Ltda.UnclassifiedIPv4 IPv6188

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263073DTEL TELECOMResidentialIPv4 IPv6399
AS268585JULIANA N CORDEIRO DE LIMA SERVICOS DE COMUNICACOUnclassifiedIPv4 IPv6214
AS28188Pronto Net Ltda.UnclassifiedIPv4 IPv6188
AS6939Hurricane Electric LLCTransitIPv4 IPv6179
AS24482SG.GSHostingIPv4 IPv614
AS35280F5 Networks SARLHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Provenance

Where this comes from

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