subnet.im

2a0a:d685:1ff::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

62 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCCN

Allocated 18th November 2025

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 2a0a:d685:1ff::/48 as seen from Amsterdam, read outward from the origin: AS219332 → AS44324 → AS9515 → AS62217 → AS6461 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS219332Xiang ZhouOriginAS44324MoeDove LLCAS9515Compute Global Li…AS62217Vinters IT LtdAS6461Zayo BandwidthAS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS219332seen on 216 paths from 63 vantage points
  2. Peer of AS44324seen on 1,181 paths from 137 vantage points
  3. Peer of AS9515seen on 1,394 paths from 137 vantage points
  4. Peer of AS62217seen on 1,282 paths from 77 vantage points
  5. Peer of AS6461seen on 132,858 paths from 5 vantage points
  6. Peer of AS25091seen on 664,395 paths from 2 vantage points
  7. 7AS8298IPng Networks GmbHCHVantage 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, UK21933244324951562217646135280This path
  2. Singapore219332443249515622176461132337This path
  3. Amsterdam219332443249515622176461250918298Shown above
  4. Sao Paulo219332443249515622176461645335280This 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 62 of 63 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
China
Allocated
18th November 2025
Allocation block
2a0a:d680::/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 2a0a:d685:1ff::/48
ROA prefixAuthorised originMax length
2a0a:d685:1ff::/48AS219332/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 2a0a:d685:1ff::/48
PrefixAddressesOriginVisibility
2a0a:d685:1fe::/4865.5k × /64AS197817Nyco Cloud Network LLC62/63

History

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