asn.dev

Observed topology

AS268503 AS268503 - L.L Informatica LTDA - ME

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268503: 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
AS273669LINKE SOLUCOES LTDAHostingIPv4 IPv6526

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268037OK NET INFOR LTDAUnclassifiedIPv4 IPv6348
AS270499CERTA FIBRA MEUnclassifiedIPv4 IPv6225
AS268024TURBONET CAXIASUnclassifiedIPv4 IPv6167
AS269461Xfiber InternetUnclassifiedIPv4 IPv6143
AS264584CAWEB INFORMATICA LTDAUnclassifiedIPv4 IPv6141
AS268625NETFAST TELECOMUNICACOES E MULTIMIDIA LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS273669LINKE SOLUCOES LTDAHostingIPv4 IPv61,625
AS268037OK NET INFOR LTDAUnclassifiedIPv4 IPv6348
AS270499CERTA FIBRA MEUnclassifiedIPv4 IPv6225
AS268024TURBONET CAXIASUnclassifiedIPv4 IPv6177
AS264584CAWEB INFORMATICA LTDAUnclassifiedIPv4 IPv6145
AS269461Xfiber InternetUnclassifiedIPv4 IPv6143
AS268625NETFAST TELECOMUNICACOES E MULTIMIDIA LTDAUnclassifiedIPv461

Provenance

Where this comes from

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