5.181.87.0/24
AS43260 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
20 of 76 vantage points
RPKI
Registry
UAAllocated 2nd April 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS211422seen on 1,087 paths from 76 vantage points
- Peer of AS44547seen on 816 paths from 119 vantage points
- Peer of AS208972seen on 1,929 paths from 25 vantage points
- Peer of AS5511seen on 36 paths from 4 vantage points
- Peer of AS8452seen on 111 paths from 6 vantage points
- Peer of AS8966seen on 5,361 paths from 2 vantage points
TR
FR
EG
AEOne 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
- Amsterdam21142244547208972502638298This path
- Oregon, US21142244547208972168042013This path
- London, UK211422445472089725511845289668529Shown above
- 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 pointsObserved 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
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 5.181.87.0/24 | AS0 | /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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 5.181.86.0/24 | 256 | AS211632Internet Solutions & Innovations LTD. | 76/76 |
History
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.