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
Past Incidents
Dec 15, 2018

No incidents reported today.

Dec 14, 2018

No incidents reported.

Dec 13, 2018

No incidents reported.

Dec 12, 2018

No incidents reported.

Dec 11, 2018

No incidents reported.

Dec 10, 2018

No incidents reported.

Dec 9, 2018

No incidents reported.

Dec 8, 2018

No incidents reported.

Dec 7, 2018
Resolved - O2 have announced that service is returning to normal and will be fully restored by around 0300.
Dec 7, 00:28 UTC
Identified - We are aware of an outage affecting the O2 4G LTE network nationally. For more information see https://status.o2.co.uk/

As a result, calls to some O2 numbers (and numbers ported to O2) may fail if the destination handset is on the 4G/LTE network. O2 is advising customers to disable 4G (using the 3G or 2G network which is working in most areas)

Whilst this fault is entirely outwith our control, we anticipate you will see a high number of call failures to O2 destinations as a result.
Dec 6, 09:44 UTC
Dec 5, 2018

No incidents reported.

Dec 4, 2018

No incidents reported.

Dec 3, 2018

No incidents reported.

Dec 2, 2018

No incidents reported.

Dec 1, 2018
Resolved - A small number of customers will have received duplicate invoices this morning with invoice numbers differing by one. Only the lower numbered invoice is valid and should be the only one visible in the portal; the second was sent but failed to commit as it was a duplicate. This was due to a legacy version of the code running in parallel and this has now been removed. Apologies for the inconvenience.
Dec 1, 09:43 UTC