Survicate Outage History
9 incidents recorded over the last 365 days, 9 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 Survicate Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 7, 2026 | Login failure after accepting company invitationNew invitations works as desired now. | 16h 8m | Resolved |
| Jun 25, 2026 | Issues with showing AI follow-ups in Text answer questionsThe issues with AI follow-up questions not being generated have been resolved. All survey questions are fully operational. | 2h 7m | Resolved |
| Apr 1, 2026 | Degraded performance for Google Sheets integrationThe Google Sheets integration is fully operational now. | 15h 36m | Resolved |
| Mar 19, 2026 | Issues with logging in and accessing workspacesWe have identified the root cause of the incident. The issue was caused by a faulty deployment that introduced a bug in the organization details endpoint, resulting in errors for some organizations. There has been **no… | 25 min | Resolved |
| Feb 20, 2026 | GoogleSheets integration degraded performanceThe Google Sheets integration is fully operational now. | 58h 10m | Resolved |
| Feb 20, 2026 | BigQuery integration degraded performanceData delivery in the BigQuery integration is back to normal. We apologize for the inconvenience this caused and thank you for your patience throughout this period. | 161h 1m | Resolved |
| Nov 18, 2025 | Partial Survey Disruption - Cloudflare OutageAll the surveys are now operating normally. We appreciate your patience. | 2h 47m | Resolved |
| Nov 6, 2025 | Microsoft Teams Integration currently unavailable.Microsoft Team integration is fully operational now | 1h 35m | Resolved |
| Nov 5, 2025 | Panel Loading DegradationThe issue causing slow loading times of the Survicate panel has been resolved. We're very sorry for the inconvenience and your patience while we worked to restore full functionality. | 49 min | 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 Survicate 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 Survicate 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 Survicate 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 Survicate outage in this window ran 6d 17h, against a mean recovery of 1d 4h. If you depend on Survicate 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.