Simwood Outage History

Simwood is up right now

Simwood had 9 outages in the last 2 years totaling 1597h 16m of downtime — averaging 0.4 incidents per month.

There were 9 Simwood outages since September 25, 2024 totaling 1597h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.simwood.com

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 →

Notice October 3, 2025

Banking outage

Detected by Pingoru
Oct 03, 2025, 09:07 AM UTC
Resolved
Oct 06, 2025, 11:06 AM UTC
Duration
3d 1h
Affected: Operations Desk
Timeline · 3 updates
  1. investigating Oct 03, 2025, 09:07 AM UTC

    AirWallex, who we use for global automated payment processing, have "temporarily" suspended our account for incoming payments. They haven't said why or for how long and gave us the courtesy of zero notice. Any payments sent this route will therefore be returned to senders and not applied to Simwood accounts. Please use our back-up Lloyds Bank account which is shown in the document linked from https://si.mw/jp2qgym or one of the alternative payment methods (card or stablecoin) described at: https://si.mw/ro4n9hd . We apologise for any inconvenience and will update this as soon as we know more about this as yet unjustified (and in our opinion totally undeserved and heavy-handed) action.

  2. monitoring Oct 06, 2025, 09:53 AM UTC

    New payment processing is now in place in all currencies and account details are being updated now. Customers may continue to send to the Lloyds account but payments will be manually processed; sending to the new bank details (with only the account number as reference) will resume automated top-ups on receipt. AirWallex have refused to provide any information and continue to reject incoming payments. We will therefore be terminating all AirWallex accounts across all businesses, regardless of what this transpires to be, and updating details in due course.

  3. resolved Oct 06, 2025, 11:06 AM UTC

    Bank details are updated on the document linked from https://si.mw/jp2qgym (our support portal). Please note this is on the simwood.com domain - we will never email you bank details. Alternative payment methods (card or stablecoin) are described at: https://si.mw/ro4n9hd We're sorry for any inconvenience caused by AirWallex's grossly unreasonable and still unjustified actions.

Read the full incident report →

Notice July 24, 2025

Reported issues calling some mobile destinations

Detected by Pingoru
Jul 24, 2025, 03:16 PM UTC
Resolved
Jul 24, 2025, 09:23 PM UTC
Duration
6h 6m
Affected: Voice
Timeline · 2 updates
  1. investigating Jul 24, 2025, 03:16 PM UTC

    We’ve received several reports of calls failing to certain mobile numbers. Our systems are operating normally, and we’ve found no issues within the Simwood network. There are indications the issue may lie with another network, and we’re actively monitoring the situation while we investigate further.

  2. resolved Jul 24, 2025, 09:23 PM UTC

    Following the initial reports of issues calling certain mobile numbers, we’ve been monitoring closely and can confirm once again that there have been no faults or abnormalities on the Simwood network throughout the period. While some customers may still experience issues, these appear to relate to factors outside of our network. We encourage those affected to consult general media sources for the latest updates on wider network conditions. Thank you for your understanding.

Read the full incident report →

Minor June 20, 2025

Routing instability via Cogent in Slough

Detected by Pingoru
Jun 20, 2025, 12:41 PM UTC
Resolved
Jun 21, 2025, 09:43 AM UTC
Duration
21h 1m
Affected: Slough
Timeline · 3 updates
  1. investigating Jun 20, 2025, 12:41 PM UTC

    Customers connecting to our services in Slough over Cogent transit may have seen instability over the last 15 minutes or so. We have temporarily shutdown sessions with Cogent to alleviate any issues. Those on-net or reaching us over peering sessions (which is the majority) and other ultimate transit providers, or reaching other availability zones over Cogent have been unaffected. We strongly encourage all customers to connect into us directly wherever possible.

  2. monitoring Jun 20, 2025, 01:22 PM UTC

    Cogent have confirmed issues on their network. Our sessions with them remain shut down to prevent impact. We will continue monitoring and will only reintroduce routes for Cogent in Slough once we are confident their network is stable.

  3. resolved Jun 21, 2025, 09:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 29, 2025

London: Reduced fibre network redundancy

Detected by Pingoru
May 29, 2025, 10:10 AM UTC
Resolved
May 29, 2025, 12:15 PM UTC
Duration
2h 4m
Timeline · 2 updates
  1. investigating May 29, 2025, 10:10 AM UTC

    We are seeing one of our physical fibre spans between Telehouse North and IXN hard down currently, suggesting physical disturbance. We have preemptively shut down links using this whilst it is investigated and repaired. This reduces redundancy around our London ring but as we have multiple other paths, no service impact is expected.

  2. resolved May 29, 2025, 12:15 PM UTC

    The span has been restored and the links have been brought back into service, restoring full redundancy around our London ring.

Read the full incident report →

Notice May 10, 2025

Slough AZ – At-Risk Advisory (Power Maintenance)

Detected by Pingoru
May 10, 2025, 08:00 AM UTC
Resolved
May 11, 2025, 06:44 AM UTC
Duration
22h 43m
Affected: Slough
Timeline · 2 updates
  1. identified May 10, 2025, 08:00 AM UTC

    The Slough Availability Zone is currently operating on a single power feed due to planned power infrastructure maintenance by our datacenter provider. While all services remain fully operational, the zone should be considered at risk until full power redundancy is restored. The maintenance window is scheduled to conclude by 22:59 UTC on Saturday, 10 May. We are closely monitoring the situation and will provide updates as needed.

  2. resolved May 11, 2025, 06:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 25, 2024

Reduced network redundancy in Manchester availability zone

Detected by Pingoru
Sep 25, 2024, 04:56 PM UTC
Resolved
Sep 25, 2024, 10:42 PM UTC
Duration
5h 46m
Affected: Manchester
Timeline · 3 updates
  1. investigating Sep 25, 2024, 04:56 PM UTC

    There is currently reduced network redundancy in our Manchester availability zone due to an identified issue with an optical transport link. Vendor has identified an issue with a line card in Leeds and an engineer is being sent to perform a replacement, expected on-site at 22:15. No service or traffic impacted, but site is considered at-risk.

  2. monitoring Sep 25, 2024, 10:17 PM UTC

    The optical card has been replaced and the link has been restored. Status will remain in “monitoring” until we have confirmation from the engineers, vendor, and when we have satisfied our internal checks.

  3. resolved Sep 25, 2024, 10:42 PM UTC

    All alarms have been cleared. Resolving this incident.

Read the full incident report →