subnet.im

85.232.180.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

78 of 78 vantage points

RPKI

Valid

Registry

RIPE NCCSE

Allocated 14th April 2005

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 85.232.180.0/24 as seen from London, UK, read outward from the origin: AS218874 → AS58057 → AS6939 → AS8529. Each hop is listed with its network name beneath the graph.AS218874Achronon LimitedOriginAS58057Securebit AGAS6939Hurricane Electri…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS218874seen on 78 paths from 78 vantage points
  2. Peer of AS58057seen on 3,431 paths from 140 vantage points
  3. Peer of AS6939seen on 234,330 paths from 8 vantage points

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. Amsterdam218874580578298This path
  2. London, UK2188745805769398529Shown above
  3. Sao Paulo218874580573454935280This path
  4. Singapore21887458057244823862323673This path
  5. Oregon, US2188745805734549855142013This 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

100%

Seen by 78 of 78 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
Sweden
Allocated
14th April 2005
Allocation block
85.232.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 85.232.180.0/24
ROA prefixAuthorised originMax length
85.232.180.0/24AS14618/24
85.232.180.0/24AS16509/24
85.232.180.0/24AS218874/24
85.232.180.0/24AS51167/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 85.232.180.0/24
PrefixAddressesOriginVisibility
85.232.181.0/24256AS212238Datacamp Limited77/78

History

  1. AS21887415th October 2026 — present
  2. AS1650915th October 2026 — 15th October 2026
  3. AS1650912th August 2026 — 14th 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 85.232.180.0/24 in the calculator/24 reference

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