Simwood Outage History
Uptime record, past incidents, and downtime history for Simwood.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 100% | 15 | 0 |
| July 2026 | 96.8% | 31 | 1 |
| June 2026 | 96.7% | 30 | 1 |
| May 2026 | 100% | 15 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
May 17
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
Slough hardware outage
Started: Jul 13, 2:29 PM
monitoring
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.
Jul 13, 4:39 PM
identified
CDRs are now being processed at full speed and catching up rapidly.
Jul 13, 4:04 PM
identified
Portal and API (v4) are now fully operational. CDRs remain lagged.
Jul 13, 3:13 PM
identified
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.
Jul 13, 2:29 PM
June 2026
Reduced network redundancy in Slough availability zone
Started: Jun 15, 10:17 AM
identified
Our transport provider has identified the fault location and fibre engineers are due to the location at 13:30 to begin repairs.
Jun 15, 11:34 AM
identified
Reduced network redundancy in our Slough AZ. An optical link back to central London is currently down, and traffic is being routed via alternative paths while we work with the transport provider to restore the link. AZ considered at risk.
Jun 15, 10:17 AM