Customer Thermometer Outage History
4 incidents recorded over the last 365 days, 4 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 Customer Thermometer Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | Feedback Management invalid links within summary emailsOur engineers have confirmed that the previous issue has been resolved. Thank you for your patience. | -3 min | Resolved |
| Oct 24, 2026 | Platform maintenanceScheduled maintenance is currently in progress. There might be some disruption to responses left, which will be queued and then later processed after the maintenance window has closed. Some notifications may be… | 40h 58m | Resolved |
| Dec 5, 2025 | Cloudflare internal server errorWe have received confirmation that the earlier outage by Cloudflare is now fully resolved. Cloudflare has issued a statement with a root cause analysis: https://blog.cloudflare.com/5-december-2025-outage/ | 3h 0m | Resolved |
| Nov 18, 2025 | Cloudflare Global Network experiencing issuesCloudflare engineers have confirmed that the previous service alert has been resolved and they have closed the [incident](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). | 4h 9m | 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 Customer Thermometer 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 Customer Thermometer 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 Customer Thermometer 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 Customer Thermometer outage in this window ran 1d 16h, against a mean recovery of 16h 2m. If you depend on Customer Thermometer 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.