asn.dev

Observed topology

AS42504 UKRBIT-NET-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42504: 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
AS15895"Kyivstar" PJSCMobileIPv458
AS13249PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv4 IPv647
AS41305UkrNet Fastiv Region LTDUnclassifiedIPv416
AS6939Hurricane Electric LLCTransitIPv414
AS35320Eurotranstelecom LtdUnclassifiedIPv46
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS43139Maximum-Net LLCUnclassifiedIPv44
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48437PP "Merezha"UnclassifiedIPv4354
AS57774PP "Merezha"UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS48437PP "Merezha"UnclassifiedIPv4354
AS43139Maximum-Net LLCUnclassifiedIPv4115
AS13249PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv4 IPv6108
AS35320Eurotranstelecom LtdUnclassifiedIPv493
AS15895"Kyivstar" PJSCMobileIPv487
AS41305UkrNet Fastiv Region LTDUnclassifiedIPv479
AS6939Hurricane Electric LLCTransitIPv469
AS57774PP "Merezha"UnclassifiedIPv459
AS3303Swisscom (Schweiz) AGResidentialIPv418
AS24482SG.GSHostingIPv49

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.