New Multi-region uptime checks and custom-domain status pages

Simwood Outage History

Daily provider-status observations and published incident history for Simwood.

Operational

Simwood is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Simwood for future changes.

100% of 37 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

2 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

July 2026
Slough hardware outage
minor Source not attested
Last archived state: resolved
View archived record details
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.
identified
CDRs are now being processed at full speed and catching up rapidly.
identified
Portal and API (v4) are now fully operational. CDRs remain lagged.
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.
June 2026
Reduced network redundancy in Slough availability zone
Source not attested
Last archived state: resolved
View archived record details
identified
Our transport provider has identified the fault location and fibre engineers are due to the location at 13:30 to begin repairs.
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.
Get alerts for Simwood Subscribe to the provider incident feed Browse all services