Is Booking.com down?
Booking.com is up
Right now
No. Booking.com Demand API answers UpButler's independent probe; no machine-readable official status.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/booking/status.agent.json
MCP: upstream_status {"service":"booking"}
Booking.com listings and the Demand and Connectivity APIs.
What Booking.com says
status.booking.com has no public JSON API or feed we may read; only the independent probe is shown.
Their site: status.booking.comWhat UpButler measured
Demand API is answeringHTTP 401 · 87 ms
One request without credentials to demandapi.booking.com every two minutes, from eu-central (one location, not a global view). An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 06:08 UTC
Booking.com incidents, last 90 days
Without a machine-readable source there is no incident history to show. Booking.com keeps its own at status.booking.com.
Get alerted when Booking.com goes down
No account. One email when our probe cannot reach Booking.com for several minutes, one when it can again. You confirm the address first, and every email has a one-click unsubscribe.
On UpButler? Add Booking.com as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Booking.com's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/booking)Tell your outage from Booking.com's
Declare that your project depends on Booking.com. When one of your monitors fails while Booking.com has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- bookingcurl -s https://upbutler.com/status/booking/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "booking",
"verdict": "proceed",
"status": "operational",
"reason": "Booking.com Demand API answers UpButler's independent probe; no machine-readable official status",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Booking.com down right now?
- No. As of 2026-10-10 07:17 UTC, Booking.com is up. This page reads the status again every 2 minutes.
- Where does this status come from?
- status.booking.com has no public JSON API or feed we may read; only the independent probe is shown.
- What does UpButler's own Booking.com check prove?
- Every two minutes UpButler sends one request without credentials to the Booking.com Demand API (demandapi.booking.com) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
- How can my agent or app check Booking.com status?
- Fetch https://upbutler.com/status/booking/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"booking"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Booking.com's?
- Add "booking" to the dependencies of your UpButler workspace. When one of your monitors fails while Booking.com has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Booking.com. Status and incident text belong to Booking.com and are read from their public status source; the probe result is UpButler's own measurement.