subnet.im

2a12:8d05::/32

Misaka Network, Inc.AS57695

Misaka Network, Inc.AS35487

Announced by more than one origin AS (MOAS).

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

94%

58 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 15th November 2021

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 2a12:8d05::/32 as seen from Sao Paulo, read outward from the origin: AS57695 → AS35487 → AS931 → AS137409 → AS32590. Each hop is listed with its network name beneath the graph.AS57695Misaka Network, I…OriginAS35487Misaka Network, I…AS931HyonixAS137409GSL Networks Pty …AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS57695Misaka Network, Inc.USOrigin
    Peer of AS57695seen on 253 paths from 137 vantage points
  2. 2AS35487Misaka Network, Inc.US
    Peer of AS35487seen on 185 paths from 128 vantage points
  3. 3AS931HyonixSG
    Peer of AS931seen on 17,104 paths from 141 vantage points
  4. 4AS137409GSL Networks Pty LTDAU
    Peer of AS137409seen on 39,434 paths from 8 vantage points
  5. 5AS32590Valve CorporationUSVantage 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. Amsterdam5769535487931137409213151This path
  2. London, UK576953548793113740951907This path
  3. Sao Paulo576953548793113740932590Shown above
  4. Singapore5769535487931137409132337This 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

94%

Seen by 58 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
United States
Allocated
15th November 2021
Allocation block
2a12:8d00::/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 2a12:8d05::/32
ROA prefixAuthorised originMax length
2a12:8d00::/29AS57695/48
2a12:8d00::/29AS917/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

No prefix of the same length in the same parent block is announced.

History

  1. AS3548712th August 2026 — present
  2. AS5769512th 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.