subnet.im

2a03:4600::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 4th February 2011

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 2a03:4600::/32 as seen from Amsterdam, read outward from the origin: AS44334 → AS30972 → AS8218 → AS213151. Each hop is listed with its network name beneath the graph.AS44334M6 Distribution D…OriginAS30972Bedrock SASAS8218Zayo EuropeAS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS44334seen on 102 paths from 59 vantage points
  2. Peer of AS30972seen on 116 paths from 30 vantage points
  3. Peer of AS8218seen on 78 paths from 1 vantage point
  4. 4AS213151Christian ElsenDEVantage 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, UK44334900251907This path
  2. Sao Paulo44334335632590This path
  3. Amsterdam44334309728218213151Shown above
  4. Singapore44334309728218132337This 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

97%

Seen by 60 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
4th February 2011
Allocation block
2a03:4600::/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 2a03:4600::/32
ROA prefixAuthorised originMax length
2a03:4600::/29AS44334/32

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