Simwood Outage History

Simwood is up right now

Simwood had 4 outages in the last 2 years totaling 1473h 42m of downtime — averaging 0.2 incidents per month.

There were 4 Simwood outages since August 14, 2025 totaling 1473h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.simwood.com

Minor July 13, 2026

Slough hardware outage

Detected by Pingoru
Jul 13, 2026, 02:29 PM UTC
Resolved
Jul 13, 2026, 06:41 PM UTC
Duration
4h 12m
Affected: API and PortalSlough
Timeline · 5 updates
  1. 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.

  2. identified Jul 13, 2026, 03:13 PM UTC

    Portal and API (v4) are now fully operational. CDRs remain lagged.

  3. identified Jul 13, 2026, 04:04 PM UTC

    CDRs are now being processed at full speed and catching up rapidly.

  4. 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.

  5. resolved Jul 13, 2026, 06:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 15, 2026

Reduced network redundancy in Slough availability zone

Detected by Pingoru
Jun 15, 2026, 10:17 AM UTC
Resolved
Jun 15, 2026, 03:17 PM UTC
Duration
5h
Affected: Slough
Timeline · 3 updates
  1. identified Jun 15, 2026, 10:17 AM UTC

    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.

  2. identified Jun 15, 2026, 11:34 AM UTC

    Our transport provider has identified the fault location and fibre engineers are due to the location at 13:30 to begin repairs.

  3. resolved Jun 15, 2026, 03:17 PM UTC

    The engineers attended an intermediate site along the affected route and found multiple fibre pairs had been damaged at the ODF there. These were replaced, testing has been completed, and the link has been restored with all alarms clear. We will continue to monitor.

Read the full incident report →

Notice December 24, 2025

Reduced media capacity in Manchester AZ

Detected by Pingoru
Dec 24, 2025, 10:40 AM UTC
Resolved
Dec 24, 2025, 04:01 PM UTC
Duration
5h 20m
Affected: Manchester
Timeline · 3 updates
  1. identified Dec 24, 2025, 10:40 AM UTC

    We are currently operating with reduced media capacity in our Manchester availability zone following a suspected hardware failure. There is no impact to services and calls are completing normally. Engineers are working to restore the affected hardware and capacity will be returned to normal in due course. In the meantime, our network is designed so that any single availability zone can carry the entire network load if all others fail. This update is for transparency only and no customer action is required.

  2. monitoring Dec 24, 2025, 12:07 PM UTC

    The affected hardware in our Manchester availability zone has been restored and reintroduced to the media pool. We are monitoring performance closely before marking this incident as fully resolved.

  3. resolved Dec 24, 2025, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →