Observed topology
AS1031 PEER1-1031 - PEER 1031 LLC
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS1031: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 8 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv6 | 2 |
| AS50304 | Blix Solutions AS | Unclassified | IPv6 | 2 |
| AS1103 | SURF B.V. | Unclassified | IPv6 | 1 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 1 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv6 | 1 |
| AS24482 | SG.GS | Hosting | IPv6 | 1 |
| AS34019 | Hivane Association | Unclassified | IPv6 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv6 | 1 |
| AS48185 | team.blue NV | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS1031 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS263917 | Nossarede Telecom LTDA ME | Residential | IPv4 IPv6 | 1,084 |
| AS52892 | COPREL TELECOM LTDA | Residential | IPv4 IPv6 | 941 |
| AS264996 | SERVLINK TELECOM LTDA - ME | Residential | IPv6 | 909 |
| AS28173 | Dinamica Telecomunicacoes Ltda | Unclassified | IPv6 | 640 |
| AS262505 | N4 Telecomunicacoes LTDA - ME | Unclassified | IPv4 IPv6 | 607 |
| AS262428 | LINK10 BR | Residential | IPv4 IPv6 | 351 |
| AS269359 | CANAA TELECOMUNICACOES LTDA - ME | Residential | IPv4 IPv6 | 343 |
| AS265379 | JULIO CESAR DAS NEVES - ME | Unclassified | IPv4 IPv6 | 247 |
| AS269089 | Hilan Telecom Ltda | Unclassified | IPv4 IPv6 | 232 |
| AS262753 | VOCE TELECOMUNICACOES LTDA | Residential | IPv4 IPv6 | 218 |
Adjacency
Adjacent networks
Every AS seen directly next to AS1031 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4230 | CLARO S.A. | Residential | IPv4 | 15,793 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 9,271 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 8,461 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 7,958 |
| AS264996 | SERVLINK TELECOM LTDA - ME | Residential | IPv6 | 6,922 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 5,434 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,258 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 3,678 |
| AS262999 | IVI TECNOLOGIA E COMUNICACAO LTDA | Unclassified | IPv4 IPv6 | 3,198 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 2,988 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.