subnet.im

2001:1a18::/29

University of CyprusAS209617

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCCY

Allocated 29th January 2004

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 2001:1a18::/29 as seen from Singapore, read outward from the origin: AS209617 → AS15805 → AS6758 → AS132337. Each hop is listed with its network name beneath the graph.AS209617University of Cyp…OriginAS15805EPIC LTDAS6758Monaco Telecom S.…AS132337Axclusive

Seen from Singapore

  1. 1AS209617University of CyprusCYOrigin
    Peer of AS209617seen on 169 paths from 110 vantage points
  2. 2AS15805EPIC LTDCY
    Peer of AS15805seen on 10,092 paths from 141 vantage points
  3. 3AS6758Monaco Telecom S.A.MC
    Peer of AS6758seen on 238 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Amsterdam20961735432213151This path
  2. Singapore209617158056758132337Shown above
  3. London, UK209617158056758900251907This path
  4. Sao Paulo209617158056758693932590This 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
Cyprus
Allocated
29th January 2004
Allocation block
2001:1a18::/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

Prefixes of the same length sharing a parent block with 2001:1a18::/29
PrefixAddressesOriginVisibility
2001:1a10::/2934.4B × /64AS8781Ooredoo Q.S.C.62/62

History

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