Resolved after 4 hours 12 minutes, affecting API and Portal and Slough, on July 13, 2026.
We have some out of hours house-keeping to do here but this incident is otherwise resolved. We will be monitoring for a few hours before closing to be certain.
Affected components
Update timeline
- identified Jul 13, 2026, 02:29 PM UTC
We have lost hardware in Slough. Voice services have failed over as expected and are unaffected. Most other services have recovered too although we are currently dealing with some Redis master failures elsewhere on the network. This will manifest in portal logins and writing to selected API end-points. Separately CDR processing is several million delayed so API balances etc. will not be current. We are recovering Redis clusters as P1 and will advise progress.
- identified Jul 13, 2026, 03:13 PM UTC
Portal and API (v4) are now fully operational. CDRs remain lagged.
- identified Jul 13, 2026, 04:04 PM UTC
CDRs are now being processed at full speed and catching up rapidly.
- monitoring Jul 13, 2026, 04:39 PM UTC
We have some out of hours house-keeping to do here but this incident is otherwise resolved. We will be monitoring for a few hours before closing to be certain.
- resolved Jul 13, 2026, 06:41 PM UTC
This incident has been resolved.
Your product runs on more than Simwood
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services