Observed topology
AS263258 INTERLIG TELECOM
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS263258: 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.
Transit
Downstream networks
Networks for which AS263258 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS268947 | ALTANET SERVICOS DE TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 530 |
| AS266104 | RPNET TELECOM | Unclassified | IPv4 IPv6 | 328 |
| AS268800 | micro line comercial ltda | Unclassified | IPv4 | 189 |
| AS267461 | GLEIDSON DE O. MARQUES - ME | Unclassified | IPv4 IPv6 | 162 |
| AS274809 | FLC Pomin | Unclassified | IPv4 IPv6 | 88 |
Adjacency
Adjacent networks
Every AS seen directly next to AS263258 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS266445 | SEA TELECOM LTDA | Unclassified | IPv4 IPv6 | 1,064 |
| AS268947 | ALTANET SERVICOS DE TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 530 |
| AS264329 | ESTRATEGIA REDES DE TELECOMUNICACOES LTDA. | Unclassified | IPv4 IPv6 | 412 |
| AS262462 | Aranet Play | Unclassified | IPv4 IPv6 | 339 |
| AS266104 | RPNET TELECOM | Unclassified | IPv4 IPv6 | 328 |
| AS1000 | CORIX NETWORKS | Unclassified | IPv4 IPv6 | 242 |
| AS268800 | micro line comercial ltda | Unclassified | IPv4 | 189 |
| AS267461 | GLEIDSON DE O. MARQUES - ME | Unclassified | IPv4 IPv6 | 162 |
| AS274809 | FLC Pomin | Unclassified | IPv4 IPv6 | 88 |
| AS271253 | LINK BRASIL TELECOMUNICACOES LTDA | Unclassified | IPv6 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.