User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 1169 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 | 771 ms | 0 |
| Tue 02 | 0 | 0.0 | 903 ms | 0 |
| Tue 04 | 0 | 0.0 | 435 ms | 0 |
| Tue 06 | 0 | 0.0 | 1500 ms | 0 |
| Tue 08 | 0 | 0.0 | 1291 ms | 0 |
| Tue 10 | 0 | 0.0 | 1017 ms | 0 |
| Tue 12 | 0 | 0.0 | 1040 ms | 0 |
| Tue 15 | 0 | 0.0 | 1019 ms | 0 |
| Tue 17 | 0 | 0.0 | 1155 ms | 0 |
| Tue 19 | 0 | 0.0 | 1669 ms | 0 |
| Tue 21 | 0 | 0.0 | 1126 ms | 0 |
| Wed 00 | 0 | 0.0 | 886 ms | 0 |
| Wed 02 | 0 | 0.0 | 1862 ms | 0 |
| Wed 04 | 0 | 0.0 | 1050 ms | 0 |
| Wed 06 | 0 | 0.0 | 1222 ms | 0 |
| Wed 09 | 0 | 0.0 | 886 ms | 0 |
| Wed 11 | 0 | 0.0 | 730 ms | 0 |
| Wed 13 | 0 | 0.0 | 838 ms | 0 |
| Wed 15 | 0 | 0.0 | 686 ms | 0 |
| Wed 17 | 0 | 0.0 | 1725 ms | 0 |
| Wed 19 | 0 | 0.0 | 1043 ms | 0 |
| Wed 22 | 0 | 0.0 | 1464 ms | 0 |
| Thu 00 | 0 | 0.0 | 1491 ms | 0 |
| Thu 02 | 0 | 0.0 | 2008 ms | 0 |
| Thu 04 | 0 | 0.0 | 1287 ms | 0 |
| Thu 06 | 0 | 0.0 | 1527 ms | 0 |
| Thu 08 | 0 | 0.0 | 862 ms | 0 |
| Thu 10 | 0 | 0.0 | 884 ms | 0 |
| Thu 12 | 0 | 0.0 | 1122 ms | 0 |
| Thu 14 | 0 | 0.0 | 1458 ms | 0 |
| Thu 16 | 0 | 0.0 | 1323 ms | 0 |
| Thu 18 | 0 | 0.0 | 913 ms | 0 |
| Thu 20 | 0 | 0.0 | 1315 ms | 0 |
| Thu 22 | 0 | 0.0 | 1318 ms | 0 |
| Fri 00 | 0 | 0.0 | 336 ms | 0 |
| Fri 03 | 0 | 0.0 | 940 ms | 0 |
| Fri 05 | 0 | 0.0 | 1062 ms | 0 |
| Fri 07 | 0 | 0.0 | 697 ms | 0 |
| Fri 09 | 0 | 0.0 | 517 ms | 0 |
| Fri 11 | 0 | 0.0 | 946 ms | 0 |
| Fri 13 | 0 | 0.0 | 1193 ms | 0 |
| Fri 15 | 0 | 0.0 | 1019 ms | 0 |
| Fri 17 | 0 | 0.0 | 1630 ms | 0 |
| Fri 19 | 0 | 0.0 | 665 ms | 0 |
| Fri 21 | 0 | 0.0 | 1021 ms | 0 |
| Fri 23 | 0 | 0.0 | 1115 ms | 0 |
| Sat 01 | 0 | 0.0 | 1417 ms | 0 |
| Sat 03 | 0 | 0.0 | 1169 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Cymbal 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 Cymbal goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cymbal alerts to Slack, Discord or a webhook — free.
Cymbal is listed in our Productivity category and checked at cymbal.co. Cymbal is event marketing software that integrates with your ticketing to send emails, texts, DMs, and run paid ads measured against tickets sold.
Cymbal publishes an official status page at status.cymbal.co; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1039 ms average, 517–1630 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Cymbal incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1039 ms on average over the last 24 hours (517–1630 ms).
Yes, at https://status.cymbal.co.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Cymbal here at once, the problem is on Cymbal'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 Cymbal. 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.