Feefo Outage History
9 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 Feefo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Significant outage to all inbound trafficWe are pleased to confirm that our cloud provider has fully resolved the underlying power issue. All Feefo services have successfully stabilised and are operating at their normal speeds. We apologise for any… | 4h 4m | Resolved |
| Aug 10, 2026 | Ongoing issues with syndicated feedback over the weekendOur monitoring period has concluded successfully. All reporting and syndication feeds remain fully operational and stable. Thank you again for your patience. | 218h 51m | Resolved |
| Aug 5, 2026 | Investigating API IssuesWe have completed testing and confirmed that the issue has been fully resolved. Thank you for your continued patience. | 54h 24m | Resolved |
| Jul 20, 2026 | Feedback request processingThe feedback request backlog will now have cleared and service has returned to normal. Thank you for your patience. | 23h 48m | Resolved |
| Jul 17, 2026 | Ticketing System MaintenanceScheduled maintenance completed. | 48h 0m | Scheduled |
| Jun 10, 2026 | Degraded Performance of the Feefo Platform.This incident has now been resolved. This incident was a result of a Google service incident across their London data centres. Preliminary root cause was identified as an issue within Googles network infrastructure… | 4h 57m | Resolved |
| May 22, 2026 | API Latency IssuesThis issue has now been resolved, thanks for your patience. | 23 min | Resolved |
| May 4, 2026 | Feefo Widgets & API Latency IssuesThis issue has now been resolved, thanks for your patience. | 1h 59m | Resolved |
| Mar 25, 2026 | Status Page MigrationThe migration to our new shiny status page is complete, please subscribe to updates at https://status.feefo.com. | 48h 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 Feefo 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 Feefo 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 Feefo 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 Feefo outage in this window ran 9d 2h, against a mean recovery of 1d 20h. If you depend on Feefo 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.