Observed topology
AS12941 INTERSAAR-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12941: 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 | 135 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 118 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 73 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 24 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 24 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 17 |
| AS5511 | Orange S.A. | Transit | IPv4 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 10 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS12941 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197063 | PfalzConnect GmbH | Residential | IPv4 IPv6 | 512 |
| AS202707 | omnidat GmbH | Residential | IPv4 | 175 |
| AS60400 | ORBIS SE | Unclassified | IPv4 | 59 |
| AS196968 | Ilm-Provider UG (haftungsbeschraenkt) | Residential | IPv4 | 30 |
| AS210521 | iks Informations- und Kommunikationssysteme GmbH | Unclassified | IPv4 IPv6 | 25 |
| AS203536 | FNOH DSL Suedheide GmbH | Residential | IPv4 | 17 |
| AS29510 | internett GmbH | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12941 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197063 | PfalzConnect GmbH | Residential | IPv4 IPv6 | 577 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 439 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 259 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 217 |
| AS202707 | omnidat GmbH | Residential | IPv4 | 175 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 95 |
| AS60400 | ORBIS SE | Unclassified | IPv4 | 59 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 41 |
| AS206499 | LOCIX LIMITED | Unclassified | IPv4 | 37 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 36 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.