All Systems Operational
Management Console - Aperture   Operational
Real Time Metrics and Logs   Operational
API   Operational
North America Operational
Virginia   Operational
Iowa   Operational
Illinois   Operational
Texas   Operational
California   Operational
Toronto   Operational
Quebec City   Operational
Ohio   Operational
Oregon   Operational
Montreal   Operational
South America Operational
São Paulo   Operational
Europe Operational
Ireland   Operational
Netherlands   Operational
Frankfurt   Operational
Magdeburg   Operational
Cardiff   Operational
London   Operational
Asia Pacific Operational
Singapore   Operational
Hong Kong   Operational
Sydney   Operational
Melbourne   Operational
Pune   Operational
Mumbai   Operational
Chennai   Operational
Tokyo   Operational
Osaka   Operational
Seoul   Operational
Real User Monitoring   Operational
DNS   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 22, 2018

No incidents reported today.

May 21, 2018

No incidents reported.

May 20, 2018

No incidents reported.

May 19, 2018

No incidents reported.

May 18, 2018

No incidents reported.

May 17, 2018

No incidents reported.

May 16, 2018

No incidents reported.

May 15, 2018

No incidents reported.

May 14, 2018

No incidents reported.

May 13, 2018

No incidents reported.

May 12, 2018

No incidents reported.

May 11, 2018

No incidents reported.

May 10, 2018

No incidents reported.

May 9, 2018

No incidents reported.

May 8, 2018
Resolved - This incident has been resolved.
May 8, 22:17 UTC
Monitoring - We have completed the manual intervention on the Threat-X WAF and are entering a monitoring state.
May 7, 22:06 UTC
Identified - Customers running the Threat-X WAF are currently affected by this issue. Changes at the central management system at Threat-X have caused the delivery proxies to consume high rates of CPU, resulting in request failures.

Engineering at section.io is currently intervening on each instance of the Threat-X proxy. Systems are recovering and complete recovery should be complete within fifteen minutes.
May 7, 21:43 UTC
Investigating - We are currently investigating a high rate of HTTP request failures
May 7, 21:10 UTC