185.27.88.0/24
Telecommunications Regulatory Authority (TRA)AS60680
Oman Telecommunications Company (S.A.O.G)AS28885
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
79 of 80 vantage points
RPKI
Registry
OMAllocated 30th May 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS60680seen on 140 paths from 140 vantage points
- Peer of AS28885seen on 21,658 paths from 141 vantage points
- Peer of AS8529seen on 4,645 paths from 2 vantage points
AE
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
- London, UK60680288858529This path
- Singapore60680288858529132337Shown above
- Amsterdam606802888585296939213151This path
- Sao Paulo606802888585296939266213This path
- Oregon, US60680288858529693920130This 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
99%
Seen by 79 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
- Oman
- Allocated
- 30th May 2013
- Allocation block
- 185.27.88.0/22
- 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 |
|---|---|---|
| 185.27.88.0/24 | AS60680 | /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.27.89.0/24 | 256 | AS60680Telecommunications Regulatory Authority (TRA) | 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.27.88.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.