Back to overview
False alerts for downtime
Apr 07 at 12:50pm EDT
Affected services
CPU functions on AWS
Volumes
Resolved
Apr 07 at 12:50pm EDT
We hit a limit on our internal workspace used to run synthetic monitors, which caused our downtime alerts to fire inaccurately. We have raised the limits now.
No users were affected. We're sorry for all the spam for status page subscribers!
Affected services
CPU functions on AWS
Volumes