- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 100
What to do
Check whether your product depends on StatusCake. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2022-05-31 09:44 UTC and 2022-05-31 00:00 UTC may need a replay.Subscribe to StatusCake's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=statuscake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from StatusCake 2
- resolved
An error occurred between 1:00AM - 7:00AM that prevented Push tests to be sent to StatusCake, which led to tests appearing as 'down', The cause was an SSL certificate, which failed to update as expected. The problem has now been resolved and all services are running as normal.
provider
- postmortem
We proactively updated our servers to include a new SSL certificate but unfortunately the provider reverted the changes during a live migration failure. this led to the certificate not being updated, and instead serving an expired certificate. The certificate has now been updated, and push tests are working as expected
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c61be4499f
Is StatusCake still down?
No, this incident was resolved 2022-05-31 00:00 UTC. For StatusCake's live state, see https://down.guide/statuscake.
How long did it last?
0m, from 2022-05-31 09:44 UTC to 2022-05-31 00:00 UTC, by the times StatusCake posted.
What caused it?
StatusCake hasn't published a root cause. If it does, it shows here.
Where does this come from?
StatusCake's official status page, https://status.statuscake.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.