User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 346 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 07 | 0 | 0.0 | 244 ms | 0 |
| Wed 10 | 0 | 0.0 | 363 ms | 0 |
| Wed 12 | 0 | 0.0 | 350 ms | 0 |
| Wed 14 | 0 | 0.0 | 234 ms | 0 |
| Wed 16 | 0 | 0.0 | 76 ms | 0 |
| Wed 18 | 0 | 0.0 | 426 ms | 0 |
| Wed 21 | 0 | 0.0 | 239 ms | 0 |
| Wed 23 | 0 | 0.0 | 197 ms | 0 |
| Thu 01 | 0 | 0.0 | 304 ms | 0 |
| Thu 03 | 0 | 0.0 | 146 ms | 0 |
| Thu 05 | 0 | 0.0 | 178 ms | 0 |
| Thu 07 | 0 | 0.0 | 44 ms | 0 |
| Thu 09 | 0 | 0.0 | 344 ms | 0 |
| Thu 11 | 0 | 0.0 | 339 ms | 0 |
| Thu 13 | 0 | 0.0 | 132 ms | 0 |
| Thu 15 | 0 | 0.0 | 238 ms | 0 |
| Thu 17 | 0 | 0.0 | 70 ms | 0 |
| Thu 19 | 0 | 0.0 | 145 ms | 0 |
| Thu 21 | 0 | 0.0 | 172 ms | 0 |
| Thu 22 | 0 | 0.0 | 81 ms | 0 |
| Fri 01 | 0 | 0.0 | 356 ms | 0 |
| Fri 03 | 0 | 0.0 | 360 ms | 0 |
| Fri 05 | 0 | 0.0 | 347 ms | 0 |
| Fri 07 | 0 | 0.0 | 266 ms | 0 |
| Fri 09 | 0 | 0.0 | 189 ms | 0 |
| Fri 11 | 0 | 0.0 | 219 ms | 0 |
| Fri 13 | 0 | 0.0 | 332 ms | 0 |
| Fri 15 | 0 | 0.0 | 323 ms | 0 |
| Fri 17 | 0 | 0.0 | 215 ms | 0 |
| Fri 18 | 0 | 0.0 | 282 ms | 0 |
| Fri 20 | 0 | 0.0 | 180 ms | 0 |
| Fri 22 | 0 | 0.0 | 142 ms | 0 |
| Sat 00 | 0 | 0.0 | 361 ms | 0 |
| Sat 02 | 0 | 0.0 | 178 ms | 0 |
| Sat 04 | 0 | 0.0 | 219 ms | 0 |
| Sat 06 | 0 | 0.0 | 326 ms | 0 |
| Sat 07 | 0 | 0.0 | 545 ms | 0 |
| Sat 09 | 0 | 0.0 | 203 ms | 0 |
| Sat 11 | 0 | 0.0 | 175 ms | 0 |
| Sat 13 | 0 | 0.0 | 134 ms | 0 |
| Sat 16 | 0 | 0.0 | 148 ms | 0 |
| Sat 18 | 0 | 0.0 | 316 ms | 0 |
| Sat 20 | 0 | 0.0 | 223 ms | 0 |
| Sat 23 | 0 | 0.0 | 628 ms | 0 |
| Sun 01 | 0 | 0.0 | 256 ms | 0 |
| Sun 03 | 0 | 0.0 | 381 ms | 0 |
| Sun 06 | 0 | 0.0 | 217 ms | 0 |
| Sun 08 | 0 | 0.0 | 346 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Thrifty Traveler 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 Thrifty Traveler goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Thrifty Traveler, at thriftytraveler.com, is one of the Travel services we monitor. Welcome to Thrifty Traveler and to the world of cheap travel. Daily flight deals, credit card offers, points & miles, destination guides and travel reviews.
Thrifty Traveler publishes an official status page at status.thriftytraveler.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 277 ms average, 64–628 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Thrifty Traveler incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
277 ms on average over the last 24 hours (64–628 ms).
Yes, at https://status.thriftytraveler.com.
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 Thrifty Traveler here at once, the problem is on Thrifty Traveler's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Thrifty Traveler. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.