asn.dev

Observed topology

AS15738 UAEXPRESS TOV BF Express Ltd

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15738: 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
AS3255LLC EKSINTECHUnclassifiedIPv484
AS56347Yugtelegroup LtdUnclassifiedIPv4 IPv642
AS6939Hurricane Electric LLCTransitIPv617
AS35297Dataline LLCUnclassifiedIPv48
AS24482SG.GSHostingIPv61
AS29632Netassist International EOODUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47359"Tvoi Net" Ltd.UnclassifiedIPv41,189
AS44695FOP Markovskiy Denis VadimovichUnclassifiedIPv4531
AS34579Soyuz LTDUnclassifiedIPv4329
AS25071RadioCom LtdUnclassifiedIPv4144
AS56386LLC "GREEN-NET"UnclassifiedIPv4122

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv41,518
AS47359"Tvoi Net" Ltd.UnclassifiedIPv41,306
AS56347Yugtelegroup LtdUnclassifiedIPv4 IPv6714
AS44695FOP Markovskiy Denis VadimovichUnclassifiedIPv4531
AS3255LLC EKSINTECHUnclassifiedIPv4403
AS34579Soyuz LTDUnclassifiedIPv4329
AS56386LLC "GREEN-NET"UnclassifiedIPv4194
AS25071RadioCom LtdUnclassifiedIPv4144
AS6939Hurricane Electric LLCTransitIPv617
AS51528KOZOBROD ANDRIY ANATOLIYOVICHUnclassifiedIPv43

All 12 adjacent →

Provenance

Where this comes from

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