subnet.im

2a0d:2681:4e00::/40

Rohmad KurniadinAS210842

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

92%

57 of 62 vantage points

RPKI

Invalid

Registry

RIPE NCCNL

Allocated 31st January 2018

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 2a0d:2681:4e00::/40 as seen from London, UK, read outward from the origin: AS210842 → AS53667 → AS174 → AS15576 → AS51907. Each hop is listed with its network name beneath the graph.AS210842Rohmad KurniadinOriginAS53667FranTech SolutionsAS174Cogent Communicat…AS15576NTS workspace AGAS51907Kanton Zug

Seen from London, UK

  1. 1AS210842Rohmad KurniadinIDOrigin
    Peer of AS210842seen on 2,010 paths from 62 vantage points
  2. 2AS53667FranTech SolutionsUS
    Peer of AS53667seen on 9,274 paths from 138 vantage points
  3. 3AS174Cogent Communications, LLCUS
    Peer of AS174seen on 147,033 paths from 3 vantage points
  4. 4AS15576NTS workspace AGCH
    Peer of AS15576seen on 442,038 paths from 2 vantage points
  5. 5AS51907Kanton 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. Singapore21084253667174132337This path
  2. Amsterdam2108425366717434549213151This path
  3. London, UK210842536671741557651907Shown above
  4. Sao Paulo21084253667174719532590This 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

92%

Seen by 57 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Netherlands
Allocated
31st January 2018
Allocation block
2a0d:2680::/29
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2a0d:2681:4e00::/40
ROA prefixAuthorised originMax length
2a0d:2681::/32AS219283/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 2a0d:2681:4e00::/40
PrefixAddressesOriginVisibility
2a0d:2681:4f00::/4016.8M × /64AS210842Rohmad Kurniadin57/62

History

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