Simwood Status
All Systems Operational
Voice   ? Operational
90 days ago
100.0 % uptime
Today
API and Portal   ? Operational
90 days ago
100.0 % uptime
Today
Availability Zones 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
Availability Zones (US) Operational
90 days ago
100.0 % uptime
Today
San Jose (US West)   Operational
90 days ago
100.0 % uptime
Today
New York (US East)   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
Scheduled Maintenance
Containerisation update - Slough Jan 26, 10:00 - Jan 27, 18:00 UTC
We will be rebuilding our container hosts in Slough to reflect a decision to change host operating system.

This will also involve failing our master database node over once maintenance is complete.

DNS will be updated to direct traffic to other sites for customers configured in accordance with our interop. Site specific IP addresses will failover between nodes yet our interop specifies that customers should not send directly to an IP address and, if doing so is unavoidable, customers should configure their own fail-over to other sites. Anycast services will be served from the next closest node but routing will change.

This maintenance should therefore not be service affecting but the network is considered at risk through a reduced level of redundancy during it.
Posted on Jan 13, 10:19 UTC
Containerisation update - London Volta Feb 9, 10:00 - Feb 10, 18:00 UTC
We will be rebuilding our container hosts in Volta to reflect a decision to change host operating system.

DNS will be updated to direct traffic to other sites for customers configured in accordance with our interop. Site specific IP addresses will failover between nodes yet our interop specifies that customers should not send directly to an IP address and, if doing so is unavoidable, customers should configure their own fail-over to other sites. Anycast services will be served from the next closest node but routing will change.

This maintenance should therefore not be service affecting but the network is considered at risk through a reduced level of redundancy during it.
Posted on Jan 13, 10:21 UTC
Past Incidents
Jan 23, 2019

No incidents reported today.

Jan 22, 2019

No incidents reported.

Jan 21, 2019

No incidents reported.

Jan 20, 2019
Completed - The scheduled maintenance has been completed.
Jan 20, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 19, 10:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jan 13, 10:14 UTC
Scheduled - We will be rebuilding our container hosts in Manchester to reflect a decision to change host operating system.

Manchester is technically deprecated and we advised changes running up to scaling it back in February, last August - http://blog.simwood.com/2018/08/network-changes/ . Therefore, Manchester specific SIP host names already point to other sites and whilst direct IP addresses still work, our interop specifies that customers should not send directly to an IP address and, if doing so is unavoidable, customers should configure their own fail-over to other sites. Therefore, whilst these addresses will go offline during this maintenance but it should not be service affecting for anyone configured properly.
Jan 13, 10:14 UTC
Jan 18, 2019

No incidents reported.

Jan 17, 2019

No incidents reported.

Jan 16, 2019

No incidents reported.

Jan 15, 2019

No incidents reported.

Jan 14, 2019

No incidents reported.

Jan 13, 2019

No incidents reported.

Jan 12, 2019

No incidents reported.

Jan 11, 2019
Resolved - This issue has been confirmed resolved and calls to all exported numbers are completing successfully.
Jan 11, 11:44 UTC
Monitoring - We believe this issue has been resolved, and have had confirmation of the same from one of the affected gaining providers.

We’ll continue to monitor this closely and ask other CPs if you experience issues with calls to Simwood numbers ported to your network to use the details provided in the GNP Contact Register to report this to us.

Please accept our apologies for any inconvenience caused.
Jan 11, 10:41 UTC
Investigating - We are investigating an issue where calls are failing to some numbers exported from Simwood, i.e. where Simwood is the LCP and the number has been ported to a new provider.

This is only affecting numbers exported to some other operators and we’re investigating as a priority.

No existing Simwood customer, or any number active on the Simwood network, is affected.

Please accept our apologies for any inconvenience this may cause.
Jan 11, 10:23 UTC
Jan 10, 2019
Completed - The scheduled maintenance has been completed.
Jan 10, 23:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 10, 21:01 UTC
Scheduled - Please accept our apologies for the short notice but we will be undertaking essential database maintenance this evening from 2100 UTC. No interruption to service is anticipated, but there is a possibility that some API or portal functionality will be reduced for a short time including the ability to provision, or configure, numbering and trunks.

Updates will be made via this page throughout, and when the works are complete.

Please accept our apologies for any inconvenience this may cause.
Jan 10, 17:54 UTC
Completed - This work has been completed without incident.
Jan 10, 23:01 UTC
Update - Please note, this maintenance is in the London site, following the successful completion of similar in Slough last night. We apologise that the earlier announcement incorrectly indicated these works were being carried out in Slough on both evenings.

Again, we do not anticipate any impact on services.
Jan 10, 19:53 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 10, 19:01 UTC
Scheduled - We will be undertaking planned maintenance as part of the works to upgrade our BT SS7 interconnects in Slough on the evenings of Wednesday 9th January and Thursday 10th January between 1900 and 0200 each day.

This has been scheduled for when the network is quiet so this will not be service affecting, but this work will result in brief periods of reduced capacity and reduced resilience therefore the service should be considered AT RISK during this time.
Jan 7, 10:51 UTC
Completed - The scheduled maintenance has been completed.
Jan 10, 00:34 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 9, 19:00 UTC
Scheduled - We will be undertaking planned maintenance as part of the works to upgrade our BT SS7 interconnects in Slough on the evenings of Wednesday 9th January and Thursday 10th January between 1900 and 0200 each day.

This has been scheduled for when the network is quiet so this will not be service affecting, but this work will result in brief periods of reduced capacity and reduced resilience therefore the service should be considered AT RISK during this time.
Jan 7, 10:50 UTC
Resolved - This incident has been resolved.
Jan 10, 00:15 UTC
Monitoring - We believe this is now resolved and are monitoring the situation.
Jan 9, 22:25 UTC
Investigating - We're aware of an intermittent issue affecting calls to some ported numbers. We're investigating this as a priority but it appears to affect a very limited number of calls, and only those originating from mobile networks or the London area.

More information will be provided as soon as possible.
Jan 9, 21:51 UTC