185.192.70.0/24
At a glance
Addresses
/24 block
Visibility
44 of 80 vantage points
RPKI
Registry
NLAllocated 28th February 2017
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS42831seen on 13,573 paths from 97 vantage points
- Peer of AS2914seen on 3,459 paths from 2 vantage points
- Peer of AS4229seen on 13,937 paths from 2 vantage points
GB
US
SGOne 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
- Amsterdam42831291434549213151This path
- London, UK1997413520090028529This path
- Singapore4283129144229132337Shown above
- Sao Paulo1997413520090023356266213This path
- Oregon, US199741352009002693920130This 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
55%
Seen by 44 of 80 full-feed vantage points
Partially 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
- Netherlands
- Allocated
- 28th February 2017
- Allocation block
- 185.192.68.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 |
|---|---|---|
| 185.192.70.0/24 | AS199741 | /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 |
|---|---|---|---|
| 185.192.71.0/24 | 256 | AS206092F.N.S. HOLDINGS LIMITED | 80/80 |
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.192.70.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.