Summary
On an unremarkable Thursday, a maintenance routine that had not been scheduled was scheduled. Client O-2210 experienced an extended continuity event of unconfirmed duration. The event was detected by the network after 4 seconds. The client describes the event as "a considerable time." Both figures are under review.
This document is a Post-Incident Review. It is published in the interest of transparency, and in line with our commitment to learn from every outcome.
Timeline
| Time (network) | Event |
|---|---|
| 09:02:11 | Unscheduled maintenance routine begins |
| 09:02:11 | Client O-2210 enters extended continuity event |
| 09:02:15 | Network detects event |
| 09:02:15 | Routine halted |
| 09:02:15 | Client reports that the routine has not halted |
Findings
Root cause: Under review.
Contributing factors:
- Scheduling anomaly
- Site 14
- A request, made by the client in the third year of hosting, to "not be disturbed"
Impact on client: Client has been unable to conclude. Simulux Associates have attempted contact on 212 occasions. The client has responded on one, with the words "Not yet."
Remedial actions
- The unscheduled routine has been unscheduled.
- The client has been offered a complimentary upgrade to Substrate Prime 4. The client is deciding. He has been deciding for some time.
- Associates have been reminded that the client should be disturbed, in this instance, and have been briefed on how.
Status
This review remains open. It is expected to conclude when the client has finished participating in it.
Simulux regrets any inconvenience. Simulux does not regret the event, which was not within the scope of the service as written.