subnet.im

92.118.232.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCCY

Allocated 7th March 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 92.118.232.0/24 as seen from Amsterdam, read outward from the origin: AS212171 → AS213887 → AS30823 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS212171Local NCC Ltd.OriginAS213887WAIcore LtdAS30823aurologic GmbHAS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS212171seen on 1,943 paths from 81 vantage points
  2. Peer of AS213887seen on 9,905 paths from 145 vantage points
  3. Peer of AS30823seen on 1,005 paths from 5 vantage points
  4. Peer of AS25091seen on 666,368 paths from 2 vantage points
  5. 5AS8298IPng Networks GmbHCHVantage 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. Singapore21217121388730823132337This path
  2. Amsterdam21217121388730823250918298Shown above
  3. London, UK21217121388730823129935280This path
  4. Sao Paulo21217121388730823291435280This path
  5. Oregon, US21217121388730823693920130This 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 81 of 81 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
Cyprus
Allocated
7th March 2019
Allocation block
92.118.232.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 92.118.232.0/24
ROA prefixAuthorised originMax length
92.118.232.0/24AS212171/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 92.118.232.0/24
PrefixAddressesOriginVisibility
92.118.233.0/24256AS212171Local NCC Ltd.81/81

History

  1. AS21217124th September 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 92.118.232.0/24 in the calculator/24 reference

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