subnet.im

185.185.40.0/24

HostUSAS7489

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCUS

Allocated 10th January 2017

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 185.185.40.0/24 as seen from London, UK, read outward from the origin: AS7489 → AS49870 → AS137409 → AS8529. Each hop is listed with its network name beneath the graph.AS7489HostUSOriginAS49870Alsycon B.V.AS137409GSL Networks Pty …AS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS7489HostUSUSOrigin
    Peer of AS7489seen on 219 paths from 140 vantage points
  2. 2AS49870Alsycon B.V.NL
    Peer of AS49870seen on 8 paths from 1 vantage point
  3. 3AS137409GSL Networks Pty LTDAU
    Peer of AS137409seen on 91,764 paths from 6 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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. Singapore748949870132337This path
  2. London, UK7489498701374098529Shown above
  3. Oregon, US748949870693920130This path
  4. Amsterdam74894987017434549213151This path
  5. Sao Paulo7489498701743356266213This 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
United States
Allocated
10th January 2017
Allocation block
185.185.40.0/23
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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 185.185.40.0/24
PrefixAddressesOriginVisibility
185.185.41.0/24256AS7489HostUS79/80

History

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

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