Jasper: Elevated errors caused by a Google Cloud incident
Timeline of updates
- resolved
Sep 1, 16:50 UTC
Resolved - The issue is now resolved.Sep 1, 16:41 UTC
Monitoring - Between 14:39 and 15:52 UTC, some generation requests and knowledge uploads failed. The cause was a Google Cloud networking incident in the us-central1 region affecting Cloud SQL, which made one of our databases unreachable. Service has since recovered and we are continuing to monitor.
This was a third-party provider issue. Google's incident details are available here: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev (opens in new tab)
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.jasper.ai (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Jasper, started 2026-09-01 16:41 UTC, resolved after 9 min, 1 update(s).
- Title
- Elevated errors caused by a Google Cloud incident
- Vendor
- Jasper
- Date
- URL
- https://rewindex.com/company/jasper/incidents/437c3640-3442-411a-aa2c-141b40c49620
Jasper profileRecent Jasper incidentsAll outages on September 1, 2026Jasper in September 2026MarkdownJSON