subnet.im

164.37.236.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.236.0/24 as seen from Amsterdam, read outward from the origin: AS207267 → AS210538 → AS219384 → AS208972 → AS6204 → AS8298. Each hop is listed with its network name beneath the graph.AS207267IBRAHIM POYRAZOGLUOriginAS210538KEYUBU Internet v…AS219384Satcore LLCAS208972GIBIRNet IletisimAS6204INTERKVM HOST SRLAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS207267seen on 375 paths from 75 vantage points
  2. Peer of AS210538seen on 2,655 paths from 76 vantage points
  3. Peer of AS219384seen on 2,370 paths from 70 vantage points
  4. Peer of AS208972seen on 39,077 paths from 135 vantage points
  5. Peer of AS6204seen on 1,426 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. Amsterdam20726721053821938420897262048298Shown above
  2. London, UK20726721053821938420897262048529This path
  3. Oregon, US207267210538219384208972693920130This path
  4. Sao Paulo2072672105382193842089726204291435280This path
  5. Singapore207267210538219384208972244823862323673This 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

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.236.0/24
ROA prefixAuthorised originMax length
164.37.236.0/24AS207267/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.236.0/24
PrefixAddressesOriginVisibility
164.37.237.0/24256AS42954Vivi 23 Co.,Ltd76/76

History

  1. AS20726727th 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 164.37.236.0/24 in the calculator/24 reference

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