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 33 min ago. Last stored result reached it in 291 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 230 ms | 0 |
| Tue 02 | 0 | 0.0 | 251 ms | 0 |
| Tue 04 | 0 | 0.0 | 236 ms | 0 |
| Tue 07 | 0 | 0.0 | 144 ms | 0 |
| Tue 09 | 0 | 0.0 | 167 ms | 0 |
| Tue 11 | 0 | 0.0 | 235 ms | 0 |
| Tue 13 | 0 | 0.0 | 309 ms | 0 |
| Tue 15 | 0 | 0.0 | 219 ms | 0 |
| Tue 17 | 0 | 0.0 | 216 ms | 0 |
| Tue 20 | 0 | 0.0 | 288 ms | 0 |
| Tue 22 | 0 | 0.0 | 174 ms | 0 |
| Wed 00 | 0 | 0.0 | 437 ms | 0 |
| Wed 02 | 0 | 0.0 | 525 ms | 0 |
| Wed 05 | 0 | 0.0 | 201 ms | 0 |
| Wed 07 | 0 | 0.0 | 176 ms | 0 |
| Wed 09 | 0 | 0.0 | 210 ms | 0 |
| Wed 11 | 0 | 0.0 | 207 ms | 0 |
| Wed 14 | 0 | 0.0 | 140 ms | 0 |
| Wed 16 | 0 | 0.0 | 778 ms | 0 |
| Wed 18 | 0 | 0.0 | 323 ms | 0 |
| Wed 20 | 0 | 0.0 | 197 ms | 0 |
| Wed 22 | 0 | 0.0 | 208 ms | 0 |
| Thu 00 | 0 | 0.0 | 279 ms | 0 |
| Thu 01 | 0 | 0.0 | 266 ms | 0 |
| Thu 03 | 0 | 0.0 | 229 ms | 0 |
| Thu 05 | 0 | 0.0 | 153 ms | 0 |
| Thu 07 | 0 | 0.0 | 146 ms | 0 |
| Thu 09 | 0 | 0.0 | 119 ms | 0 |
| Thu 11 | 0 | 0.0 | 173 ms | 0 |
| Thu 13 | 0 | 0.0 | 194 ms | 0 |
| Thu 15 | 0 | 0.0 | 381 ms | 0 |
| Thu 17 | 0 | 0.0 | 466 ms | 0 |
| Thu 19 | 0 | 0.0 | 170 ms | 0 |
| Thu 21 | 0 | 0.0 | 282 ms | 0 |
| Thu 23 | 0 | 0.0 | 139 ms | 0 |
| Fri 01 | 0 | 0.0 | 113 ms | 0 |
| Fri 03 | 0 | 0.0 | 276 ms | 0 |
| Fri 04 | 0 | 0.0 | 331 ms | 0 |
| Fri 06 | 0 | 0.0 | 163 ms | 0 |
| Fri 08 | 0 | 0.0 | 282 ms | 0 |
| Fri 10 | 0 | 0.0 | 110 ms | 0 |
| Fri 12 | 0 | 0.0 | 253 ms | 0 |
| Fri 14 | 0 | 0.0 | 232 ms | 0 |
| Fri 16 | 0 | 0.0 | 350 ms | 0 |
| Fri 17 | 0 | 0.0 | 361 ms | 0 |
| Fri 18 | 0 | 0.0 | 311 ms | 0 |
| Fri 20 | 0 | 0.0 | 270 ms | 0 |
| Fri 22 | 0 | 0.0 | 291 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Rekaz 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 Rekaz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rekaz alerts to Slack, Discord or a webhook — free.
Rekaz is listed in our Money category and checked at rekaz.io. Rekaz brings bookings, subscriptions, payments, staff, and customer communication into one operating system built for service businesses.
Rekaz publishes an official status page at status.rekaz.io; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 242 ms average, 39–361 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rekaz incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
242 ms on average over the last 24 hours (39–361 ms).
Yes, at https://status.rekaz.io.
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 Rekaz here at once, the problem is on Rekaz'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 Rekaz. 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.