Observed topology
AS49888 ULTRANET-AS Ultranet Sp. z o.o.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49888: 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 |
|---|---|---|---|---|
| AS29535 | Orange Polska Spolka Akcyjna | Unclassified | IPv4 IPv6 | 34 |
| AS24724 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 26 |
| AS12741 | Netia SA | Residential | IPv4 IPv6 | 23 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 9 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 4 |
| AS12912 | T-Mobile Polska S.A. | Unclassified | IPv6 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS49888 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209802 | Neurosoft Sp. z o.o. | Unclassified | IPv4 | 57 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49888 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29535 | Orange Polska Spolka Akcyjna | Unclassified | IPv4 IPv6 | 67 |
| AS209802 | Neurosoft Sp. z o.o. | Unclassified | IPv4 | 57 |
| AS24724 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 38 |
| AS12741 | Netia SA | Residential | IPv4 IPv6 | 23 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 13 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 8 |
| AS12912 | T-Mobile Polska S.A. | Unclassified | IPv4 IPv6 | 5 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS50607 | Stowarzyszenie e-Poludnie | Unclassified | IPv4 | 1 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 1 |
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.