Simwood Status
All Systems Operational
Voice ? Operational
90 days ago
100.0 % uptime
Today
API and Portal ? Operational
90 days ago
99.86 % 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
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Nov 13, 2019

No incidents reported today.

Nov 12, 2019

No incidents reported.

Nov 11, 2019

No incidents reported.

Nov 10, 2019

No incidents reported.

Nov 9, 2019

No incidents reported.

Nov 8, 2019

No incidents reported.

Nov 7, 2019

No incidents reported.

Nov 6, 2019

No incidents reported.

Nov 5, 2019

No incidents reported.

Nov 4, 2019

No incidents reported.

Nov 3, 2019
Completed - The scheduled maintenance has been completed.
Nov 3, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 06:00 UTC
Scheduled - We will be performing maintenance on one of our container hosts in Volta as part of planned maintenance on Sunday morning. We do not anticipate any impact to services but will be shifting traffic away from London for the duration out of caution.

Site specific IP addresses will failover between nodes but may see brief windows of inaccessibility. DNS will be updated to direct traffic to other sites for customers configured in accordance with our interop. Our interop specifies that customers should not send directly to an IP address and, if doing so is unavoidable or for those with wrongly cached DNS, 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.
Nov 1, 17:05 UTC
Nov 2, 2019

No incidents reported.

Nov 1, 2019
Resolved - This was resolved as of 1615.

We are aware that some customers are continuing to receive messages from earlier, this is as a result of them being queued upstream of Simwood and we cannot control when the originating network retries where the message could not be delivered initially.

Please accept our apologies for any inconvenience caused.
Nov 1, 16:52 UTC
Identified - We are aware of an issue affecting some SMS message deliverability and are investigating. Some customers may experience delays in inbound and outbound SMS.

This incident will be updated with more information as soon as it is available.
Nov 1, 14:39 UTC
Resolved - Normal service was restored at 1045, and the backlogged CDRs were processed entirely by 1300.

This has been monitored continuously since and has operated as expected.

Please accept our apologies for any inconvenience this caused.
Nov 1, 16:50 UTC
Monitoring - We believe this is now resolved and are continuing to monitor the situation.

The Portal and API should function as expected, although CDRs will remain backlogged on some accounts for a short time.

Will will update this incident further when complete.
Nov 1, 10:45 UTC
Investigating - We are experiencing performance issues with our primary database cluster and are investigating as a priority. As a result, you may experience issues with the performance of the API and Portal; new provisioning and reconfiguration of numbering is not possible, and CDRs are currently lagging behind live.

Normal calling and messaging services are unaffected, as these are completely isolated from the primary database.

Please accept our apologies for any inconvenience this causes. We will update this incident with further information as soon as it becomes available.
Nov 1, 08:52 UTC
Oct 31, 2019

No incidents reported.

Oct 30, 2019

No incidents reported.