asn.dev

Observed topology

AS49888 ULTRANET-AS

Unclassified RIPE Cable/DSL/ISP

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 7
Upstream graph Who carries AS49888, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS49888 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv635
AS24724Atman Sp. z o.o.HostingIPv4 IPv631
AS12741Netia SAResidentialIPv4 IPv616
AS3356Level 3 Parent, LLCTransitIPv49
AS174Cogent Communications, LLCTransitIPv45
AS12912T-Mobile Polska S.A.UnclassifiedIPv63
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv61

Transit

Downstream networks

inferred

Networks for which AS49888 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS209802Neurosoft Sp. z o.o.UnclassifiedIPv456

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS49888 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv671
AS209802Neurosoft Sp. z o.o.UnclassifiedIPv456
AS24724Atman Sp. z o.o.HostingIPv4 IPv641
AS12741Netia SAResidentialIPv4 IPv616
AS3356Level 3 Parent, LLCTransitIPv412
AS174Cogent Communications, LLCTransitIPv410
AS12912T-Mobile Polska S.A.UnclassifiedIPv63
AS24482SG.GSHostingIPv4 IPv63
AS29632Netassist International EOODUnclassifiedIPv62
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv41

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.