Observed topology
AS6855 SK-TELEKOM Slovak Telekom T-Mobile CZ
Mobile RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS6855: 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 | 1,497 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 669 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 188 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 132 |
| AS47232 | ISP Alliance a.s. | Residential | IPv4 | 37 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 15 |
| AS30764 | PODA a.s. | Residential | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS6855 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS13036 | T-Mobile Czech Republic a.s. | Unclassified | IPv4 IPv6 | 2,170 |
| AS29148 | SURANY.NET s.r.o. | Unclassified | IPv4 IPv6 | 845 |
| AS49117 | DTnet Detva s.r.o. | Unclassified | IPv4 IPv6 | 544 |
| AS48298 | MINISTERSTVO VNITRA CR | Unclassified | IPv4 IPv6 | 461 |
| AS21433 | Accenture UK Limited | Unclassified | IPv4 | 397 |
| AS30898 | DataCentrum | Unclassified | IPv4 | 381 |
| AS50881 | ESET, spol. s r.o. | Unclassified | IPv4 IPv6 | 304 |
| AS216450 | Letiste Praha, a. s. | Unclassified | IPv4 | 290 |
| AS34475 | Agrostroj Pelhrimov, a.s. | Unclassified | IPv4 | 244 |
| AS201447 | The Czech National Bank | Unclassified | IPv4 | 244 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6855 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 11,024 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 3,212 |
| AS13036 | T-Mobile Czech Republic a.s. | Unclassified | IPv4 IPv6 | 2,170 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,008 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 929 |
| AS29148 | SURANY.NET s.r.o. | Unclassified | IPv4 IPv6 | 845 |
| AS49117 | DTnet Detva s.r.o. | Unclassified | IPv4 IPv6 | 544 |
| AS48298 | MINISTERSTVO VNITRA CR | Unclassified | IPv4 IPv6 | 461 |
| AS21433 | Accenture UK Limited | Unclassified | IPv4 | 397 |
| AS30898 | DataCentrum | Unclassified | IPv4 | 381 |
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.