Observed topology
AS15763 ASDOKOM
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS15763: 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 |
|---|---|---|---|---|
| AS34309 | Link11 GmbH | Unclassified | IPv4 IPv6 | 1,259 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 437 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 312 |
| AS12329 | GLASFASER RUHR GmbH & Co. KG | Unclassified | IPv4 IPv6 | 172 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 131 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 21 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 21 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 21 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 21 |
| AS1836 | green.ch AG | Residential | IPv4 | 20 |
Transit
Downstream networks
Networks for which AS15763 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203593 | TeleMark Telekommunikationsgesellschaft Mark mbH | Unclassified | IPv4 IPv6 | 577 |
| AS41585 | ELEMENTMEDIA GmbH | Unclassified | IPv4 | 435 |
| AS16024 | GELSEN-NET Kommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 352 |
| AS213731 | Westfalen-Informatik AG | Unclassified | IPv4 IPv6 | 162 |
| AS15486 | Materna Information & Communications SE | Unclassified | IPv4 | 150 |
| AS200931 | Lumberg Connect GmbH | Unclassified | IPv4 IPv6 | 145 |
| AS34722 | rku.it GmbH | Unclassified | IPv4 | 138 |
| AS12329 | GLASFASER RUHR GmbH & Co. KG | Unclassified | IPv4 | 84 |
| AS210437 | Sonepar Deutschland Information Services GmbH | Unclassified | IPv4 IPv6 | 75 |
| AS43455 | Schlueter-Systems KG | Unclassified | IPv4 IPv6 | 73 |
Adjacency
Adjacent networks
Every AS seen directly next to AS15763 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 1,637 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,379 |
| AS34309 | Link11 GmbH | Unclassified | IPv4 IPv6 | 1,259 |
| AS12329 | GLASFASER RUHR GmbH & Co. KG | Unclassified | IPv4 IPv6 | 1,228 |
| AS203593 | TeleMark Telekommunikationsgesellschaft Mark mbH | Unclassified | IPv4 IPv6 | 700 |
| AS16024 | GELSEN-NET Kommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 454 |
| AS41585 | ELEMENTMEDIA GmbH | Unclassified | IPv4 | 435 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 249 |
| AS213731 | Westfalen-Informatik AG | Unclassified | IPv4 IPv6 | 162 |
| AS15486 | Materna Information & Communications SE | Unclassified | IPv4 | 150 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.