asn.dev

Observed topology

AS48789 RFC-INTERNET

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48789: 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 IPv6866
AS6939Hurricane Electric LLCTransitIPv632
AS24482SG.GSHostingIPv4 IPv615
AS5617Orange Polska Spolka AkcyjnaMobileIPv414
AS12618Politechnika Bydgoska im. Jana i Jedrzeja SniadeckichUnclassifiedIPv412
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv44
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv42
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206674Elzbieta Joanna Nakiewicz trading as TelecentrumUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv6929
AS206674Elzbieta Joanna Nakiewicz trading as TelecentrumUnclassifiedIPv465
AS6939Hurricane Electric LLCTransitIPv632
AS24482SG.GSHostingIPv4 IPv616
AS5617Orange Polska Spolka AkcyjnaMobileIPv415
AS12618Politechnika Bydgoska im. Jana i Jedrzeja SniadeckichUnclassifiedIPv412
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv44
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv42
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv62

Provenance

Where this comes from

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