subnet.im

2a00:ec83::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 31st May 2011

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 2a00:ec83::/32 as seen from Singapore, read outward from the origin: AS15890 → AS15557 → AS2914 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS15890Societe Francaise…OriginAS15557SFR SAAS2914NTT America, Inc.AS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. Peer of AS15890seen on 62 paths from 62 vantage points
  2. Peer of AS15557seen on 6,686 paths from 142 vantage points
  3. Peer of AS2914seen on 24,785 paths from 24 vantage points
  4. Peer of AS6939seen on 320,794 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. London, UK1589015557900251907This path
  2. Sao Paulo1589015557676232590This path
  3. Amsterdam158901555717434549213151This path
  4. Singapore158901555729146939132337Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 62 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
France
Allocated
31st May 2011
Allocation block
2a00:ec80::/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 2a00:ec83::/32
ROA prefixAuthorised originMax length
2a00:ec83::/32AS15890/32
2a00:ec80::/29AS198949/48

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 2a00:ec83::/32
PrefixAddressesOriginVisibility
2a00:ec82::/324.3B × /64AS34860Societe Francaise Du Radiotelephone - SFR SA62/62

History

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