subnet.im

195.216.164.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCES

Allocated 3rd October 1997

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 195.216.164.0/24 as seen from London, UK, read outward from the origin: AS213607 → AS56630 → AS6762 → AS8529. Each hop is listed with its network name beneath the graph.AS213607WORLD FIRST COMMU…OriginAS56630Melbikomas UABAS6762Telecom Italia Sp…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS213607seen on 476 paths from 80 vantage points
  2. Peer of AS56630seen on 1,210 paths from 46 vantage points
  3. Peer of AS6762seen on 33,111 paths from 1 vantage 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. Singapore21360756630132337This path
  2. Amsterdam2136075663034549213151This path
  3. London, UK2136075663067628529Shown above
  4. Sao Paulo213607566303356266213This path
  5. Oregon, US21360756630693920130This 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 79 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
Spain
Allocated
3rd October 1997
Allocation block
195.216.160.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 195.216.164.0/24
ROA prefixAuthorised originMax length
195.216.164.0/24AS213607/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 195.216.164.0/24
PrefixAddressesOriginVisibility
195.216.165.0/24256AS32043NeoFiber Communications inc.80/80

History

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

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