asn.dev

Observed topology

AS28824 ASN-EMPSECURE EMP Secure AS

Hosting RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28824: 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
AS50304Blix Solutions ASUnclassifiedIPv4 IPv687
AS1299Arelion Sweden ABTransitIPv4 IPv664
AS6939Hurricane Electric LLCTransitIPv427
AS8896GLOBALCONNECT ASUnclassifiedIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv64
AS34927iFog GmbHHostingIPv4 IPv64
AS57381Daniel HusandUnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41049Xait ASUnclassifiedIPv4143

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS41049Xait ASUnclassifiedIPv4143
AS1299Arelion Sweden ABTransitIPv4 IPv6136
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6120
AS6939Hurricane Electric LLCTransitIPv456
AS8896GLOBALCONNECT ASUnclassifiedIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv67
AS34927iFog GmbHHostingIPv4 IPv67
AS57381Daniel HusandUnclassifiedIPv4 IPv67

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.