Executive summary

Generated from the week’s records. Every sentence carries the record it came from.

Generated07:00 EAT, 1 September · covers

Payments held; billing is where the week was lost

The week carried two Sev 1 incidents, both in billing rather than payments. Prepaid billing overran its nightly batch on Tuesday and again on Thursday INC0048198 INC0048174, delaying statement generation for roughly 40 minutes each time. No customer-facing payment path was interrupted in either window.

Daraja API produced the week’s highest incident count: sixteen, of which eleven share the connection-pool signature already tracked as an open problem record PRB0003318. The workaround in the runbook resolved every one of them KB0010992; the underlying cause remains unconfirmed.

Nine changes ran to plan. One was rolled back: a USSD certificate rotation that failed verification on the second node CHG0011142. It was rescheduled for tonight.

Two audit findings passed their due date without closure IA-2025-114 IA-2025-097. Both relate to monitoring coverage on the token issuance path, which is the same path the Daraja incidents run through.

What this summary could not see
Teams conversations were excluded this week; ingestion is behind a feature flag pending the DPIA. Service telemetry is not ingested at all, so nothing here describes performance, only recorded incidents. This is a view onto ServiceNow and Outlook, not a position of record.
Sev 1 incidents
2
+1 vs last week
Mean time to restore
1h 47m
−22m vs last week
Derived from ServiceNow state changes, not from telemetry.
Sources behind this
ServiceNow118 records
Outlook calendar31 entries
Documents6 findings
Microsoft Teamsexcluded
See every citation