User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 165 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 15 | 0 | 0.0 | 172 ms | 0 |
| Tue 18 | 0 | 0.0 | 124 ms | 0 |
| Tue 20 | 0 | 0.0 | 290 ms | 0 |
| Tue 22 | 0 | 0.0 | 176 ms | 0 |
| Wed 00 | 0 | 0.0 | 91 ms | 0 |
| Wed 03 | 0 | 0.0 | 85 ms | 0 |
| Wed 05 | 0 | 0.0 | 224 ms | 0 |
| Wed 07 | 0 | 0.0 | 54 ms | 0 |
| Wed 09 | 0 | 0.0 | 86 ms | 0 |
| Wed 12 | 0 | 0.0 | 81 ms | 0 |
| Wed 14 | 0 | 0.0 | 144 ms | 0 |
| Wed 16 | 0 | 0.0 | 82 ms | 0 |
| Wed 18 | 0 | 0.0 | 205 ms | 0 |
| Wed 20 | 0 | 0.0 | 317 ms | 0 |
| Wed 22 | 0 | 0.0 | 105 ms | 0 |
| Thu 01 | 0 | 0.0 | 146 ms | 0 |
| Thu 03 | 0 | 0.0 | 192 ms | 0 |
| Thu 05 | 0 | 0.0 | 213 ms | 0 |
| Thu 07 | 0 | 0.0 | 240 ms | 0 |
| Thu 09 | 0 | 0.0 | 183 ms | 0 |
| Thu 11 | 0 | 0.0 | 202 ms | 0 |
| Thu 13 | 0 | 0.0 | 268 ms | 0 |
| Thu 15 | 0 | 0.0 | 238 ms | 0 |
| Thu 17 | 0 | 0.0 | 166 ms | 0 |
| Thu 19 | 0 | 0.0 | 71 ms | 0 |
| Thu 21 | 0 | 0.0 | 153 ms | 0 |
| Thu 22 | 0 | 0.0 | 162 ms | 0 |
| Fri 00 | 0 | 0.0 | 214 ms | 0 |
| Fri 02 | 0 | 0.0 | 127 ms | 0 |
| Fri 04 | 0 | 0.0 | 87 ms | 0 |
| Fri 06 | 0 | 0.0 | 158 ms | 0 |
| Fri 09 | 0 | 0.0 | 257 ms | 0 |
| Fri 11 | 0 | 0.0 | 160 ms | 0 |
| Fri 13 | 0 | 0.0 | 187 ms | 0 |
| Fri 15 | 0 | 0.0 | 107 ms | 0 |
| Fri 17 | 0 | 0.0 | 100 ms | 0 |
| Fri 18 | 0 | 0.0 | 104 ms | 0 |
| Fri 20 | 0 | 0.0 | 141 ms | 0 |
| Fri 22 | 0 | 0.0 | 169 ms | 0 |
| Sat 00 | 0 | 0.0 | 94 ms | 0 |
| Sat 02 | 0 | 0.0 | 240 ms | 0 |
| Sat 04 | 0 | 0.0 | 277 ms | 0 |
| Sat 06 | 0 | 0.0 | 189 ms | 0 |
| Sat 08 | 0 | 0.0 | 56 ms | 0 |
| Sat 10 | 0 | 0.0 | 136 ms | 0 |
| Sat 12 | 0 | 0.0 | 75 ms | 0 |
| Sat 15 | 0 | 0.0 | 183 ms | 0 |
| Sat 17 | 0 | 0.0 | 165 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 TravelJoy 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 TravelJoy 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 TravelJoy (traveljoy.com) as part of the Money group. From first reply to final payment, TravelJoy makes it easy for you to book your ideal client faster, with less legwork.
TravelJoy publishes an official status page at status.traveljoy.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, 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: 152 ms average, 56–277 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TravelJoy incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
152 ms on average over the last 24 hours (56–277 ms).
Yes, at https://status.traveljoy.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report TravelJoy here at once, the problem is on TravelJoy'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 TravelJoy. 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.