subnet.im

164.37.235.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCPL

Allocated 31st January 1993

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 164.37.235.0/24 as seen from Amsterdam, read outward from the origin: AS152606 → AS401322 → AS174 → AS6762 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS152606LINK4 COMMUNICATI…OriginAS401322NetO CorpAS174Cogent Communicat…AS6762Telecom Italia Sp…AS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS152606seen on 996 paths from 76 vantage points
  2. Peer of AS401322seen on 4,305 paths from 75 vantage points
  3. Peer of AS174seen on 178,349 paths from 22 vantage points
  4. Peer of AS6762seen on 251,398 paths from 5 vantage points
  5. Peer of AS25091seen on 663,280 paths from 2 vantage points
  6. 6AS8298IPng 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. London, UK15260640132217412998529This path
  2. Sao Paulo152606401322174645335280This path
  3. Singapore152606401322174335623673This path
  4. Oregon, US152606401322174855142013This path
  5. Amsterdam1526064013221746762250918298Shown above

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

99%

Seen by 75 of 76 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
Poland
Allocated
31st January 1993
Allocation block
164.37.192.0/18
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 164.37.235.0/24
ROA prefixAuthorised originMax length
164.37.235.0/24AS152606/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 164.37.235.0/24
PrefixAddressesOriginVisibility
164.37.234.0/24256AS219447HONG KONG FLASH SPEED LIMITED76/76

History

  1. AS15260625th October 2026 — present
  2. AS930422nd September 2026 — 24th October 2026
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 164.37.235.0/24 in the calculator/24 reference

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