SUBNET.IM

2a09:80::/29

SIA ServerumAS59615

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCLV

Allocated 26th November 2018

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2a09:80::/29 as seen from London, UK, read outward from the origin: AS59615 → AS43317 → AS20764 → AS51907. Each hop is listed with its network name beneath the graph.AS59615SIA ServerumOriginAS43317SIA VEESPAS20764CJSC RASCOMAS51907Kanton Zug

Seen from London, UK

  1. 1AS59615SIA ServerumLVOrigin
    Peer of AS59615seen on 141 paths from 141 vantage points
  2. 2AS43317SIA VEESPLV
    Peer of AS43317seen on 389 paths from 112 vantage points
  3. 3AS20764CJSC RASCOMRU
    Peer of AS20764seen on 5,396 paths from 2 vantage points
  4. 4AS51907Kanton ZugCHVantage 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. Amsterdam596154331720764213151This path
  2. London, UK59615433172076451907Shown above
  3. Sao Paulo5961543317693932590This path
  4. Singapore596154331720764132337This 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

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
Latvia
Allocated
26th November 2018
Allocation block
2a09:80::/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 2a09:80::/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.2a09:80::/29AS59615This prefix2a09:81::/32AS59615

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 2a09:80::/29
PrefixAddressesOriginVisibility
2a09:81::/324.3B × /64AS59615SIA Serverum62/62

Sibling prefixes

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

History

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