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 46 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 05 | 0 | 0.0 | 1485 ms | 0 |
| Wed 07 | 0 | 0.0 | 189 ms | 0 |
| Wed 10 | 0 | 0.0 | 107 ms | 0 |
| Wed 12 | 0 | 0.0 | 158 ms | 0 |
| Wed 14 | 0 | 0.0 | 125 ms | 0 |
| Wed 16 | 0 | 0.0 | 127 ms | 0 |
| Wed 18 | 0 | 0.0 | 2054 ms | 0 |
| Wed 20 | 0 | 0.0 | 140 ms | 0 |
| Wed 23 | 0 | 0.0 | 201 ms | 0 |
| Thu 01 | 0 | 0.0 | 158 ms | 0 |
| Thu 03 | 0 | 0.0 | 2393 ms | 0 |
| Thu 05 | 0 | 0.0 | 131 ms | 0 |
| Thu 07 | 0 | 0.0 | 59 ms | 0 |
| Thu 09 | 0 | 0.0 | 119 ms | 0 |
| Thu 11 | 0 | 0.0 | 2159 ms | 0 |
| Thu 13 | 0 | 0.0 | 139 ms | 0 |
| Thu 15 | 0 | 0.0 | 149 ms | 0 |
| Thu 17 | 0 | 0.0 | 85 ms | 0 |
| Thu 19 | 0 | 0.0 | 72 ms | 0 |
| Thu 21 | 0 | 0.0 | 128 ms | 0 |
| Thu 23 | 0 | 0.0 | 59 ms | 0 |
| Fri 02 | 0 | 0.0 | 85 ms | 0 |
| Fri 04 | 0 | 0.0 | 92 ms | 0 |
| Fri 06 | 0 | 0.0 | 46 ms | 0 |
| Fri 08 | 0 | 0.0 | 55 ms | 0 |
| Fri 10 | 0 | 0.0 | 147 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 12 | 0 | 0.0 | 55 ms | 0 |
| Fri 14 | 0 | 0.0 | 42 ms | 0 |
| Fri 16 | 0 | 0.0 | 110 ms | 0 |
| Fri 18 | 0 | 0.0 | 70 ms | 0 |
| Fri 20 | 0 | 0.0 | 86 ms | 0 |
| Fri 22 | 0 | 0.0 | 70 ms | 0 |
| Sat 00 | 0 | 0.0 | 2059 ms | 0 |
| Sat 02 | 0 | 0.0 | 114 ms | 0 |
| Sat 04 | 0 | 0.0 | 74 ms | 0 |
| Sat 06 | 0 | 0.0 | 48 ms | 0 |
| Sat 08 | 0 | 0.0 | 2193 ms | 0 |
| Sat 10 | 0 | 0.0 | 140 ms | 0 |
| Sat 13 | 0 | 0.0 | 65 ms | 0 |
| Sat 15 | 0 | 0.0 | 108 ms | 0 |
| Sat 17 | 0 | 0.0 | 195 ms | 0 |
| Sat 20 | 0 | 0.0 | 144 ms | 0 |
| Sat 21 | 0 | 0.0 | 2404 ms | 0 |
| Sat 23 | 0 | 0.0 | 2124 ms | 0 |
| Sun 01 | 0 | 0.0 | 2315 ms | 0 |
| Sun 04 | 0 | 0.0 | 95 ms | 0 |
| Sun 06 | 0 | 0.0 | 46 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 Neobookings S.L. 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 Neobookings S.L. 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.
We track Neobookings S.L. (neobookings.com) as part of the Travel group. Automatiza, impacta, crece. Es hora de hacer brillar a tu hotel. | Neobookings
Neobookings S.L. publishes an official status page at status.neobookings.com; when we can read it, its incident level is folded into the status shown here.
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 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 894 ms average, 46–2404 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 Neobookings S.L. incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
894 ms on average over the last 24 hours (46–2404 ms).
Yes, at https://status.neobookings.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 Neobookings S.L. here at once, the problem is on Neobookings S.L.'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 Neobookings S.L.. 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.