subnet.im

2a0a:d840::/29

ITT Desk B.V.AS42383

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

69%

43 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCNL

Allocated 9th May 2017

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 2a0a:d840::/29 as seen from Amsterdam, read outward from the origin: AS42383 → AS8455 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS42383ITT Desk B.V.OriginAS8455atom86 BVAS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. 1AS42383ITT Desk B.V.NLOrigin
    Peer of AS42383seen on 123 paths from 123 vantage points
  2. 2AS8455atom86 BVNL
    Peer of AS8455seen on 1,505 paths from 17 vantage points
  3. 3AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 309,709 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. Singapore423838455132337This path
  2. Amsterdam4238384556939213151Shown above
  3. London, UK423838455900251907This path
  4. Sao Paulo423838455693932590This 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

69%

Seen by 43 of 62 full-feed vantage points

Partially 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
9th May 2017
Allocation block
2a0a:d840::/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.

CoveringMore specific
Prefix hierarchy for 2a0a:d840::/29: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a0a:d840::/29AS42383This prefix2a0a:d840::/32AS42383

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2a0a:d840::/29
PrefixAddressesOriginVisibility
2a0a:d840::/324.3B × /64AS42383ITT Desk B.V.61/62

Sibling prefixes

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

History

  1. AS4238312th 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.