Live outage monitoring
Real-time status for the websites and services you rely on.
Hotels.com status · hotels.com
Hotel booking site.
Hotels.com status is uncertain
hotels.com status is currently uncertain. The latest automated check was run 2026-08-14 23:09 UTC from primary location. A failed probe from a single location is not treated as a confirmed global outage.
Hotels.com
hotels.com
hotels.com status is currently uncertain.
A failed probe from one location is not a confirmed global outage.
Hotels.com does not publish a verified public incident feed. We record incidents from repeated independent check failures and from elevated user reports on this site, not from other outage trackers. Our independent check could not reach the website from this monitoring location, which is not the same as a confirmed outage.
Crowd reports submitted on this site for Hotels.com over the last 24 hours.
0 reports
Loading user-report chart…
Not enough independent response-time samples yet to draw this chart.
Availability from independent checks, with recorded incidents and downtime in each window. Monitoring for 5 hours. Period percentages appear only after we have full coverage for that window.
Today
—
Latest 2026-08-14 23:09 UTC · Primary location
Monitoring for 5 hours
None today
Our independent check could not reach Hotels.com from this monitoring location. That can be a regional network issue and is not a confirmed global outage.
Not enough history
Last 7 days
—
Not enough history
Last 30 days
—
Not enough history
Last 365 days
—
Not enough history
Recorded outages with duration and start time.
No outage history stored yet.
Who's Down Today monitors Hotels.com independently of the company that runs it. We send reachability checks from our primary location every 3 minutes and record response time, HTTP errors, and timeouts.
Hotels.com does not publish a verified public incident feed. We do not copy third-party outage lists. Repeated independent check failures and elevated user reports on this site can still be recorded as possible issues. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.