Feefo logo

Is Feefo Down?

SaaSLive status, outages, and incident history

No. Feefo is up right now.

Every monitored Feefo system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Feefo breaks

Feefo is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Feefo status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Feefo Component Status

The main Feefo systems on this page. All 26 are operational right now.

26operational
APIs » Authentication
Operational
APIs » Entersaleremotely
Operational
APIs » Product Ratings
Operational

23 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking APIs » Reviews, APIs » WebHooks, Feedback Process » Feedback Form, Feedback Process » Feedback Requests, Feedback Process » Places, Feefo Hub » Feedback, Feefo Hub » Login, Feefo Hub » Products, Feefo Hub » Reports, Feefo Hub » Sales Uploads, Feefo Support Platform - Ticketing System, Review Display » Feefo Merchant Page, and 11 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Feefo Outages & Incidents

Incident history from the official Feefo status page, including resolution updates.

Ongoing issues with syndicated feedback over the weekendResolved Aug 10, 2026 · 218h 51mResolved

Our monitoring period has concluded successfully. All reporting and syndication feeds remain fully operational and stable. Thank you again for your patience. --- [2026-08-15T17:06:05.747+01:00] (monitoring) The data refresh has successfully completed, and all reporting and syndication feeds are now fully up to date. Our team will continue to monitor performance throughout the weekend as a precaution. Thank you again for your patience and understanding while we worked to resolve this! --- [2026-08-14T16:56:29.930+01:00] (identified) Our Data Team has identified the cause of the delay and applied a fix to prevent further timeouts. A data refresh is currently running to bring all reporting and syndication feeds back up to date. The regular automated system will run overnight, with manual backups in place throughout the weekend if needed. We are hopeful these issues will be resolved soon and will provide another update once everything is verified. Please rest assured that all incoming feedback continues to be safely captured with zero data loss. Thank you for your patience! --- [2026-08-13T17:21:42.391+01:00] (investigating) Our Data Team has identified a solution and is currently investigating a potential fix to restore our automated reporting and syndication feeds that have been effected. To minimize disruption, our team is manually processing data in the interim to keep daily reporting as current as possible. All incoming feedback continues to be safely captured with zero data loss. We will provide another update as soon as a permanent fix is fully in place and verified. --- [2026-08-11T12:34:26.696+01:00] (investigating) We are continuing to actively investigate the issue where feedback submitted since Friday, August 7th is not loading into our reporting or syndication pipelines. There are no new updates at this time. Please rest assured that all incoming feedback is still being safely captured without data loss. Metrics and syndicated feeds will remain temporarily delayed while our Data Team works toward a resolution. We will share another update as soon as new information becomes available. --- [2026-08-10T12:19:13.263+01:00] (investigating) We are actively investigating an issue where feedback submitted since Friday, August 7th is not loading into our reporting or syndication pipelines. All incoming feedback continues to be safely captured, but metrics and syndicated feeds relying on this data will be temporarily delayed while our Data Team works to resolve the issue.

Investigating API IssuesResolved Aug 5, 2026 · 54h 24mResolved

We have completed testing and confirmed that the issue has been fully resolved. Thank you for your continued patience. --- [2026-08-07T11:17:57.469+01:00] (identified) Testing on the Download Feedback API remains underway. We are currently running an automated script to address the underlying issue and are actively monitoring its progress. Because the duration of this process depends on database processing times, we are unable to provide an exact estimated time of completion at present. We will provide another status update as soon as the script completes or if any further developments occur. Thank you for your continued patience. --- [2026-08-06T17:31:36.777+01:00] (identified) We are continuing to perform maintenance on the Download Feedback API but were unable to come to a final resolution today, we are currently testing a possible solution and hope to have a full resolution tomorrow (07/08/2026). --- [2026-08-06T10:07:46.510+01:00] (identified) We believe we have identified the root cause of the issue effecting our Download Feedback API and the Download Feedback function in the Feefo Hub. A fix is being tested and upon confirmation of successful resolution, this fix will be applied to our production environment. We hope to have this issue resolved in full by the end of the day (06/08/2026). Thank you for your continued patience. --- [2026-08-05T17:19:10.838+01:00] (investigating) Testing is still underway for the identified fix regarding the 500 errors with our Download Feedback API and Feefo Hub feedback downloads. We currently expect the fix to be potentially ready for release tomorrow. We will provide another update as testing concludes or new details become available. --- [2026-08-05T15:06:33.602+01:00] (investigating) We are currently investigating intermittent 500 errors impacting the Download Feedback API and downloading feedback through the Feefo Hub. Our engineering team has identified a potential fix and is currently testing the resolution. We will share another update as soon as testing is complete. --- [2026-08-05T11:29:32.529+01:00] (investigating) We are currently experiencing performance issues with our Download Feedback API, resulting in 500 errors. Applications and integrations may encounter errors when requesting or providing information related to downloading feedback. Our engineering team is investigating the cause as a priority and will update this page shortly. Please be aware this issue only effects our Download Feedback API, all other APIs are currently working as expected.

Feedback request processingResolved Jul 20, 2026 · 23h 48mResolved

The feedback request backlog will now have cleared and service has returned to normal. Thank you for your patience. --- [2026-07-20T17:19:32.329+01:00] (monitoring) Our engineering teams have made progress to identify the cause of this outage and have begun monitoring feedback requests that have begun to send as expected. We will continue to monitor this until service has returned to normal. Thank you for your patience. --- [2026-07-20T11:02:28.225+01:00] (investigating) We are currently investigating an issue impacting the processing of feedback requests, causing a backlog waiting to send for some of our customers. ur engineering team is actively investigating the root cause as a matter of priority. We apologise for the disruption and will provide further updates here as soon as we have more information.

Feefo Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Feefo incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 7 days with incidentsSep 25

Live Feefo Outage Reports

Problems reported by engineers using Feefo. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Feefo problems reported yet.

Something wrong with Feefo on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Feefo

Is Feefo down? Feefo reports live availability for 31 components at status.feefo.com, among them Login, Integration Widgets and Feedback Requests (Email, SMS). Track Feefo outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Feefo uptime at 100.00%. Response times, incident history, and SLA tracking for Feefo are available on the PulsAPI dashboard.

Feefo Status FAQ

Is Feefo down right now?

The verdict at the top of this page comes from the latest poll of the official Feefo status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Feefo is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Feefo recovers.

How do I check Feefo uptime history?

PulsAPI tracks Feefo uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Feefo changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Feefo outages?

PulsAPI reads the official Feefo status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Feefo components?

Yes. PulsAPI monitors 26 individual Feefo components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Feefo goes down?

Yes. Create a free account and subscribe to Feefo: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Feefo to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Feefo problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Feefo?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Feefo plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Feefo with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services