185.158.23.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
IQAllocated 23rd February 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS207598seen on 1,514 paths from 139 vantage points
- Peer of AS212330seen on 28,870 paths from 139 vantage points
- Peer of AS208293seen on 944 paths from 138 vantage points
- Peer of AS200612seen on 1,335 paths from 56 vantage points
- Peer of AS6939seen on 41,713 paths from 5 vantage points
- Peer of AS38623seen on 83,119 paths from 1 vantage point
VG
US
KHOne 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, UK2075982123302082932006128529This path
- Amsterdam207598212330208293211513210021250918298This path
- Sao Paulo207598212330208293211513210021645335280This path
- Singapore20759821233020829320061269393862323673Shown above
- Oregon, US2075982123302082932115132100211299855142013This 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 76 of 76 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
- Iraq
- Allocated
- 23rd February 2018
- Allocation block
- 185.158.20.0/22
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 185.158.22.0/24 | 256 | AS207598Iraqcell Communications Co. 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 185.158.23.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.