User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
orbitz.com · Travel
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 83 ms · 7 min ago.
No status feed
Orbitz does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 18:45 | 0 | 0.0 | 140 ms | 0 |
| 19:00 | 0 | 0.0 | 170 ms | 0 |
| 19:15 | 0 | 0.0 | 115 ms | 0 |
| 19:30 | 0 | 0.0 | 203 ms | 0 |
| 19:45 | 0 | 0.0 | 220 ms | 0 |
| 20:00 | 0 | 0.0 | 101 ms | 0 |
| 20:15 | 0 | 0.0 | 158 ms | 0 |
| 20:30 | 0 | 0.0 | 681 ms | 0 |
| 20:45 | 0 | 0.0 | 112 ms | 0 |
| 21:00 | 0 | 0.0 | 161 ms | 0 |
| 21:15 | 0 | 0.0 | 174 ms | 0 |
| 21:30 | 0 | 0.0 | 140 ms | 0 |
| 21:45 | 0 | 0.0 | 230 ms | 0 |
| 22:00 | 0 | 0.0 | 79 ms | 0 |
| 22:15 | 0 | 0.0 | 303 ms | 0 |
| 22:30 | 0 | 0.0 | 83 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.
No outages on record for Orbitz 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 Orbitz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Orbitz alerts to Slack, Discord or a webhook — free.
We track Orbitz (orbitz.com) as part of the Travel group. Live checks and user reports.
Orbitz has no official status feed we can read, so this page relies on our own checks and user reports.
Common problems for travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 182 ms average, 73–681 ms range across 26 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Orbitz incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
182 ms on average over the last 24 hours (73–681 ms).
Not one we can read. This page uses independent checks of orbitz.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report Orbitz here at once, the problem is on Orbitz's side.