Simwood Status
All Systems Operational
Voice ? Operational
90 days ago
100.0 % uptime
Today
API and Portal ? Operational
90 days ago
99.48 % 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
99.99 % uptime
Today
San Jose (US West) Operational
90 days ago
100.0 % uptime
Today
New York (US East) Operational
90 days ago
99.99 % 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
May 25, 2019

No incidents reported today.

May 24, 2019

No incidents reported.

May 23, 2019
Resolved - This incident has been resolved.
May 23, 10:30 UTC
Update - This is now fully resolved.
May 23, 10:30 UTC
Monitoring - A fix has been implemented for this and we're continuing to monitor the situation closely.

CDRs are still backlogged, but we're processing these as fast as possible and this should be completed shortly, however, the information available in the API and portal may be slightly delayed.

Provisioning should now work as expected, and the porting desk is operating normally. Any numbers due to port will be processed shortly.
May 23, 09:21 UTC
Identified - The issue has been identified and a fix is being implemented.
May 23, 07:27 UTC
Investigating - We're presently unable to write CDRs so billing will be delayed. Number provisioning (including porting) is also not possible at this time along with other operations which require writing to our primary database cluster. This does not affect call routing or primary services as they do not use the database.

Earlier this morning one of the nodes in the cluster restarted and it is being synched across the network from others. Normally it uses one, leaving another available for writes, but this time it is using two. That sync needs to conclude from at least one node before writes can resume.

To repeat, this does not affect call routing or reading from the API or portal, only making changes that require writing to permanent storage.
May 23, 07:26 UTC
May 22, 2019

No incidents reported.

May 21, 2019

No incidents reported.

May 20, 2019

No incidents reported.

May 19, 2019

No incidents reported.

May 18, 2019

No incidents reported.

May 17, 2019

No incidents reported.

May 16, 2019

No incidents reported.

May 15, 2019
Completed - The scheduled maintenance has been completed.
May 15, 21:59 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 20:01 UTC
Scheduled - We are upgrading fibre MUXs between our London sites as part of our normal capacity planning. Links between sites will be taken down one at a time and brought back into service before moving onto the next.

Whilst we anticipate no interruption to service during this, and routing of customer traffic will not be affected, it is prudent to consider these sites AT RISK during this time.
Apr 26, 10:54 UTC
Resolved - This incident has been resolved.
May 15, 15:33 UTC
Monitoring - This morning we experienced a hardware failure in Manchester which resulted in the failure of a database node. As a result, there were some earlier delays with CDR processing as the database resynced, and the information provided in the API and Portal may not have been up-to-date.

The Simwood Blog also remains temporarily offline as a result of this, and we're working to restore it.

Calls and messaging were unaffected throughout, and no core services were affected or unavailable. Our normal processes to ensure consistency and continuity of data worked, although introduced delays that were longer than expected and we are looking into how to improve resilience in the future to minimise these.

We are continuing to monitor the situation, and working to resolve the issue with the Manchester site.
May 14, 08:19 UTC
Completed - The scheduled maintenance has been completed.
May 15, 02:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 20:00 UTC
Scheduled - We are upgrading fibre MUXs between our London sites as part of our normal capacity planning. Links between sites will be taken down one at a time and brought back into service before moving onto the next.

Whilst we anticipate no interruption to service during this, and routing of customer traffic will not be affected, it is prudent to consider these sites AT RISK during this time.
Apr 26, 10:54 UTC
May 14, 2019
Completed - The scheduled maintenance has been completed.
May 14, 02:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 20:00 UTC
Scheduled - We are upgrading fibre MUXs between our London sites as part of our normal capacity planning. Links between sites will be taken down one at a time and brought back into service before moving onto the next.

Whilst we anticipate no interruption to service during this, and routing of customer traffic will not be affected, it is prudent to consider these sites AT RISK during this time.
Apr 26, 10:54 UTC
May 12, 2019

No incidents reported.

May 11, 2019

No incidents reported.