CustomerGauge Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded CustomerGauge Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 7, 2026 | SMS and WhatsApp sending disruptionThe issue affecting SMS and WhatsApp message delivery has now been resolved by our third-party messaging provider. Messages are being sent as expected again, and our services are operating normally. We apologise for… | 1h 44m | Resolved |
| Sep 9, 2026 | Elevated Errors in ReportsReporting services have been restored, and reports are available again. We’ll continue monitoring the service to ensure it remains stable. | 42 min | Resolved |
| Jul 10, 2026 | Resolved - Email Delivery RestoredThe issue affecting email delivery for campaigns using Custom Email Sender Domains has been fully resolved. Email delivery is operating normally, and we are currently reprocessing emails that previously failed with a… | 1h 14m | Resolved |
| Mar 18, 2026 | 401 Unauthorized errors for PUT Record, PATCH Survey Record, and PUT Personal LinkWe identified and resolved an issue that caused some PUT Record, PATCH Survey Record, and PUT Personal Link requests to return 401 Unauthorized errors instead of executing successfully between 11:01-14:12 in EU and… | -353 min | Resolved |
| Mar 18, 2026 | Elevated report loading errors in EU regionThis incident has been resolved. We’ve received confirmation from impacted customers that report loading is working as expected again. | 2h 41m | Resolved |
| Feb 16, 2026 | Issue with Pop-up Surveys (In-Application Surveys) being presentedWe have experienced an issue with our Pop-Up Surveys (In-Application Surveys) being presented. For most end recipients, the pop-up surveys would not have been presented to, during this incident window. This issue was… | -5969 min | Resolved |
| Feb 12, 2026 | Issue with Manual data upload, Incoming Webhooks and Native IntegrationsOur team has successfully resolved the issue, and all new imports should now process successfully. You should no longer encounter the error at this time. No data has been compromised or lost, it was just not possible… | 3h 37m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next CustomerGauge incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This CustomerGauge Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CustomerGauge acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single CustomerGauge outage in this window ran 3h 37m, against a mean recovery of 1h 60m. If you depend on CustomerGauge in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.