subnet.im

2a04:1b00:2::/48

OpenTLD BVAS61007

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCNL

Allocated 14th March 2013

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 2a04:1b00:2::/48 as seen from London, UK, read outward from the origin: AS61007 → AS60679 → AS48921 → AS24971 → AS9002 → AS51907. Each hop is listed with its network name beneath the graph.AS61007OpenTLD BVOriginAS60679Freedom Registry …AS48921Yoursafe Holding …AS24971MasterDC s.r.o.AS9002RETN LimitedAS51907Kanton Zug

Seen from London, UK

  1. 1AS61007OpenTLD BVNLOrigin
    Peer of AS61007seen on 780 paths from 142 vantage points
  2. 2AS60679Freedom Registry BVNL
    Peer of AS60679seen on 930 paths from 75 vantage points
  3. 3AS48921Yoursafe Holding B.V.NL
    Peer of AS48921seen on 843 paths from 81 vantage points
  4. 4AS24971MasterDC s.r.o.CZ
    Peer of AS24971seen on 3,829 paths from 83 vantage points
  5. 5AS9002RETN LimitedGB
    Peer of AS9002seen on 325,294 paths from 2 vantage points
  6. 6AS51907Kanton ZugCHVantage 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. Sao Paulo610076067948921335632590This path
  2. Amsterdam610076067948921249719002213151This path
  3. London, UK61007606794892124971900251907Shown above
  4. Singapore610076067948921249719002132337This 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

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
Netherlands
Allocated
14th March 2013
Allocation block
2a04:1b00::/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

Prefixes of the same length sharing a parent block with 2a04:1b00:2::/48
PrefixAddressesOriginVisibility
2a04:1b00:3::/4865.5k × /64AS61007OpenTLD BV62/62

History

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