System status
Is this thing working?
This page is the human-readable rendering of our
/health endpoint — the same JSON our monitoring reads,
the same numbers, computed the same way. A status page that always says
"all systems operational" is worth nothing, so this one reports the bad
news too.
Degraded — the data is not fully healthy right now
Something in the data pipeline is not right. The site is up and serving, but the
forecast data behind it is incomplete, stale, or both. Treat what you see on the
site with that in mind. The specific reasons are listed below.
What is wrong
These are the raw reason codes emitted by the refresh job, shown unedited.
Forecast data
- Last refreshed
- 09 August 2026, 05:01 UTC
- That was
- 34 minutes ago
- Considered stale?
- No
- Qualifying destinations
- 39
The refresh runs hourly. We flag the data as stale past 150 minutes,
which is generous enough to absorb a slow supplier pass but tight enough that a dead
scheduler shows up here rather than going unnoticed for days.
Coverage
- Destinations in the dataset
- 39
- With hotel inventory
- 37
- Hotel coverage
- 95%
- With photography
- 39
- With flight times
- 39
- Hotel chains recognised
- 38
- Hotel fetch completed
- No
Data sources
- Weather forecasts — Open-Meteo
- Live
- Hotel inventory and rates — LiteAPI / Nuitée
- Not reporting
- Destination photography — Pexels
- Live
Flight durations are computed from great-circle distance between airports, not
fetched from a live carrier feed — they are estimates and we label them as
such wherever they appear.
Machine-readable version of everything on this page:
/health. It returns HTTP 200 even when degraded, deliberately
— the service being reachable and the data being good are two different
questions, and a load balancer should not pull a working site because a photo
fetch failed. Alert on the degraded field, not the status code.