subnet.im

45.11.106.0/24

Misaka Network, Inc.AS57695

Misaka Network, Inc.AS35487

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

95%

76 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 26th April 2019

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 45.11.106.0/24 as seen from Amsterdam, read outward from the origin: AS57695 → AS35487 → AS931 → AS137409 → AS213151. Each hop is listed with its network name beneath the graph.AS57695Misaka Network, I…OriginAS35487Misaka Network, I…AS931HyonixAS137409GSL Networks Pty …AS213151Christian Elsen

Seen from Amsterdam

  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 6,918 paths from 2 vantage points
  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. Singapore5769535487931132337This path
  2. Amsterdam5769535487931137409213151Shown above
  3. London, UK57695354879311374098529This path
  4. Sao Paulo5769535487931137409266213This path
  5. Oregon, US5769535487931693920130This 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

95%

Seen by 76 of 80 full-feed vantage points

Globally propagated

Observed at 5 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
26th April 2019
Allocation block
45.11.104.0/22
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 45.11.106.0/24
ROA prefixAuthorised originMax length
45.11.104.0/22AS23961/24
45.11.104.0/22AS57695/24
45.11.104.0/22AS917/24

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 45.11.106.0/24
PrefixAddressesOriginVisibility
45.11.107.0/24256AS969Misaka Network, Inc.79/80

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.

Open 45.11.106.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.