User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
expedia.com · Travel
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Live diagnosis
Tests expedia.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Not enough checks
Last check reached it in 184 ms · 3 min ago.
No status feed
Expedia does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Sun 11 | 0 | 0.0 | 126 ms | 0 |
| Sun 12 | 0 | 0.0 | 161 ms | 0 |
| Sun 13 | 0 | 0.0 | 196 ms | 0 |
| Sun 14 | 0 | 0.0 | 196 ms | 0 |
| Sun 15 | 0 | 0.0 | 170 ms | 0 |
| Sun 16 | 0 | 0.0 | 176 ms | 0 |
| Sun 17 | 0 | 0.0 | 195 ms | 0 |
| Sun 18 | 0 | 0.0 | 184 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Expedia yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Expedia goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Runs on: AWS
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.