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 169 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 127 ms | 0 |
| Mon 14 | 0 | 0.0 | 121 ms | 0 |
| Mon 16 | 0 | 0.0 | 184 ms | 0 |
| Mon 18 | 0 | 0.0 | 81 ms | 0 |
| Mon 21 | 0 | 0.0 | 138 ms | 0 |
| Mon 23 | 0 | 0.0 | 168 ms | 0 |
| Tue 01 | 0 | 0.0 | 163 ms | 0 |
| Tue 03 | 0 | 0.0 | 115 ms | 0 |
| Tue 05 | 0 | 0.0 | 155 ms | 0 |
| Tue 07 | 0 | 0.0 | 144 ms | 0 |
| Tue 09 | 0 | 0.0 | 138 ms | 0 |
| Tue 11 | 0 | 0.0 | 148 ms | 0 |
| Tue 14 | 0 | 0.0 | 140 ms | 0 |
| Tue 16 | 0 | 0.0 | 144 ms | 0 |
| Tue 18 | 0 | 0.0 | 141 ms | 0 |
| Tue 20 | 0 | 0.0 | 199 ms | 0 |
| Tue 23 | 0 | 0.0 | 182 ms | 0 |
| Wed 01 | 0 | 0.0 | 67 ms | 0 |
| Wed 03 | 0 | 0.0 | 66 ms | 0 |
| Wed 05 | 0 | 0.0 | 160 ms | 0 |
| Wed 08 | 0 | 0.0 | 100 ms | 0 |
| Wed 10 | 0 | 0.0 | 169 ms | 0 |
| Wed 12 | 0 | 0.0 | 159 ms | 0 |
| Wed 14 | 0 | 0.0 | 182 ms | 0 |
| Wed 16 | 0 | 0.0 | 155 ms | 0 |
| Wed 18 | 0 | 0.0 | 120 ms | 0 |
| Wed 21 | 0 | 0.0 | 176 ms | 0 |
| Wed 23 | 0 | 0.0 | 160 ms | 0 |
| Thu 01 | 0 | 0.0 | 221 ms | 0 |
| Thu 03 | 0 | 0.0 | 177 ms | 0 |
| Thu 05 | 0 | 0.0 | 171 ms | 0 |
| Thu 07 | 0 | 0.0 | 161 ms | 0 |
| Thu 09 | 0 | 0.0 | 111 ms | 0 |
| Thu 11 | 0 | 0.0 | 217 ms | 0 |
| Thu 13 | 0 | 0.0 | 102 ms | 0 |
| Thu 16 | 0 | 0.0 | 127 ms | 0 |
| Thu 18 | 0 | 0.0 | 207 ms | 0 |
| Thu 20 | 0 | 0.0 | 169 ms | 0 |
| Thu 22 | 0 | 0.0 | 124 ms | 0 |
| Thu 23 | 0 | 0.0 | 132 ms | 0 |
| Fri 01 | 0 | 0.0 | 151 ms | 0 |
| Fri 03 | 0 | 0.0 | 86 ms | 0 |
| Fri 05 | 0 | 0.0 | 196 ms | 0 |
| Fri 07 | 0 | 0.0 | 100 ms | 0 |
| Fri 10 | 0 | 0.0 | 146 ms | 0 |
| Fri 12 | 0 | 0.0 | 130 ms | 0 |
| Fri 14 | 0 | 0.0 | 122 ms | 0 |
| Fri 16 | 0 | 0.0 | 169 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 Singular 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 Singular goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Singular alerts to Slack, Discord or a webhook — free.
Singular is listed in our Productivity category and checked at singular.net. Unify your marketing data, measure true ROI, and unlock actionable insights with Singular’s AI-powered attribution and analytics platform
Singular publishes an official status page at status.singular.net; 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: 144 ms average, 86–207 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 Singular incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
144 ms on average over the last 24 hours (86–207 ms).
Yes, at https://status.singular.net.
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 Singular here at once, the problem is on Singular'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 Singular. 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.