subnet.im

2401:1660:3::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICBD

Allocated 10th July 2023

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 2401:1660:3::/48 as seen from Amsterdam, read outward from the origin: AS149019 → AS58717 → AS9002 → AS213151. Each hop is listed with its network name beneath the graph.AS149019Penta-Six Communi…OriginAS58717Summit Communicat…AS9002RETN LimitedAS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS149019seen on 1,270 paths from 138 vantage points
  2. Peer of AS58717seen on 41,554 paths from 87 vantage points
  3. Peer of AS9002seen on 4,831 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. Singapore14901958682132337This path
  2. Amsterdam149019587179002213151Shown above
  3. London, UK14901958717693951907This path
  4. Sao Paulo14901958717949832590This 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
APNIC — Asia-Pacific
Country
Bangladesh
Allocated
10th July 2023
Allocation block
2401:1660::/32
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 2401:1660:3::/48
ROA prefixAuthorised originMax length
2401:1660:3::/48AS149019/48
2401:1660::/32AS149019/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

Prefixes of the same length sharing a parent block with 2401:1660:3::/48
PrefixAddressesOriginVisibility
2401:1660:2::/4865.5k × /64AS149019Penta-Six Communication61/62

History

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