Observed topology
AS199434 COTA-AS
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS199434: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 225 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 60 |
| AS12479 | Orange Espagne SA | Residential | IPv4 IPv6 | 59 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 18 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 11 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 6 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS199434 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS199434 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 292 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 81 |
| AS202054 | GRUPO SYS4NET, S.L. | Unclassified | IPv4 | 80 |
| AS12479 | Orange Espagne SA | Residential | IPv4 IPv6 | 59 |
| AS205279 | Montel Telecom, S.L. | Unclassified | IPv4 | 30 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 27 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 9 |
| AS29632 | Netassist International EOOD | 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.