subnet.im

2a10:ccc1:495::/48

The Constant Company, LLCAS20473

At a glance

Subnets

65,536 × /64

/48 block

Visibility

64%

41 of 64 vantage points

RPKI

No ROA

Registry

RIPE NCCCH

Allocated 1st April 2021

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 2a10:ccc1:495::/48 as seen from London, UK, read outward from the origin: AS20473 → AS2914 → AS35280. Each hop is listed with its network name beneath the graph.AS20473The Constant Comp…OriginAS2914NTT America, Inc.AS35280F5 Networks SARL

Seen from London, UK

  1. 1AS20473The Constant Company, LLCUSOrigin
    Peer of AS20473seen on 81,423 paths from 140 vantage points
  2. 2AS2914NTT America, Inc.US
    Peer of AS2914seen on 441,193 paths from 6 vantage points
  3. 3AS35280F5 Networks SARLFRVantage 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, UK20473291435280Shown above
  2. Sao Paulo20473291435280This path
  3. Amsterdam204732914250918298This 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

64%

Seen by 41 of 64 full-feed vantage points

Partially propagated

Observed at 3 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
Switzerland
Allocated
1st April 2021
Allocation block
2a10:ccc0::/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

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

History

  1. AS2047312th November 2026 — present
  2. AS2047310th November 2026 — 10th November 2026
  3. AS204731st November 2026 — 1st November 2026
  4. AS2047328th October 2026 — 28th October 2026
  5. AS2047314th October 2026 — 14th October 2026
  6. AS204736th October 2026 — 6th October 2026
  7. AS2047329th September 2026 — 4th October 2026
  8. AS2047324th September 2026 — 24th September 2026
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.