subnet.im

2a06:9801:3fe::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

62 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 2nd February 2026

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 2a06:9801:3fe::/48 as seen from Amsterdam, read outward from the origin: AS201182 → AS209735 → AS6939 → AS8298. Each hop is listed with its network name beneath the graph.AS201182IT Uoga MBOriginAS209735Lagrange Cloud Te…AS6939Hurricane Electri…AS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS201182seen on 124 paths from 62 vantage points
  2. Peer of AS209735seen on 13,809 paths from 67 vantage points
  3. Peer of AS6939seen on 130,681 paths from 2 vantage points
  4. 4AS8298IPng 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. Amsterdam20118220973569398298Shown above
  2. London, UK201182209735693935280This path
  3. Sao Paulo201182209735693935280This path
  4. Singapore2011822097356939132337This 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
United Kingdom
Allocated
2nd February 2026
Allocation block
2a06:9800::/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 2a06:9801:3fe::/48
ROA prefixAuthorised originMax length
2a06:9801:3fe::/48AS201182/48
2a06:9801:300::/40AS201182/40

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 2a06:9801:3fe::/48
PrefixAddressesOriginVisibility
2a06:9801:3ff::/4865.5k × /64AS201182IT Uoga MB63/63

History

  1. AS2011824th October 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.