asn.dev

Observed topology

AS268623 VTEK TELECOM LTDA - ME

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268623: 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
AS263880WANTEL TECNOLOGIA LTDA. EPPUnclassifiedIPv4 IPv6414
AS52901MINAS TELECOMUnclassifiedIPv4 IPv6109

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270800ROBERTO VIEIRA DA CRUZ MEUnclassifiedIPv4 IPv6285
AS273438Olah ConnectUnclassifiedIPv4 IPv6166
AS269041MJB & TJS COM. E SERVICOS DE INFORMATICA LTDAUnclassifiedIPv4 IPv6126

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263880WANTEL TECNOLOGIA LTDA. EPPUnclassifiedIPv4 IPv6965
AS270800ROBERTO VIEIRA DA CRUZ MEUnclassifiedIPv4 IPv6285
AS273438Olah ConnectUnclassifiedIPv4 IPv6166
AS52901MINAS TELECOMUnclassifiedIPv4 IPv6135
AS269041MJB & TJS COM. E SERVICOS DE INFORMATICA LTDAUnclassifiedIPv4 IPv6126

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.