Skip to content

Outage tracker

FreeAgent: incident history

The last 24 hours in detail, FreeAgent's declared incident record, and our regional check results beside it.

← Back to FreeAgent's check readings

We started checking FreeAgent on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when FreeAgent reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is FreeAgent's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what FreeAgent's own status page declared. Below it, any public chatter we saw about FreeAgent and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what FreeAgent's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about FreeAgent in the last 24 hours, which is not evidence that nothing is wrong.
FreeAgent's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is FreeAgent's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention FreeAgent next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%583
US-West100.00%442
Europe100.00%403
Asia-Pacific100.00%244

Their declared record

FreeAgent's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Smart Capture DelaysMinor incident
Apr 7, 2026, 2:53 PM UTC to Apr 7, 2026, 3:54 PM UTC (1h 1m)resolved
their latest update (Apr 7, 2026, 3:54 PM UTC): Smart Capture service has resumed. Some captures have failed to extract data and may need to be retried, we apologise for the inconvenience.
Some customers may have issues accessing FreeAgentPartial outage
Mar 12, 2026, 3:01 PM UTC to Mar 12, 2026, 3:24 PM UTC (24 min)resolved
their latest update (Mar 12, 2026, 3:24 PM UTC): This incident has been resolved.
FreeAgent is unavailableMajor outage
Feb 2, 2026, 10:28 AM UTC to Feb 2, 2026, 10:34 AM UTC (6 min)resolved
their latest update (Feb 2, 2026, 10:34 AM UTC): This incident has been resolved.
Some customers getting redirected to our fraud pageMinor incident
Aug 14, 2025, 8:32 AM UTC to Aug 18, 2025, 11:25 AM UTC (4d 2h)resolved
their latest update (Aug 18, 2025, 11:25 AM UTC): This incident has been resolved.
Duplicate transactions appearing for some Mettle usersAll systems operational
Jul 1, 2025, 11:40 AM UTC to Jul 2, 2025, 12:04 PM UTC (1d 0h)resolved
their latest update (Jul 2, 2025, 12:04 PM UTC): This incident has been resolved.
Email Delivery IssuesAll systems operational
Jul 1, 2025, 10:26 AM UTC to Jul 2, 2025, 7:01 AM UTC (20h 35m)resolved
their latest update (Jul 2, 2025, 7:01 AM UTC): We have had confirmation from our email provider that this issue has been resolved. Between approximately June 30, 2025 at 9:47pm BST to July 1, 2025 at 1:21pm BST, an IP was listed for spam causing some customers emails to not be sent. If you sent emails within this timeframe, …
Customers blocked from logging into FreeAgentPartial outage
Apr 25, 2025, 1:57 PM UTC to Apr 25, 2025, 2:33 PM UTC (36 min)resolved
their latest update (Apr 25, 2025, 2:33 PM UTC): This incident has now been resolved and customers should be able to login into their accounts again.
Emails to Google Email accounts being marked as spamAll systems operational
Mar 24, 2025, 4:28 PM UTC to Mar 25, 2025, 9:30 AM UTC (17h 1m)resolved
their latest update (Mar 25, 2025, 9:30 AM UTC): This incident is now resolved. Emails sent from the FreeAgent app to Google email accounts should no longer be marked as spam for recipients. Our vendor, working with Google, deployed a fix at 2025-03-24 23:04 UTC. They continued to monitor email delivery and declared the issue …
Knowledge Base cannot be accessedAll systems operational
Feb 28, 2025, 11:30 AM UTC to Feb 28, 2025, 12:28 PM UTC (59 min)resolved
their latest update (Feb 28, 2025, 12:28 PM UTC): The issues around accessing the Knowledge Base have now been resolved.
Website issues at www.freeagent.comMinor incident
Feb 18, 2025, 3:10 PM UTC to Feb 18, 2025, 4:30 PM UTC (1h 20m)resolved
their latest update (Feb 18, 2025, 4:30 PM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents FreeAgent has declared in the history we hold.

These entries are FreeAgent's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

FreeAgent's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.