Focsec Outage History

Type: Incident Duration: 5 hours Affected Components: API Oct 9, 07:05:00 GMT+0 - Resolved - The outage was caused by a backend system process failing, all backend systems automatically recovered within 60 seconds. The operations team continues to investigating the root cause. Oct 9, 06:35:00 GMT+0 - Resolved - This system has fully recovered. We are currently investigating this incident. Oct 9, 06:30:00 GMT+0 - Investigating - We are seeing a increased error rate on all /ip API endpoints, resulting in error 500\. We are currently investigating this incident.

This system has fully recovered. We are currently investigating this incident.

The outage was caused by a backend system process failing, all backend systems automatically recovered within 60 seconds. The operations team continues to investigating the root cause.

Type: Incident Duration: 5 minutes Affected Components: API, Account management Oct 18, 06:17:00 GMT+0 - Investigating - We are seeing a increase in API errors resulting in error 500 and 503\. We are currently investigating this incident. Oct 18, 06:22:00 GMT+0 - Resolved - This incident has been resolved. The root cause was a short (< 20 second) internal network outage on our hosting infrastructure. We apologize for any inconvenience caused.

Type: Maintenance Duration: 30 days Affected Components: Billing, invoices and payments, Account management Aug 10, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 11, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 11, 07:00:00 GMT+0 - Identified - Over the next few days, we are upgrading our email configuration to improve deliverability. During this time, emails from Focsec may arrive with a delay or may be flagged as spam. If you are missing any emails, please check for spam folder. API operations are not affected.

Type: Incident Duration: 1 hour and 38 minutes Affected Components: API May 13, 10:12:00 GMT+0 - Resolved - This incident has been resolved. The cause was a misconfiguration during a update. We apologize for an inconvenience this may have caused. May 13, 09:58:03 GMT+0 - Investigating - We are currently investigating a issue that prevents detecting TOR IPs and downloading the TOR database.

Type: Incident Duration: 2 minutes Affected Components: API Nov 18, 22:04:27 GMT+0 - Resolved - This incident has been resolved. The root cause was a temporary network outage on one of our backend nodes. All API endpoints are back to normal now. We apologize for any inconvenience this may have caused. Nov 18, 22:02:04 GMT+0 - Investigating - A small percentage (<1%) of API requests are resulting in error 502, error 503 or error 504\. We are currently investigating this incident.