subnet.im

2a13:d140::/29

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

97%

62 of 64 vantage points

RPKI

Valid

Registry

RIPE NCCLT

Allocated 5th September 2023

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 2a13:d140::/29 as seen from Amsterdam, read outward from the origin: AS214266 → AS62610 → AS21859 → AS4229 → AS3257 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS214266ZERODESK LTDOriginAS62610Zenlayer IncAS21859Zenlayer IncAS4229Zenlayer IncAS3257GTT Communication…AS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS214266seen on 2,492 paths from 64 vantage points
  2. Peer of AS62610seen on 68,306 paths from 142 vantage points
  3. Peer of AS21859seen on 219,735 paths from 142 vantage points
  4. Peer of AS4229seen on 7,545 paths from 131 vantage points
  5. Peer of AS3257seen on 40,200 paths from 5 vantage points
  6. Peer of AS25091seen on 663,779 paths from 2 vantage points
  7. 7AS8298IPng Networks GmbHCHVantage 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. Singapore214266626102185942296939132337This path
  2. Amsterdam214266626102185942293257250918298Shown above
  3. London, UK214266626102185942293257335635280This path
  4. Sao Paulo214266626102185942293257645335280This 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 62 of 64 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
Lithuania
Allocated
5th September 2023
Allocation block
2a13:d140::/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 2a13:d140::/29
ROA prefixAuthorised originMax length
2a13:d140::/29AS214266/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. AS21426612th 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.