Observed topology
AS33843 NEPUSTILNET-AS02
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS33843: 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 IPv6 | 164 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 42 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 32 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 12 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 10 |
| AS1836 | green.ch AG | Residential | IPv4 | 4 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 4 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 4 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS33843 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 AS33843 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 188 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 99 |
| AS203546 | Naegele IT-Service GmbH | Unclassified | IPv4 | 59 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 53 |
| AS206394 | CeGaT GmbH | Unclassified | IPv4 IPv6 | 53 |
| AS198818 | ISP Service eG | Unclassified | IPv4 | 32 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 27 |
| AS12502 | Dr.-Ing. Nepustil & Co. GmbH Internet Service Center Ingenieurgesellschaft fuer Systemsoftware und Kommunikationstechnik | Residential | IPv4 IPv6 | 19 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 15 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 | 9 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.