SUBNET.IM

2a00:ccc5::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 29th March 2012

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 2a00:ccc5::/32 as seen from Sao Paulo, read outward from the origin: AS60461 → AS57433 → AS6939 → AS32590. Each hop is listed with its network name beneath the graph.AS60461intercolo GmbHOriginAS57433intercolo GmbHAS6939Hurricane Electri…AS32590Valve Corporation

Seen from Sao Paulo

  1. Peer of AS60461seen on 140 paths from 140 vantage points
  2. Peer of AS57433seen on 195 paths from 42 vantage points
  3. Peer of AS6939seen on 335,352 paths from 8 vantage points
  4. 4AS32590Valve CorporationUSVantage 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. Amsterdam60461574336939213151This path
  2. London, UK6046157433693951907This path
  3. Sao Paulo6046157433693932590Shown above
  4. Singapore60461574336939132337This 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
Germany
Allocated
29th March 2012
Allocation block
2a00:ccc0::/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:ccc5::/32
ROA prefixAuthorised originMax length
2a00:ccc5::/32AS60461/128
2a00:ccc5::/32AS62294/32
2a00:ccc0::/29AS57433/128
2a00:ccc0::/29AS59592/128

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:ccc5::/32
PrefixAddressesOriginVisibility
2a00:ccc4::/324.3B × /64AS59592intercolo GmbH61/62

History

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