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 105 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 77 ms | 0 |
| Tue 05 | 0 | 0.0 | 49 ms | 0 |
| Tue 07 | 0 | 0.0 | 144 ms | 0 |
| Tue 09 | 0 | 0.0 | 165 ms | 0 |
| Tue 11 | 0 | 0.0 | 92 ms | 0 |
| Tue 13 | 0 | 0.0 | 82 ms | 0 |
| Tue 16 | 0 | 0.0 | 193 ms | 0 |
| Tue 18 | 0 | 0.0 | 101 ms | 0 |
| Tue 20 | 0 | 0.0 | 71 ms | 0 |
| Tue 22 | 0 | 0.0 | 244 ms | 0 |
| Wed 01 | 0 | 0.0 | 58 ms | 0 |
| Wed 03 | 0 | 0.0 | 249 ms | 0 |
| Wed 05 | 0 | 0.0 | 23 ms | 0 |
| Wed 07 | 0 | 0.0 | 257 ms | 0 |
| Wed 10 | 0 | 0.0 | 130 ms | 0 |
| Wed 12 | 0 | 0.0 | 253 ms | 0 |
| Wed 14 | 0 | 0.0 | 84 ms | 0 |
| Wed 16 | 0 | 0.0 | 103 ms | 0 |
| Wed 18 | 0 | 0.0 | 240 ms | 0 |
| Wed 20 | 0 | 0.0 | 96 ms | 0 |
| Wed 23 | 0 | 0.0 | 128 ms | 0 |
| Thu 01 | 0 | 0.0 | 160 ms | 0 |
| Thu 03 | 0 | 0.0 | 283 ms | 0 |
| Thu 05 | 0 | 0.0 | 124 ms | 0 |
| Thu 07 | 0 | 0.0 | 104 ms | 0 |
| Thu 09 | 0 | 0.0 | 49 ms | 0 |
| Thu 11 | 0 | 0.0 | 91 ms | 0 |
| Thu 13 | 0 | 0.0 | 99 ms | 0 |
| Thu 15 | 0 | 0.0 | 295 ms | 0 |
| Thu 17 | 0 | 0.0 | 87 ms | 0 |
| Thu 19 | 0 | 0.0 | 88 ms | 0 |
| Thu 21 | 0 | 0.0 | 255 ms | 0 |
| Thu 23 | 0 | 0.0 | 243 ms | 0 |
| Fri 02 | 0 | 0.0 | 50 ms | 0 |
| Fri 04 | 0 | 0.0 | 45 ms | 0 |
| Fri 06 | 0 | 0.0 | 85 ms | 0 |
| Fri 08 | 0 | 0.0 | 123 ms | 0 |
| Fri 10 | 0 | 0.0 | 96 ms | 0 |
| Fri 12 | 0 | 0.0 | 318 ms | 0 |
| Fri 14 | 0 | 0.0 | 115 ms | 0 |
| Fri 16 | 0 | 0.0 | 214 ms | 0 |
| Fri 18 | 0 | 0.0 | 123 ms | 0 |
| Fri 19 | 0 | 0.0 | 88 ms | 0 |
| Fri 21 | 0 | 0.0 | 83 ms | 0 |
| Fri 23 | 0 | 0.0 | 119 ms | 0 |
| Sat 00 | 0 | 0.0 | 79 ms | 0 |
| Sat 02 | 0 | 0.0 | 121 ms | 0 |
| Sat 03 | 0 | 0.0 | 105 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 Namastay 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 Namastay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Namastay alerts to Slack, Discord or a webhook — free.
Namastay, at namastay.io, is one of the Travel services we monitor. Namastay reimagines hotel booking and payment—secure, mobile-first, and intuitive. Empowering seamless travel for guests and hotels globally.
Namastay publishes an official status page at status.namastay.io; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 128 ms average, 79–318 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 Namastay incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
128 ms on average over the last 24 hours (79–318 ms).
Yes, at https://status.namastay.io.
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 Namastay here at once, the problem is on Namastay'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 Namastay. 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.