asn.dev

Observed topology

AS268625 NETFAST TELECOMUNICACOES E MULTIMIDIA LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268625: 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
AS7738V talUnclassifiedIPv4 IPv6183
AS268421WEBFIBER TELECOMUNICACAO LTDA MEResidentialIPv4183
AS26615TIM S/AMobileIPv4 IPv6174
AS268503L.L Informatica LTDA - MEUnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268421WEBFIBER TELECOMUNICACAO LTDA MEResidentialIPv4 IPv6286
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv694
AS266397UNINET TELECOM E INFORMATICA - EIRELLI - MEUnclassifiedIPv4 IPv692
AS273453R G DE SOUZA INFORMATICAUnclassifiedIPv425

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS26615TIM S/AMobileIPv4 IPv6646
AS268421WEBFIBER TELECOMUNICACAO LTDA MEResidentialIPv4 IPv6469
AS7738V talUnclassifiedIPv4 IPv6259
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv694
AS266397UNINET TELECOM E INFORMATICA - EIRELLI - MEUnclassifiedIPv4 IPv692
AS273453R G DE SOUZA INFORMATICAUnclassifiedIPv476
AS268503L.L Informatica LTDA - MEUnclassifiedIPv459

Provenance

Where this comes from

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