31.58.176.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 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 AS213915seen on 480 paths from 80 vantage points
- Peer of AS207208seen on 4,519 paths from 91 vantage points
- Peer of AS201814seen on 2,187 paths from 63 vantage points
- Peer of AS9002seen on 33,837 paths from 2 vantage points
GB
PLOne 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
- Amsterdam2139152072082018146939213151This path
- London, UK21391520720820181490028529Shown above
- Sao Paulo2139152072082018146939266213This path
- Singapore21391520720820181450263132337This path
- Oregon, US213915207208201814693920130This 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 80 of 80 full-feed vantage points
Globally propagatedObserved 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 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.58.176.0/24 | AS213915 | /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.58.176.0/22 | 1k | AS48678Pentech Bilisim Teknolojileri Sanayi Ve Ticaret Limited Sirketi | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.58.177.0/24 | 256 | AS213915HOSTES LTD | 80/80 |
History
- AS21391512th 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 31.58.176.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.