SUBNET.IM

2a05:5c00::/29

OPS SarlAS51630

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

97%

60 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCFR

Allocated 12th November 2014

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 2a05:5c00::/29, fanning out from AS51630 toward the vantage points that see it. Each path is written out in full beneath the graph.AS51630OPS SarlOriginAS174Cogent Communicat…AS34549meerfarbig GmbH &…AS213151Christian ElsenAS15576NTS workspace AGAS51907Kanton ZugAS7195EdgeUnoAS32590Valve CorporationAS3215Orange S.A.AS5511Orange S.A.AS6939Hurricane Electri…AS132337Axclusive
  1. Amsterdam5163017434549213151This path
  2. London, UK516301741557651907This path
  3. Sao Paulo51630174719532590This path
  4. Singapore51630321555116939132337This 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

97%

Seen by 60 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
France
Allocated
12th November 2014
Allocation block
2a05:5c00::/29
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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