Observed topology
AS47447 TTM
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS47447: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 808 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 669 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 364 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 271 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 180 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 168 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 55 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 55 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 42 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 42 |
Transit
Downstream networks
Networks for which AS47447 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202656 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 8,493 |
| AS202448 | MVPS LTD | Unclassified | IPv4 IPv6 | 1,135 |
| AS60991 | Dominik Schubert | Unclassified | IPv4 IPv6 | 207 |
| AS203466 | INTROSERV d.o.o | Unclassified | IPv4 IPv6 | 149 |
| AS395092 | Shock Hosting LLC | Unclassified | IPv4 IPv6 | 148 |
| AS204033 | Oliver Arthur | Unclassified | IPv4 IPv6 | 128 |
| AS212966 | Markus Wolf | Unclassified | IPv4 IPv6 | 124 |
| AS49603 | Nerdherrschaft GmbH | Unclassified | IPv4 | 118 |
| AS201790 | Joshua Eliah Gerke | Unclassified | IPv4 IPv6 | 91 |
| AS39378 | servinga GmbH | Hosting | IPv4 IPv6 | 67 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47447 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202656 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 8,493 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 5,290 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,102 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,594 |
| AS202448 | MVPS LTD | Unclassified | IPv4 IPv6 | 1,135 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,025 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 507 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 447 |
| AS132132 | MyRepublic Ltd. | Residential | IPv4 | 438 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 430 |
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.