GetFeedback Outage History
9 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 GetFeedback Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 7, 2026 | Scheduled maintenance - GetFeedback help centerWe will be undergoing scheduled maintenance during this time. | 3h 0m | Scheduled |
| Oct 21, 2026 | Urgent preventive security maintenanceIncident is Resolved. GetFeedback is back online. We finished the preventive security maintenance and have the needed protections in place. We see no evidence of a security breach or any compromise of customer data. | 7h 21m | Resolved |
| Oct 6, 2026 | Database UpgradeThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jul 14, 2026 | Customers are unable to contact support through our Help Center chatbotThis incident has been resolved. | 51 min | Resolved |
| Jul 6, 2026 | Upcoming platform maintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jul 1, 2026 | Upcoming Platform MaintenanceThe scheduled maintenance has been completed. | 7h 0m | Scheduled |
| Feb 18, 2026 | GetFeedback Direct (https://app.getfeedback.com/) is downThis incident has been resolved. | 1h 41m | Resolved |
| Nov 26, 2025 | Checkbox questions for In-Page Widgets not gathering dataThis incident has been resolved. If you still face issues, please re-save your widget and try again. | 4h 2m | Resolved |
| Nov 18, 2025 | GetFeedback Direct MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 GetFeedback 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 GetFeedback 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 GetFeedback 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 GetFeedback outage in this window ran 7h 21m, against a mean recovery of 3h 26m. If you depend on GetFeedback 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.