subnet.im

2001:df7:7800::/49

At a glance

Subnets

32,768 × /64

/49 block

Visibility

6%

4 of 62 vantage points

RPKI

No ROA

Registry

APNICJP

Allocated 11th July 2014

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2001:df7:7800::/49 as seen from Singapore, read outward from the origin: AS17523 → AS2907 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS17523Aoyama Gakuin Uni…OriginAS2907Science Informati…AS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. Peer of AS17523seen on 168 paths from 84 vantage points
  2. Peer of AS2907seen on 15 paths from 2 vantage points
  3. Peer of AS8966seen on 133,632 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Singapore1752329078966132337Shown 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.

Route visibility

6%

Seen by 4 of 62 full-feed vantage points

Seen by few vantage points

Observed at 1 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
Japan
Allocated
11th July 2014
Allocation block
2001:df7:7800::/48
Status
assigned
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.

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 2001:df7:7800::/49
PrefixAddressesOriginVisibility
2001:df7:7800:8000::/4932.8k × /64AS17523Aoyama Gakuin University4/62

History

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