directrateStatus
Measured, not declared.
Every source is probed with a real shop every 15 minutes. The table shows the share of probes it answered over the window and the average latency. There is no 'operational' badge because nobody is declaring anything: it is the ratio or nothing.
| Source | Uptime (30 days) | Avg latency |
|---|---|---|
| Agoda | 100 % | 1,408 ms |
| Best Western | 90.31 % | 3,316 ms |
| Booking.com | 100 % | 1,539 ms |
| Choice | 100 % | 2,027 ms |
| Trip.com | 100 % | 1,844 ms |
| Expedia | 100 % | 1,390 ms |
| Hilton | 99.83 % | 1,281 ms |
| Hotels.com | 100 % | 1,372 ms |
| Hyatt | 97.35 % | 9,908 ms |
| IHG | 98.29 % | 2,676 ms |
| I Prefer | 100 % | 751 ms |
| Marriott | 97.60 % | 1,363 ms |
| Meliá | 99.83 % | 1,036 ms |
| Premier Inn | 99.06 % | 2,942 ms |
| Radisson | 97.69 % | 3,764 ms |
| Wyndham | 94.52 % | 4,365 ms |
generated 2026-10-11 09:30Z · build-time snapshot; refreshes from the API when the page can read it · uptime = the share of 15-minute probes the source answered coherently; our own probe errors are left out.
Feed: https://api.directrate.dev/status.json. No uptime SLA yet — chains and OTAs change their systems without notice and a source can degrade for hours; source and cache_age_sec on every response say what you got. Errors are never billed.