subnet.im

2a0d:d940:2011::/48

Maksims DoronkinsAS199277

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCRU

Allocated 8th November 2024

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:d940:2011::/48 as seen from London, UK, read outward from the origin: AS199277 → AS6517 → AS198064 → AS6204 → AS51907. Each hop is listed with its network name beneath the graph.AS199277Maksims DoronkinsOriginAS6517LAKENETWORKSAS198064ZEROPACKETS LTDAS6204INTERKVM HOST SRLAS51907Kanton Zug

Seen from London, UK

  1. 1AS199277Maksims DoronkinsLVOrigin
    Peer of AS199277seen on 222 paths from 62 vantage points
  2. 2AS6517LAKENETWORKS US
    Peer of AS6517seen on 497 paths from 113 vantage points
  3. 3AS198064ZEROPACKETS LTDGB
    Peer of AS198064seen on 337 paths from 112 vantage points
  4. 4AS6204INTERKVM HOST SRLRO
    Peer of AS6204seen on 350 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. Amsterdam19927765171980646204213151This path
  2. London, UK1992776517198064620451907Shown above
  3. Sao Paulo199277651756786676232590This path
  4. Singapore19927765171980646204132337This 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

97%

Seen by 60 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
Russia
Allocated
8th November 2024
Allocation block
2a0d:d940::/29
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 2a0d:d940:2011::/48
ROA prefixAuthorised originMax length
2a0d:d940:2011::/48AS199277/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:d940:2011::/48
PrefixAddressesOriginVisibility
2a0d:d940:2010::/4865.5k × /64AS200386Igor Iamolov62/62

History

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