subnet.im

2401:ed20:83::/48

N963 PTE. LTD.AS963

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

APNICSG

Allocated 10th February 2025

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 2401:ed20:83::/48 as seen from London, UK, read outward from the origin: AS963 → AS3257 → AS9002 → AS51907. Each hop is listed with its network name beneath the graph.AS963N963 PTE. LTD.OriginAS3257GTT Communication…AS9002RETN LimitedAS51907Kanton Zug

Seen from London, UK

  1. 1AS963N963 PTE. LTD.SGOrigin
    Peer of AS963seen on 1,909 paths from 98 vantage points
  2. 2AS3257GTT Communications Inc.US
    Peer of AS3257seen on 334,233 paths from 27 vantage points
  3. 3AS9002RETN LimitedGB
    Peer of AS9002seen on 325,294 paths from 2 vantage points
  4. 4AS51907Kanton 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. Amsterdam9636939213151This path
  2. Sao Paulo963719532590This path
  3. Singapore9636939132337This path
  4. London, UK9633257900251907Shown above

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
Singapore
Allocated
10th February 2025
Allocation block
2401:ed20::/32
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.

CoveringMore specific
Prefix hierarchy for 2401:ed20:83::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2401:ed20::/32AS9632401:ed20:83::/48AS963This prefix2401:ed20:82::/48AS963

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 2401:ed20:83::/48
PrefixAddressesOriginVisibility
2401:ed20::/324.3B × /64AS963N963 PTE. LTD.61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2401:ed20:83::/48
PrefixAddressesOriginVisibility
2401:ed20:82::/4865.5k × /64AS963N963 PTE. LTD.61/62

History

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