Observed topology
AS269783 WIND NET S.A.
Residential AFRINIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS269783: 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 | IPv4 IPv6 | 120 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 99 |
| AS61624 | INFNOC TECNOLOGIA LTDA | Unclassified | IPv4 IPv6 | 43 |
| AS28158 | Ampernet Telecomunicacoes Ltda | Unclassified | IPv4 | 39 |
| AS24482 | SG.GS | Hosting | IPv6 | 6 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv6 | 5 |
Transit
Downstream networks
Networks for which AS269783 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS265728 | FLYNET SRL | Residential | IPv4 | 410 |
| AS264770 | Leonir Remussi (KDMNET) | Unclassified | IPv4 IPv6 | 354 |
| AS263732 | PANDA CONECT S.A. | Unclassified | IPv4 IPv6 | 350 |
| AS267914 | TVH S.A | Unclassified | IPv4 IPv6 | 330 |
| AS267837 | Vicente Sosa Peralta | Unclassified | IPv4 IPv6 | 271 |
| AS272099 | WIRSCHKE MONGES RICARDO DANIEL | Hosting | IPv4 IPv6 | 221 |
| AS272062 | TV 2 S.A. | Unclassified | IPv4 IPv6 | 211 |
| AS263717 | SOL TELECOMUNICACIONES S.A. | Residential | IPv4 | 200 |
| AS263750 | Douglas Back Pavan (SI NET) | Residential | IPv4 IPv6 | 183 |
| AS274952 | CMD INTERNET E.A.S. | Unclassified | IPv4 IPv6 | 170 |
Adjacency
Adjacent networks
Every AS seen directly next to AS269783 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 1,693 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 782 |
| AS61624 | INFNOC TECNOLOGIA LTDA | Unclassified | IPv4 IPv6 | 660 |
| AS28158 | Ampernet Telecomunicacoes Ltda | Unclassified | IPv4 | 556 |
| AS265728 | FLYNET SRL | Residential | IPv4 | 410 |
| AS264770 | Leonir Remussi (KDMNET) | Unclassified | IPv4 IPv6 | 354 |
| AS263732 | PANDA CONECT S.A. | Unclassified | IPv4 IPv6 | 350 |
| AS267914 | TVH S.A | Unclassified | IPv4 IPv6 | 330 |
| AS267837 | Vicente Sosa Peralta | Unclassified | IPv4 IPv6 | 271 |
| AS272099 | WIRSCHKE MONGES RICARDO DANIEL | Hosting | IPv4 IPv6 | 221 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.