Fetch.ai Outage History
5 incidents recorded over the last 365 days. 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 Fetch.ai Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 1, 2026 | Fetchhub Mainnet Upgrade v0.15.0The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| May 18, 2026 | Dorado upgradeThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| May 7, 2026 | Agentverse MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 11, 2025 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Dec 11, 2025 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 5h 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 Fetch.ai 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 Fetch.ai 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 Fetch.ai 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 Fetch.ai outage in this window ran 5h, against a mean recovery of 3h 24m. If you depend on Fetch.ai 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.