Simwood Status
All Systems Operational
Network ? Operational
90 days ago
100.0 % uptime
Today
London Network   ? Operational
90 days ago
100.0 % uptime
Today
Slough Network   ? Operational
90 days ago
100.0 % uptime
Today
Manchester Network   ? Operational
90 days ago
100.0 % uptime
Today
Wholesale VoIP Operational
90 days ago
100.0 % uptime
Today
London   ? Operational
90 days ago
100.0 % uptime
Today
Slough   ? Operational
90 days ago
100.0 % uptime
Today
Manchester   ? Operational
90 days ago
100.0 % uptime
Today
Customer Interfaces Operational
90 days ago
100.0 % uptime
Today
API   ? Operational
90 days ago
100.0 % uptime
Today
Portal   ? Operational
90 days ago
100.0 % uptime
Today
Support Operational
90 days ago
100.0 % uptime
Today
Operations Desk   ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jul 16, 2018

No incidents reported today.

Jul 15, 2018

No incidents reported.

Jul 14, 2018
Completed - The maintenance has been completed as planned.

Some customers may have noticed misleading channel counts during this window as forewarned, and as a result channel limits may not have been enforced correctly. We're also aware a small number of customers saw some calls rejected due to channel limits, where they were unable to burst beyond their allocation, we apologise for any inconvenience this caused. Once this was identified, enforcement of limits was temporarily suspended.
Jul 14, 12:34 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 14, 08:12 UTC
Scheduled - We are planning upgrades to our Redis cluster, and undertaking further resilience testing on the changes deployed in recent maintenance similar to those previously announced in April.

We have scheduled this when the network is quietest, and are confident this is very unlikely to affect production voice traffic but may impact statistics displayed in the portal or retrieved via the API, additionally there is a small chance that channel and rate limits will not work as expected during this time. In the event that our limiting experiences issues we operate on a 'fail safe' basis where our platform will disregard channel limits, ensuring calls complete, rather than limit calls based on out of date information about current use.

As a precaution, services should be considered AT RISK during this maintenance window.
Jul 9, 11:16 UTC
Jul 13, 2018
Resolved - This incident has been resolved and channel statistics should now be accurate, additionally channel limits should now be enforced as normal.

Please accept our apologies for any inconvenience this may have caused.
Jul 13, 15:21 UTC
Identified - We're continuing to investigate this, it seems that some channels are being added but not being removed upon call completion, particularly on shorter duration calls, as a result some channel counters are being artificially inflated.

We're working on this as a priority, and apologies for any inconvenience this causes. Calls are completing as normal, but channel information may be incorrectly reported.
Jul 13, 12:27 UTC
Investigating - We are aware of an issue where channel utilisation may be incorrectly reported, and as a result there is a risk that some limits were incorrectly applied.

As a precautionary measure, you may find that per-trunk channel limits are not currently applied.
Jul 13, 11:39 UTC
Jul 12, 2018
Resolved - We have been monitoring this for some time and are confident that the issue is now resolved.

More information will follow.
Jul 12, 13:18 UTC
Monitoring - This should now be resolved, and we're continuing to monitor the situation. Normal routing has been restored.
Jul 12, 10:58 UTC
Identified - We have identified the cause of these failures and, as a precaution, temporarily re-routed most traffic to another availability zone.
Jul 12, 10:27 UTC
Investigating - We are investigating sporadic reports of calls failing with a 480 or 407 error, more information will be provided as soon as it becomes available.
Jul 12, 10:00 UTC
Jul 11, 2018

No incidents reported.

Jul 10, 2018
Resolved - This incident has been resolved.
Jul 10, 19:04 UTC
Monitoring - We have implemented a fix for this, and the network should have been stable from around 1530.

We're continuing to investigate the underlying cause.
Jul 10, 14:54 UTC
Identified - We are currently investigating an issue affecting return traffic to a small number of customer IPs, notably those which send traffic sporadically, that are not directly connected to Simwood.

This issue appears to be due to some IPs that are disappearing from the top prefix list, on one router but not on another, which can cause a loop for a few seconds until the lists synchronise. Our network engineers are investigating this as a priority.

There is a helpful presentation discussing how we use Selective Route Download (SRD) at http://blog.simwood.com/2017/09/our-talk-at-linx98-sdn-without-the-bs/ which might better explain how this usually works.

All customers who are directly connected, or connected to us via private peering, are unaffected. Additionally, the vast majority of customers reaching us over the public internet are also unaffected.
Jul 10, 14:49 UTC
Jul 9, 2018

No incidents reported.

Jul 8, 2018

No incidents reported.

Jul 7, 2018

No incidents reported.

Jul 6, 2018

No incidents reported.

Jul 5, 2018

No incidents reported.

Jul 4, 2018

No incidents reported.

Jul 3, 2018

No incidents reported.

Jul 2, 2018
Resolved - This issue has now been resolved, please accept our apologies for any inconvenience caused.
Jul 2, 17:18 UTC
Identified - We are aware of an issue affecting retrieval of Invoices via the Simwood Portal.

Invoices will still have been eMailed as normal, and the API is unaffected. We're working to resolve this as a priority but, in the interim, if you need a copy Invoice please contact the Operations Desk who will be happy to help.

Please accept our apologies for any inconvenience caused.
Jul 2, 09:03 UTC