subnet.im

2404::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICTW

Allocated 25th January 2006

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 2404::/32 as seen from Amsterdam, read outward from the origin: AS17709 → AS4780 → AS9002 → AS213151. Each hop is listed with its network name beneath the graph.AS17709Asia Pacific Tele…OriginAS4780Digital United In…AS9002RETN LimitedAS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS17709seen on 110,960 paths from 142 vantage points
  2. Peer of AS4780seen on 175,203 paths from 141 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. Singapore17709132337This path
  2. Sao Paulo17709693932590This path
  3. Amsterdam1770947809002213151Shown above
  4. London, UK177094780900251907This 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
Taiwan
Allocated
25th January 2006
Allocation block
2404::/26
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 2404::/32
ROA prefixAuthorised originMax length
2404::/26AS17709/48

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2404::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2404::/26AS177092404::/32AS17709This prefix2404:0:2000::/36AS74822404:0:4000::/36AS93112404:0:6000::/36AS241552404:0:7000::/36AS1311422404:0:8000::/36AS131591+16 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 2404::/32
PrefixAddressesOriginVisibility
2404::/26275B × /64AS17709Asia Pacific Telecom61/62

More specific announcements

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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