Focsec Outage History

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 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. Aug 10, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully

Type: Incident Duration: 1 hour and 38 minutes Affected Components: API May 13, 09:58:03 GMT+0 - Investigating - We are currently investigating a issue that prevents detecting TOR IPs and downloading the TOR database. 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.

Type: Incident Duration: 2 minutes Affected Components: API 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. 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.

Type: Incident Duration: 15 minutes Affected Components: API Jul 3, 13:23:31 GMT+0 - Investigating - The API request counts in the X-RequestLimit-RequestsMadeToday and X-RequestLimit-RequestsRemainingToday headers are not calculated correctly. As a result, the API request counts returned may be lower than your actual usage. Your actual API request limits are not affected by this. We are actively investigating this issue. Jul 3, 13:38:17 GMT+0 - Resolved - This incident has been resolved. API requests are now being counted correctly again. The overall API request count shown for today (2024-07-03) may be slightly lower than your actual usage. Your actual API request limits are not affected by this. We apologize for any inconvenience this may have caused.