Observed topology
AS214762 MATHOST Sebastian Stefanek trading as MatHost.eu
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS214762: 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 | 309 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 70 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 59 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 38 |
| AS205941 | Lungu Stefan Gabriel | Unclassified | IPv4 | 14 |
| AS24482 | SG.GS | Hosting | IPv6 | 9 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 5 |
Transit
Downstream networks
Networks for which AS214762 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201132 | Mateusz Sikorski trading as MSCode | Hosting | IPv4 IPv6 | 229 |
| AS218995 | Bobeica Mihaita David | Unclassified | IPv6 | 187 |
| AS198057 | Flooyd Telecom LTDA | Residential | IPv6 | 171 |
| AS219481 | Krzysztof Manczak | Unclassified | IPv4 IPv6 | 169 |
| AS201640 | Patryk Kulikowski trading as psHost | Hosting | IPv4 IPv6 | 167 |
| AS63286 | Hop179 OU | Unclassified | IPv4 IPv6 | 96 |
| AS218628 | Mariusz Mikolajczak trading as CodeBy | Unclassified | IPv4 IPv6 | 96 |
| AS218720 | Marcin Hornik trading as ActivHost | Unclassified | IPv4 IPv6 | 96 |
| AS218722 | Dawid Slowik | Unclassified | IPv4 IPv6 | 96 |
| AS218283 | LLC KETRIX PARK | Unclassified | IPv4 IPv6 | 95 |
Adjacency
Adjacent networks
Every AS seen directly next to AS214762 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,752 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 464 |
| AS201640 | Patryk Kulikowski trading as psHost | Hosting | IPv4 IPv6 | 275 |
| AS218995 | Bobeica Mihaita David | Unclassified | IPv6 | 268 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 240 |
| AS201132 | Mateusz Sikorski trading as MSCode | Hosting | IPv4 IPv6 | 229 |
| AS205941 | Lungu Stefan Gabriel | Unclassified | IPv4 IPv6 | 218 |
| AS198057 | Flooyd Telecom LTDA | Residential | IPv6 | 171 |
| AS219481 | Krzysztof Manczak | Unclassified | IPv4 IPv6 | 169 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 141 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.