subnet.im

5.181.87.0/24

At a glance

Addresses

256

/24 block

Visibility

26%

20 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 2nd April 2019

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 5.181.87.0/24 as seen from London, UK, read outward from the origin: AS211422 → AS44547 → AS208972 → AS5511 → AS8452 → AS8966 → AS8529. Each hop is listed with its network name beneath the graph.AS211422Emre AydoganOriginAS44547NETUNDWEB TELEKOM…AS208972GIBIRNet IletisimAS5511Orange S.A.AS8452Telecom EgyptAS8966Etisalat (E&)AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS211422seen on 1,087 paths from 76 vantage points
  2. Peer of AS44547seen on 816 paths from 119 vantage points
  3. Peer of AS208972seen on 1,929 paths from 25 vantage points
  4. Peer of AS5511seen on 36 paths from 4 vantage points
  5. Peer of AS8452seen on 111 paths from 6 vantage points
  6. Peer of AS8966seen on 5,361 paths from 2 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. Amsterdam21142244547208972502638298This path
  2. Oregon, US211422445472089726204855142013This path
  3. London, UK211422445472089725511845289668529Shown above
  4. Sao Paulo2114224454720897255118452896635280This 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

26%

Seen by 20 of 76 full-feed vantage points

Seen by few vantage points

Observed at 4 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
Ukraine
Allocated
2nd April 2019
Allocation block
5.181.84.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 5.181.87.0/24
ROA prefixAuthorised originMax length
5.181.87.0/24AS211422/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 5.181.87.0/24
PrefixAddressesOriginVisibility
5.181.86.0/24256AS211632Internet Solutions & Innovations LTD.76/76

History

  1. AS21142211th November 2026 — present
  2. AS4758529th October 2026 — 11th November 2026
  3. AS4326017th October 2026 — 20th October 2026
  4. AS2034944th October 2026 — 6th October 2026
  5. AS4758512th August 2026 — 22nd 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 5.181.87.0/24 in the calculator/24 reference

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