Rehearsal of the status page
A drill that shows how an incident reads on this page. No service was affected.
Published:
This is a rehearsal, not an incident. No Skribly service was affected. It shows how an incident reads here, and it is removed once the first real incident has been written up.
Timeline
- 08:00 UTC, Investigating. What we saw: the symptom, and which sites it touches.
- 08:20 UTC, Identified. What we found to be the cause.
- 08:40 UTC, Monitoring. What we changed, and what we are watching.
- 09:00 UTC, Resolved. The sites answer again. A short note on what happens next.
How an incident is written
An incident is one Markdown file per language under status/src/content/incidents/. The newest update goes at the bottom of the timeline and the summary says where things stand now.