User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
tuple.app · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests tuple.app from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1142 ms · 6 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 651 ms | 0 |
| 03:30 | 0 | 0.0 | 271 ms | 0 |
| 03:45 | 0 | 0.0 | 455 ms | 0 |
| 04:00 | 0 | 0.0 | 483 ms | 0 |
| 04:15 | 0 | 0.0 | 760 ms | 0 |
| 04:30 | 0 | 0.0 | 474 ms | 0 |
| 04:45 | 0 | 0.0 | 397 ms | 0 |
| 05:00 | 0 | 0.0 | 828 ms | 0 |
| 05:15 | 0 | 0.0 | 338 ms | 0 |
| 05:30 | 0 | 0.0 | 287 ms | 0 |
| 05:45 | 0 | 0.0 | 481 ms | 0 |
| 06:00 | 0 | 0.0 | 351 ms | 0 |
| 06:15 | 0 | 0.0 | 388 ms | 0 |
| 06:30 | 0 | 0.0 | 324 ms | 0 |
| 06:45 | 0 | 0.0 | 299 ms | 0 |
| 07:00 | 0 | 0.0 | 842 ms | 0 |
| 07:15 | 0 | 0.0 | 583 ms | 0 |
| 07:30 | 0 | 0.0 | 439 ms | 0 |
| 07:45 | 0 | 0.0 | 366 ms | 0 |
| 08:00 | 0 | 0.0 | 209 ms | 0 |
| 08:15 | 0 | 0.0 | 450 ms | 0 |
| 08:30 | 0 | 0.0 | 360 ms | 0 |
| 08:45 | 0 | 0.0 | 216 ms | 0 |
| 09:00 | 0 | 0.0 | 381 ms | 0 |
| 09:15 | 0 | 0.0 | 487 ms | 0 |
| 09:30 | 0 | 0.0 | 1268 ms | 0 |
| 09:45 | 0 | 0.0 | 120 ms | 0 |
| 10:00 | 0 | 0.0 | 676 ms | 0 |
| 10:15 | 0 | 0.0 | 343 ms | 0 |
| 10:30 | 0 | 0.0 | 415 ms | 0 |
| 10:45 | 0 | 0.0 | 427 ms | 0 |
| 11:00 | 0 | 0.0 | 369 ms | 0 |
| 11:15 | 0 | 0.0 | 931 ms | 0 |
| 11:30 | 0 | 0.0 | 351 ms | 0 |
| 11:45 | 0 | 0.0 | 316 ms | 0 |
| 12:00 | 0 | 0.0 | 280 ms | 0 |
| 12:15 | 0 | 0.0 | 1258 ms | 0 |
| 12:30 | 0 | 0.0 | 553 ms | 0 |
| 12:45 | 0 | 0.0 | 940 ms | 0 |
| 13:00 | 0 | 0.0 | 507 ms | 0 |
| 13:15 | 0 | 0.0 | 777 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tuple 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 Tuple goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tuple alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Tuple is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Tuple's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.