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.
Operational
The forecast data is complete and current. No degradation is being reported by the
refresh pipeline.
Forecast data
- Last refreshed
- 08 November 2026, 02:11 UTC
- That was
- 13 minutes ago
- Considered stale?
- No
- Qualifying destinations
- 63
We flag the data as stale past 123 minutes. That
limit is read from the refresh job's own schedule, so a dead scheduler shows up here
rather than going unnoticed for days.
Coverage
- Destinations in the dataset
- 63
- With hotel inventory
- 63
- Hotel coverage
- 100%
- With photography
- 63
- With flight times
- 63
- Hotel chains recognised
- 60
- Hotel data last refreshed
- 13 minutes ago
Data sources
- Weather forecasts — Open-Meteo
- Live
- Hotel inventory and rates — third-party supplier data
- Live
- Destination photography — Pexels
- Live
342 of 3,516 headline flight times (destination by origin city) are the shortest itinerary Duffel actually returned, connections included, marked "Xh Ym (verified, Duffel)". The other 3,174 are estimates, marked "~Xh Ym (estimated)". Straight-line estimate: great-circle distance at airliner speed, not a quoted itinerary.
Flight data currently comes from Duffel and RouteStack.
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.