SUBNET.IM

2a0b:ec00::/29

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 24th August 2016

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Amsterdam.

OriginVantage point · Amsterdam
One AS path to 2a0b:ec00::/29 as seen from Amsterdam, read outward from the origin: AS34373 → AS24785 → AS20562 → AS213151. Each hop is listed with its network name beneath the graph.AS34373XXLnet B.V.OriginAS24785Joint Transit (Br…AS20562Open Peering (Bro…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS34373seen on 404 paths from 37 vantage points
  2. Peer of AS24785seen on 14,265 paths from 85 vantage points
  3. Peer of AS20562seen on 2,358 paths from 2 vantage points
  4. 4AS213151Christian ElsenDEVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore34373132337This path
  2. London, UK343734335051907This path
  3. Sao Paulo34373693932590This path
  4. Amsterdam343732478520562213151Shown above

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
Netherlands
Allocated
24th August 2016
Allocation block
2a0b:ec00::/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 2a0b:ec00::/29
ROA prefixAuthorised originMax length
2a0b:ec00::/29AS34373/48

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

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. AS3437312th 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.