Skip to main content
StatusCake

New Public Reporting Pages temporarily not accepting CNAME

Degraded Lasted 3d · started · StatusCake's page

Level
confirmed
Worst impact
Degraded
Components
Public Reporting
Down Index
25of 100

What to do

  • Check whether you use StatusCake Public Reporting. 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 3d it lasted.

    Anything that failed between 2023-07-21 11:15 UTC and 2023-07-24 11:42 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

  1. investigating

    We are investigating an issue where new public reporting pages are not properly applying the CNAME configuration, no existing public reports would be affected, and we will have this resolved asap.

    provider

  2. resolved

    The issue has now been fully resolved

    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-4754b3377f

Is StatusCake still down?

No, this incident was resolved 2023-07-24 11:42 UTC. For StatusCake's live state, see https://down.guide/statuscake.

How long did it last?

3d, from 2023-07-21 11:15 UTC to 2023-07-24 11:42 UTC, by the times StatusCake posted.

What was affected?

StatusCake named Public Reporting.

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.