Is Forethought Down?
- Forethought's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 177 ms
Right now
The verdict is the worse of these two. How we decide
Forethought's status page
status.forethought.ai · read · checked every 3 minutes
| Component | Status |
|---|---|
| Dashboard | Operational |
| Solve Widget | Operational |
| Solve Email | Operational |
| Solve Voice | Operational |
| Solve for Slack | Operational |
| Assist | Operational |
| API | Operational |
| Triage | Operational |
| Discover | Operational |
| Orchestrator | Operational |
FlareWarden checks
forethought.ai from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 177 ms
- Checked
By region
- Ashburn reachable, 197 ms
- Chicago reachable, 252 ms
- Frankfurt reachable, 98 ms
- Johannesburg reachable, 212 ms
- London reachable, 75 ms
- Los Angeles reachable, 225 ms
- São Paulo reachable, 307 ms
- Tokyo reachable, 56 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 134 ms | 1 ms | 8 ms | 191 ms |
| Chicago | 167 ms | 1 ms | 13 ms | 244 ms |
| Frankfurt | 37 ms | 2 ms | 11 ms | 90 ms |
| Johannesburg | 173 ms | 1 ms | 8 ms | 205 ms |
| London | 12 ms | 3 ms | 14 ms | 64 ms |
| Los Angeles | 149 ms | 3 ms | 14 ms | 214 ms |
| São Paulo | 232 ms | 2 ms | 13 ms | 299 ms |
| Tokyo | 11 ms | 1 ms | 7 ms | 50 ms |
History
Incidents Forethought reported
Since Nov 4, 2 days · from status.forethought.ai
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Forethought website availability
Measured by FlareWarden · forethought.ai
- Last 7 days
- —
- Last 30 days
- —
- Last 90 days
- —
- Avg response, 30 days
- —
Last 30 days
Measured by FlareWarden's own checks of forethought.ai from multiple regions every 6 hours. Forethought's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Forethought does
Forethought is a customer service AI platform: its AI agents answer customers in a website widget, by email, on the phone, and in Slack, and hand conversations to human agents in the company's helpdesk. Its status page lists the Dashboard, Solve (Widget, Email, Voice and Slack), Assist, Triage, Discover, Orchestrator and the API.
What an outage looks like
Incidents usually hit one channel. The Solve Widget failed to load for some customers on July 9, 2026 for about 25 minutes. Solve Voice calls sound different or degrade when a speech or communications provider fails, as on March 23 and April 2, and call transfers failed on October 21, 2025 during a Twilio disruption. The Dashboard was unavailable for all users on February 3, 2026 for about 2.8 hours.
What to do about it
Check status.forethought.ai for the channel your customers use: the Solve Widget, Solve Email, Solve Voice and Solve for Slack each have a row. Many incidents start at a provider, so check that provider too: Intercom for Intercom customers, Twilio for call transfers, and Cloudflare, which caused the November 18, 2025 API errors. During Solve Voice provider incidents Forethought has switched calls to a backup provider.
Is it down for everyone, or just you?
If this page says Forethought is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Forethought outage FAQ
Does a Forethought outage stop my helpdesk?
Why does Forethought's voice agent sound different?
Does a Cloudflare or AWS outage affect Forethought?
Why are my Forethought Dashboard numbers wrong?
How we measure this
- We request Forethought's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Forethought publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Forethought itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Forethought goes down
We check Forethought every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring