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 33 min ago. Last stored result reached it in 61 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 10 | 0 | 0.0 | 61 ms | 0 |
| Tue 13 | 0 | 0.0 | 68 ms | 0 |
| Tue 15 | 0 | 0.0 | 192 ms | 0 |
| Tue 17 | 0 | 0.0 | 126 ms | 0 |
| Tue 19 | 0 | 0.0 | 203 ms | 0 |
| Tue 22 | 0 | 0.0 | 65 ms | 0 |
| Wed 00 | 0 | 0.0 | 75 ms | 0 |
| Wed 02 | 0 | 0.0 | 195 ms | 0 |
| Wed 04 | 0 | 0.0 | 113 ms | 0 |
| Wed 07 | 0 | 0.0 | 110 ms | 0 |
| Wed 09 | 0 | 0.0 | 125 ms | 0 |
| Wed 11 | 0 | 0.0 | 51 ms | 0 |
| Wed 13 | 0 | 0.0 | 105 ms | 0 |
| Wed 15 | 0 | 0.0 | 80 ms | 0 |
| Wed 17 | 0 | 0.0 | 55 ms | 0 |
| Wed 20 | 0 | 0.0 | 94 ms | 0 |
| Wed 22 | 0 | 0.0 | 97 ms | 0 |
| Thu 00 | 0 | 0.0 | 155 ms | 0 |
| Thu 02 | 0 | 0.0 | 182 ms | 0 |
| Thu 04 | 0 | 0.0 | 209 ms | 0 |
| Thu 06 | 0 | 0.0 | 130 ms | 0 |
| Thu 08 | 0 | 0.0 | 78 ms | 0 |
| Thu 10 | 0 | 0.0 | 99 ms | 0 |
| Thu 12 | 0 | 0.0 | 62 ms | 0 |
| Thu 15 | 0 | 0.0 | 82 ms | 0 |
| Thu 16 | 0 | 0.0 | 187 ms | 0 |
| Thu 18 | 0 | 0.0 | 86 ms | 0 |
| Thu 20 | 0 | 0.0 | 99 ms | 0 |
| Thu 22 | 0 | 0.0 | 111 ms | 0 |
| Fri 00 | 0 | 0.0 | 119 ms | 0 |
| Fri 02 | 0 | 0.0 | 103 ms | 0 |
| Fri 05 | 0 | 0.0 | 142 ms | 0 |
| Fri 07 | 0 | 0.0 | 119 ms | 0 |
| Fri 09 | 0 | 0.0 | 142 ms | 0 |
| Fri 10 | 0 | 0.0 | 56 ms | 0 |
| Fri 12 | 0 | 0.0 | 106 ms | 0 |
| Fri 14 | 0 | 0.0 | 65 ms | 0 |
| Fri 16 | 0 | 0.0 | 84 ms | 0 |
| Fri 18 | 0 | 0.0 | 357 ms | 0 |
| Fri 20 | 0 | 0.0 | 95 ms | 0 |
| Fri 21 | 0 | 0.0 | 63 ms | 0 |
| Fri 23 | 0 | 0.0 | 94 ms | 0 |
| Sat 01 | 0 | 0.0 | 72 ms | 0 |
| Sat 03 | 0 | 0.0 | 111 ms | 0 |
| Sat 06 | 0 | 0.0 | 87 ms | 0 |
| Sat 08 | 0 | 0.0 | 120 ms | 0 |
| Sat 10 | 0 | 0.0 | 89 ms | 0 |
| Sat 12 | 0 | 0.0 | 61 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Stay22 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 Stay22 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Stay22 alerts to Slack, Discord or a webhook — free.
We track Stay22 (stay22.com) as part of the Travel group. Monetize your travel content effortlessly with Stay22. Transform audience intent into revenue without added work, empowering creators and platforms to earn on bookings seamlessly.
Stay22 publishes an official status page at status.stay22.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 106 ms average, 51–357 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Stay22 incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
106 ms on average over the last 24 hours (51–357 ms).
Yes, at https://status.stay22.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 Stay22 here at once, the problem is on Stay22'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 Stay22. 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.