subnet.im

64.89.161.0/24

AS403005

Netiface LLCAS36680

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 13th January 2026

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 64.89.161.0/24 as seen from London, UK, read outward from the origin: AS403005 → AS203446 → AS35280. Each hop is listed with its network name beneath the graph.AS403005OriginAS203446SMARTNET Germany …AS35280F5 Networks SARL

Seen from London, UK

  1. 1AS403005Origin
    Adjacentseen on 557 paths from 80 vantage points
  2. Peer of AS203446seen on 239 paths from 2 vantage points
  3. 3AS35280F5 Networks SARLFRVantage 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. Amsterdam4030052034468298This path
  2. London, UK40300520344635280Shown above
  3. Singapore403005203446132337This path
  4. Sao Paulo403005203446423035280This path
  5. Oregon, US4030052034466461693920130This 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 80 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
ARIN — North America
Country
United States
Allocated
13th January 2026
Allocation block
64.89.160.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 64.89.161.0/24
ROA prefixAuthorised originMax length
64.89.161.0/24AS205759/24
64.89.161.0/24AS403005/24
64.89.160.0/23AS36680/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 64.89.161.0/24
PrefixAddressesOriginVisibility
64.89.160.0/24256AS36680Netiface LLC1/81
64.89.160.0/24256AS40300580/81

History

  1. AS40300527th September 2026 — present
  2. AS3668022nd September 2026 — present
  3. AS20575912th August 2026 — 21st September 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 64.89.161.0/24 in the calculator/24 reference

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