Observed topology
AS219062 Nera - Nera sp z.o.o
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS219062: 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 | 119 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 105 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 12 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 4 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 | 4 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 4 |
| AS48185 | team.blue NV | Unclassified | IPv4 | 4 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 | 4 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS219062 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47329 | WDM Sp. z o.o. | Unclassified | IPv4 | 882 |
| AS197099 | Multinet24 Sp.zoo | Unclassified | IPv4 | 720 |
| AS206963 | SPRINTCDN LLC | Unclassified | IPv4 | 455 |
| AS52153 | Pawel Kowalski BGCOM | Residential | IPv4 | 65 |
| AS8819 | Metro Internet Sp. z o.o. | Hosting | IPv4 | 52 |
| AS15624 | OKITECH Krzysztof Kusnierczyk | Residential | IPv4 | 48 |
| AS60646 | Krzysztof Sebastian Widerkiewicz trading as LutekLAN.pl | Unclassified | IPv4 | 35 |
| AS199723 | Michal Gomolka trading as Strzyzowski.Net Spolka Komandytowa | Residential | IPv4 | 20 |
| AS199585 | TELNET Ropczyce Sp. z o.o. | Residential | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS219062 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,150 |
| AS47329 | WDM Sp. z o.o. | Unclassified | IPv4 | 928 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 737 |
| AS197099 | Multinet24 Sp.zoo | Unclassified | IPv4 | 720 |
| AS206963 | SPRINTCDN LLC | Unclassified | IPv4 | 455 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 251 |
| AS52153 | Pawel Kowalski BGCOM | Residential | IPv4 | 112 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 105 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 97 |
| AS8819 | Metro Internet Sp. z o.o. | Hosting | IPv4 | 52 |
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.