Observed topology
AS28283 AS28283 - Adylnet Telecom
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS28283: 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 |
|---|---|---|---|---|
| AS8167 | V tal | Residential | IPv4 IPv6 | 119 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 58 |
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 50 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 43 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 39 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 28 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 22 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 18 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS28283 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS268218 | COPREL TELECOM LTDA | Unclassified | IPv4 IPv6 | 2,407 |
| AS269656 | RK Telecom Provedor Internet LTDA | Residential | IPv4 IPv6 | 1,355 |
| AS7465 | PROCERGS - Cia de Processamento de Dados do RGS | Unclassified | IPv4 | 1,170 |
| AS52653 | Marlon L. Larger & Cia Ltda | Unclassified | IPv4 IPv6 | 1,075 |
| AS262741 | CONECTSUL SOLUCOES EM INTERNET | Residential | IPv4 IPv6 | 1,005 |
| AS61893 | RM dos Santos Informatica | Residential | IPv4 IPv6 | 991 |
| AS263604 | Hilton C. Bender Eireli | Unclassified | IPv4 IPv6 | 937 |
| AS271700 | STEC GUAIBA | Unclassified | IPv4 IPv6 | 873 |
| AS53169 | Tche Turbo Provedor de Internet LTDA | Residential | IPv4 IPv6 | 854 |
| AS262543 | BRMOM CONSTRUINDO CONEXOES LTDA | Unclassified | IPv4 IPv6 | 682 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28283 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8167 | V tal | Residential | IPv4 IPv6 | 19,732 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 7,925 |
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 7,265 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 5,625 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 5,250 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 4,538 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,306 |
| AS266181 | GOLDEN LINK | Residential | IPv4 IPv6 | 3,152 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 3,013 |
| AS262587 | CST - Cerentini Solucoes em Tecnologia | Residential | IPv4 IPv6 | 2,918 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.