AWS use1-az4 thermal event
May 8, 02:22 UTCMay 8, 19:22 UTC
Duration
17h
Impact
Informational
Root cause
Not disclosed
PlanetScale, 90 days
8 incidents
Affected
Not listed by the vendor.
Final update
PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.
Timeline
- Resolved · May 8, 19:22 UTC
PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.
- Monitoring · May 8, 02:22 UTC
PlanetScale is aware of the AWS use1-az4 thermal event. We expect databases to be unaffected. Please contact support if you have any questions or notice any disruption.
More from PlanetScale
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 518:39 UTC | Connectivity issues with Vitess databases in GCP | major | 14m |
| Sep 216:34 UTC | Dashboard and API 500 errors for postgres databases | major | 10m |
| Jul 2414:41 UTC | Insights metrics underreporting | major | 3h |
| Jul 2018:29 UTC | Insights metrics underreporting | minor | 20h 49m |
| Jul 1820:32 UTC | Connectivity issues in us-east-1 | major | 33m |
| Jul 1716:41 UTC | API and dashboard errors | major | 28m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.