Forethought AI Outage History
10 incidents recorded over the last 365 days, 9 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 Forethought AI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 10, 2026 | Database MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Jul 9, 2026 | Elevated errors loading Solve WidgetThis incident has been fully resolved. The Solve Widget is now loading normally for all customers, and our monitoring confirms that performance and traffic have returned to stable levels following the rollback. | 22 min | Resolved |
| Apr 2, 2026 | Solve Voice Call Quality DegradationThis incident has been resolved. | 19 min | Resolved |
| Mar 23, 2026 | Solve Voice Call Quality DegradationThis incident has been resolved | 44 min | Resolved |
| Feb 3, 2026 | Dashboard OutageThis incident has been resolved. The issue looks to have resulted from the earlier Cloudflare outage. Dashboard is now stable. | 2h 49m | Resolved |
| Feb 3, 2026 | Invalid Solve Conversations in Dashboard InsightsThis incident has been resolved. | 30h 5m | Resolved |
| Jan 9, 2026 | Third-Party Outage: Intercom Connectivity IssuesThis incident has been resolved. | 1h 6m | Resolved |
| Jan 9, 2026 | Analytics Visibility IssuesThis incident has been resolved. | 5h 3m | Resolved |
| Dec 2, 2025 | Solve Voice OutageThis incident has been resolved. | 1h 54m | Resolved |
| Nov 18, 2025 | Elevated API Errors due to Cloudflare Global Network OutageThis incident has been resolved. | 1h 44m | Resolved |
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 Forethought 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 Forethought 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 Forethought 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 Forethought AI outage in this window ran 1d 6h, against a mean recovery of 4h 55m. If you depend on Forethought 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.