Observed topology
AS205103 TELEGRAPH-AS Telegraph42 Management GmbH
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS205103: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 56 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 7 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 6 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 4 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 4 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 2 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2 |
| AS35320 | Eurotranstelecom Ltd | Unclassified | IPv4 IPv6 | 2 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 2 |
Transit
Downstream networks
Networks for which AS205103 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48887 | CJSC INDIGO TAJIKISTAN | Unclassified | IPv4 | 861 |
| AS51346 | Opened Joint Stock Company "Tojiktelecom" | Unclassified | IPv4 IPv6 | 358 |
| AS208592 | LLC "NET SOLUTIONS" | Unclassified | IPv4 | 354 |
| AS61010 | IPNET OOO | Unclassified | IPv4 IPv6 | 248 |
| AS202746 | Europeer Ltd. | Unclassified | IPv4 IPv6 | 102 |
| AS50107 | Vista Technology LLP | Unclassified | IPv4 IPv6 | 14 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 13 |
Adjacency
Adjacent networks
Every AS seen directly next to AS205103 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 16,327 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 15,860 |
| AS208592 | LLC "NET SOLUTIONS" | Unclassified | IPv4 IPv6 | 6,898 |
| AS35168 | TNS-Plus LLP | Unclassified | IPv4 | 3,429 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 3,227 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,999 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 2,236 |
| AS51346 | Opened Joint Stock Company "Tojiktelecom" | Unclassified | IPv4 IPv6 | 1,251 |
| AS48887 | CJSC INDIGO TAJIKISTAN | Unclassified | IPv4 | 861 |
| AS61010 | IPNET OOO | Unclassified | IPv4 IPv6 | 692 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.