SUBNET.IM

2a13:1c0::/64

SAFECLOUDBOX SASAS59721

At a glance

Subnets

1 × /64

/64 block

Visibility

8%

5 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 12th October 2022

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 2a13:1c0::/64 as seen from Singapore, read outward from the origin: AS59721 → AS2914 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS59721SAFECLOUDBOX SASOriginAS2914NTT America, Inc.AS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. 1AS59721SAFECLOUDBOX SASFROrigin
    Peer of AS59721seen on 125 paths from 30 vantage points
  2. 2AS2914NTT America, Inc.US
    Peer of AS2914seen on 60,369 paths from 3 vantage points
  3. 3AS8966Etisalat (E&)AE
    Peer of AS8966seen on 133,632 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. Singapore5972129148966132337Shown above

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.

Route visibility

8%

Seen by 5 of 62 full-feed vantage points

Seen by few vantage points

Observed at 2 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 October 2022
Allocation block
2a13:1c0::/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:1c0::/64
ROA prefixAuthorised originMax length
2a13:1c0::/64AS59721/64

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