FreeAgent Outage History
7 incidents recorded over the last 365 days, 3 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 FreeAgent Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | At-risk periodScheduled maintenance is currently in progress. We will provide updates as necessary. | 1h 0m | Scheduled |
| Jun 17, 2026 | At-risk periodThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 7, 2026 | Smart Capture DelaysSmart Capture service has resumed. Some captures have failed to extract data and may need to be retried, we apologise for the inconvenience. | 1h 0m | Resolved |
| Apr 1, 2026 | At-risk periodThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 12, 2026 | Some customers may have issues accessing FreeAgentThis incident has been resolved. | 23 min | Resolved |
| Feb 2, 2026 | FreeAgent is unavailableThis incident has been resolved. | 5 min | Resolved |
| Nov 26, 2025 | At-risk periodThe 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 FreeAgent 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 FreeAgent 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 FreeAgent 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 FreeAgent outage in this window ran 1h, against a mean recovery of 47 min. If you depend on FreeAgent 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.