asn.dev

Observed topology

AS48278 UKRDATACOM-NET-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48278: 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
AS35297Dataline LLCUnclassifiedIPv4666
AS29632Netassist International EOODUnclassifiedIPv4252
AS8772Netassist International EOODUnclassifiedIPv4234

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35530Proline TM Ltd.UnclassifiedIPv41,024
AS47678"Sunline.net.ua" LTDUnclassifiedIPv41,024
AS48279Delta-Net LLCUnclassifiedIPv41,024
AS48587PE Zharkov Mukola MukolayovuchUnclassifiedIPv4193
AS47280DZHUVA LTDUnclassifiedIPv464
AS60828LLC "UIP"UnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv42,747
AS35530Proline TM Ltd.UnclassifiedIPv41,216
AS47678"Sunline.net.ua" LTDUnclassifiedIPv41,024
AS48279Delta-Net LLCUnclassifiedIPv41,024
AS29632Netassist International EOODUnclassifiedIPv41,020
AS8772Netassist International EOODUnclassifiedIPv4970
AS48587PE Zharkov Mukola MukolayovuchUnclassifiedIPv4193
AS47280DZHUVA LTDUnclassifiedIPv464
AS60828LLC "UIP"UnclassifiedIPv464

Provenance

Where this comes from

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