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 1 hr ago. Last stored result reached it in 583 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 717 ms | 0 |
| Tue 00 | 0 | 0.0 | 569 ms | 0 |
| Tue 02 | 0 | 0.0 | 912 ms | 0 |
| Tue 05 | 0 | 0.0 | 562 ms | 0 |
| Tue 07 | 0 | 0.0 | 577 ms | 0 |
| Tue 09 | 0 | 0.0 | 1949 ms | 0 |
| Tue 11 | 0 | 0.0 | 1894 ms | 0 |
| Tue 13 | 0 | 0.0 | 1543 ms | 0 |
| Tue 15 | 0 | 0.0 | 1844 ms | 0 |
| Tue 18 | 0 | 0.0 | 794 ms | 0 |
| Tue 20 | 0 | 0.0 | 577 ms | 0 |
| Tue 22 | 0 | 0.0 | 531 ms | 0 |
| Wed 00 | 0 | 0.0 | 559 ms | 0 |
| Wed 03 | 0 | 0.0 | 1351 ms | 0 |
| Wed 05 | 0 | 0.0 | 1075 ms | 0 |
| Wed 07 | 0 | 0.0 | 733 ms | 0 |
| Wed 09 | 0 | 0.0 | 795 ms | 0 |
| Wed 12 | 0 | 0.0 | 509 ms | 0 |
| Wed 14 | 0 | 0.0 | 822 ms | 0 |
| Wed 16 | 0 | 0.0 | 697 ms | 0 |
| Wed 18 | 0 | 0.0 | 664 ms | 0 |
| Wed 20 | 0 | 0.0 | 596 ms | 0 |
| Wed 22 | 0 | 0.0 | 575 ms | 0 |
| Thu 00 | 0 | 0.0 | 1641 ms | 0 |
| Thu 03 | 0 | 0.0 | 1769 ms | 0 |
| Thu 05 | 0 | 0.0 | 700 ms | 0 |
| Thu 07 | 0 | 0.0 | 683 ms | 0 |
| Thu 09 | 0 | 0.0 | 658 ms | 0 |
| Thu 11 | 0 | 0.0 | 1217 ms | 0 |
| Thu 13 | 0 | 0.0 | 841 ms | 0 |
| Thu 15 | 0 | 0.0 | 2456 ms | 0 |
| Thu 17 | 0 | 0.0 | 1843 ms | 0 |
| Thu 19 | 0 | 0.0 | 776 ms | 0 |
| Thu 21 | 0 | 0.0 | 631 ms | 0 |
| Thu 23 | 0 | 0.0 | 727 ms | 0 |
| Fri 01 | 0 | 0.0 | 740 ms | 0 |
| Fri 03 | 0 | 0.0 | 737 ms | 0 |
| Fri 05 | 0 | 0.0 | 593 ms | 0 |
| Fri 07 | 0 | 0.0 | 772 ms | 0 |
| Fri 09 | 0 | 0.0 | 1510 ms | 0 |
| Fri 11 | 0 | 0.0 | 758 ms | 0 |
| Fri 13 | 0 | 0.0 | 1545 ms | 0 |
| Fri 15 | 0 | 0.0 | 657 ms | 0 |
| Fri 17 | 0 | 0.0 | 523 ms | 0 |
| Fri 18 | 0 | 0.0 | 571 ms | 0 |
| Fri 19 | 0 | 0.0 | 804 ms | 0 |
| Fri 21 | 0 | 0.0 | 1215 ms | 0 |
| Fri 22 | 0 | 0.0 | 583 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Byhours 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 Byhours goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Byhours alerts to Slack, Discord or a webhook — free.
We track Byhours (byhours.com) as part of the Travel group. Reserva habitaciones por horas en tu hotel favorito y decide la hora de check-in. Escoge entre más de 4.000 hoteles de 3, 4 y 5 estrellas y reserva en más de 25 países. Accede a todos los servicios del Hotel con cancelación gratuita. Reserva ya con BYHOURS, líder en Microestancias.
Byhours publishes an official status page at status.byhours.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 811 ms average, 523–1545 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Byhours incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
811 ms on average over the last 24 hours (523–1545 ms).
Yes, at https://status.byhours.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 Byhours here at once, the problem is on Byhours'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 Byhours. 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.