SUBNET.IM

2a05:ec0::/29

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCNO

Allocated 15th August 2014

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 2a05:ec0::/29 as seen from Amsterdam, read outward from the origin: AS56828 → AS2116 → AS12552 → AS213151. Each hop is listed with its network name beneath the graph.AS56828Norsk Helsenett SFOriginAS2116GLOBALCONNECT ASAS12552GlobalConnect (IP…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS56828seen on 180 paths from 42 vantage points
  2. Peer of AS2116seen on 13,260 paths from 106 vantage points
  3. Peer of AS12552seen on 3,460 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. London, UK56828211951907This path
  2. Amsterdam56828211612552213151Shown above
  3. Sao Paulo568282119719532590This path
  4. Singapore56828211612552132337This 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

100%

Seen by 62 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
Norway
Allocated
15th August 2014
Allocation block
2a05:ec0::/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 2a05:ec0::/29
ROA prefixAuthorised originMax length
2a05:ec0::/29AS56828/29

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