SUBNET.IM

2a14:9d02::/32

Falcon FZE LLCAS208111

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCAE

Allocated 7th January 2025

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 4 observed paths to 2a14:9d02::/32, fanning out from AS208111 toward the vantage points that see it. Each path is written out in full beneath the graph.AS208111Falcon FZE LLCOriginAS213622Falcon FZE LLCAS137409GSL Networks Pty …AS213151Christian ElsenAS51907Kanton ZugAS32590Valve CorporationAS132337Axclusive
  1. Amsterdam208111213622137409213151This path
  2. London, UK20811121362213740951907This path
  3. Sao Paulo20811121362213740932590This path
  4. Singapore208111213622137409132337This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

98%

Seen by 61 of 62 full-feed vantage points

Globally propagated

Observed at 4 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
United Arab Emirates
Allocated
7th January 2025
Allocation block
2a14:9d00::/29
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 2a14:9d02::/32
ROA prefixAuthorised originMax length
2a14:9d02::/32AS208111/32
2a14:9d00::/29AS213622/29

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2a14:9d02::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a14:9d00::/29AS2136222a14:9d02::/32AS208111This prefix

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 2a14:9d02::/32
PrefixAddressesOriginVisibility
2a14:9d00::/2934.4B × /64AS213622Falcon FZE LLC61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS20811112th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Routing data derived from RouteViews MRT archives and public registry data.