80%
“Approximately 80% of our initial incident-response workflow is now automated.”
As published on incident.io, August 2026. Captured by usedby on Oct 7, 2026.
What happened
Kaizen Gaming's Site Reliability team uses incident.io to automate the start of major incidents, including creating Slack channels, assigning roles, paging responders and notifying stakeholders. It also manages customer-facing status pages across its markets from the same incident record, and tracks post-incident follow-up actions.
Summary written by usedby from the source page, in English. The figures are those of incident.io and Kaizen Gaming, not ours.
- two minutes“The initial response workflow launches in under two minutes, compared with five to ten minutes previously.”
- 20 status pages“Following a one-month phased rollout, Kaizen Gaming migrated its incident-response workflows and 20 status pages to incident.io.”
- one working day“Today, the equivalent end-to-end process can be completed within one working day.”
Approximately 80% of our initial incident-response workflow is now automated. The team can spend less time administering the incident and more time resolving it.
The hardest part of an incident isn't always the technical problem. It's coordinating the response.
What the story claims, and what we checked
We compared the story with its live page on Oct 7, 2026.
- The figure: 80%CheckedPrinted word for word on the page, near the name of Kaizen Gaming.
- The passage quoted aboveCheckedCopied word for word from the page, near the name of Kaizen Gaming.
- The publication dateCheckedRead from the page’s own metadata, never guessed.
- Kaizen Gaming uses incident.ioCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
- The result itselfNot checkedWe quote it; we did not measure it.




