subnet.im

2001:df5:5e80::/48

KAMAR LimitedAS141413

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICNZ

Allocated 15th November 2020

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 2001:df5:5e80::/48 as seen from Amsterdam, read outward from the origin: AS141413 → AS9790 → AS9507 → AS9002 → AS213151. Each hop is listed with its network name beneath the graph.AS141413KAMAR LimitedOriginAS9790Two Degrees Netwo…AS9507NextHop Pty LtdAS9002RETN LimitedAS213151Christian Elsen

Seen from Amsterdam

  1. 1AS141413KAMAR LimitedNZOrigin
    Peer of AS141413seen on 284 paths from 142 vantage points
  2. 2AS9790Two Degrees Networks LimitedNZ
    Peer of AS9790seen on 21,637 paths from 92 vantage points
  3. 3AS9507NextHop Pty LtdAU
    Peer of AS9507seen on 8,765 paths from 69 vantage points
  4. 4AS9002RETN LimitedGB
    Peer of AS9002seen on 4,831 paths from 1 vantage point
  5. 5AS213151Christian 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. London, UK1414139790693951907This path
  2. Singapore14141397906939132337This path
  3. Amsterdam141413979095079002213151Shown above
  4. Sao Paulo1414139790950790021295632590This 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

100%

Seen by 62 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
New Zealand
Allocated
15th November 2020
Allocation block
2001:df5:5e80::/48
Status
assigned
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 2001:df5:5e80::/48
ROA prefixAuthorised originMax length
2001:df5:5e80::/48AS141413/48

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:df5:5e80::/48
PrefixAddressesOriginVisibility
2001:df5:5e81::/4865.5k × /64AS141413KAMAR Limited62/62

History

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