31.59.181.0/24
At a glance
Addresses
/24 block
Visibility
57 of 78 vantage points
RPKI
Registry
AEAllocated 28th January 2011
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 AS212238seen on 262,714 paths from 142 vantage points
- Peer of AS60068seen on 146,535 paths from 142 vantage points
- Peer of AS1299seen on 379,888 paths from 2 vantage points
GB
SEOne 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
- London, UK2122386006812998529Shown above
- Sao Paulo21223860068645335280This path
- Amsterdam212238600681299250918298This path
- Singapore213915495813257335623673This path
- Oregon, US212238600681299855142013This 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
73%
Seen by 57 of 78 full-feed vantage points
Partially propagatedObserved 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
- United Arab Emirates
- Allocated
- 28th January 2011
- Allocation block
- 31.56.0.0/14
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 31.59.181.0/24 | AS212238 | /24 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.59.176.0/21 | 2k | AS219048Sachin Kothawade trading as SUN IT SOLUTIONS | 20/78 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.59.180.0/24 | 256 | AS219064Akenai Products LTD | 78/78 |
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 31.59.181.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.