subnet.im

213.249.92.0/22

Metaregistrar B.V.AS42585

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 20th January 2006

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 213.249.92.0/22 as seen from Amsterdam, read outward from the origin: AS42585 → AS30870 → AS20495 → AS9136 → AS213151. Each hop is listed with its network name beneath the graph.AS42585Metaregistrar B.V.OriginAS30870Trans-iX B.V.AS20495We Dare B.V.AS9136WOBCOM GmbHAS213151Christian Elsen

Seen from Amsterdam

  1. 1AS42585Metaregistrar B.V.NLOrigin
    Peer of AS42585seen on 362 paths from 141 vantage points
  2. 2AS30870Trans-iX B.V.NL
    Peer of AS30870seen on 118 paths from 5 vantage points
  3. 3AS20495We Dare B.V.NL
    Peer of AS20495seen on 483 paths from 38 vantage points
  4. 4AS9136WOBCOM GmbHDE
    Peer of AS9136seen on 233 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. Singapore4258530870132337This path
  2. London, UK42585308701374098529This path
  3. Oregon, US4258530870693920130This path
  4. Amsterdam4258530870204959136213151Shown above
  5. Sao Paulo4258530870491273356266213This 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 80 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
Netherlands
Allocated
20th January 2006
Allocation block
213.249.64.0/19
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 213.249.92.0/22
ROA prefixAuthorised originMax length
213.249.92.0/22AS42585/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

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

History

  1. AS4258512th 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 213.249.92.0/22 in the calculator/22 reference

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