Observed topology
AS3330 PROFINET-AT eww ag
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3330: 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 |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 170 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 97 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 83 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 75 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 66 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 64 |
| AS21013 | eww ag | Unclassified | IPv4 IPv6 | 38 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 36 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 14 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 14 |
Transit
Downstream networks
Networks for which AS3330 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35765 | Gemeindewerke Telfs GmbH | Unclassified | IPv4 | 337 |
| AS204410 | Feistritzwerke-STEWEAG GmbH | Unclassified | IPv4 IPv6 | 240 |
| AS196897 | Horst Grottenthaler | Unclassified | IPv4 | 220 |
| AS16055 | AADD GmbH | Unclassified | IPv4 | 180 |
| AS28760 | Infotech EDV-Systeme GmbH | Unclassified | IPv4 IPv6 | 147 |
| AS61108 | eww ag | Unclassified | IPv4 IPv6 | 143 |
| AS29395 | webquake Computing Solutions GmbH | Unclassified | IPv4 | 58 |
| AS48055 | Business Data Solutions GmbH | Unclassified | IPv4 | 57 |
| AS200026 | Ortswaerme St. Johann in Tirol GmbH | Unclassified | IPv4 IPv6 | 50 |
| AS39555 | Stadtwerke Schwaz GmbH | Unclassified | IPv4 IPv6 | 27 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3330 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 612 |
| AS196897 | Horst Grottenthaler | Unclassified | IPv4 | 500 |
| AS35765 | Gemeindewerke Telfs GmbH | Unclassified | IPv4 | 337 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 320 |
| AS28760 | Infotech EDV-Systeme GmbH | Unclassified | IPv4 IPv6 | 299 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 274 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 250 |
| AS204410 | Feistritzwerke-STEWEAG GmbH | Unclassified | IPv4 IPv6 | 240 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 237 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 209 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.