Focsec Outage History

Focsec is up right now

Focsec had 6 outages in the last 2 years totaling 1h 1m of downtime, averaging 0.2 incidents per month.

There were 6 Focsec outages since November 18, 2024 totaling 1h 1m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: focsec.instatus.com

Minor October 9, 2026

Increased error rate on /ip API

Detected by Pingoru
Oct 09, 2026, 06:30 AM UTC
Resolved
Oct 09, 2026, 07:05 AM UTC
Duration
35m
Timeline · 3 updates
  1. investigating Oct 09, 2026, 06:30 AM UTC

    We are seeing a increased error rate on all /ip API endpoints, resulting in error 500\. We are currently investigating this incident..

  2. resolved Oct 09, 2026, 06:35 AM UTC

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

  3. resolved Oct 09, 2026, 07:05 AM UTC

    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. .

Read the full incident report →

Major October 9, 2026

Increased error rate on /ip API

Detected by Pingoru
Oct 09, 2026, 06:30 AM UTC
Resolved
Oct 09, 2026, 06:35 AM UTC
Duration
5m
Affected: API
Timeline · 3 updates
  1. investigating Oct 09, 2026, 06:30 AM UTC

    We are seeing a increased error rate on all /ip API endpoints, resulting in error 500\. We are currently investigating this incident.

  2. resolved Oct 09, 2026, 06:35 AM UTC

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

  3. resolved Oct 09, 2026, 07:05 AM UTC

    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.

Read the full incident report →

Minor October 18, 2025

API errors

Detected by Pingoru
Oct 18, 2025, 06:17 AM UTC
Resolved
Oct 18, 2025, 06:22 AM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Oct 18, 2025, 06:17 AM UTC

    We are seeing a increase in API errors resulting in error 500 and 503\. We are currently investigating this incident..

  2. resolved Oct 18, 2025, 06:22 AM UTC

    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..

Read the full incident report →

Minor May 13, 2025

TOR detection and database issue

Detected by Pingoru
May 13, 2025, 09:58 AM UTC
Resolved
May 13, 2025, 10:12 AM UTC
Duration
13m
Timeline · 2 updates
  1. investigating May 13, 2025, 09:58 AM UTC

    We are currently investigating a issue that prevents detecting TOR IPs and downloading the TOR database. .

  2. resolved May 13, 2025, 10:12 AM UTC

    This incident has been resolved. The cause was a misconfiguration during a update. We apologize for an inconvenience this may have caused..

Read the full incident report →

Major November 18, 2024

Temporary API outage

Detected by Pingoru
Nov 18, 2024, 10:02 PM UTC
Resolved
Nov 18, 2024, 10:04 PM UTC
Duration
2m
Timeline · 2 updates
  1. investigating Nov 18, 2024, 10:02 PM UTC

    A small percentage (<1%) of API requests are resulting in error 502, error 503 or error 504\. We are currently investigating this incident..

  2. resolved Nov 18, 2024, 10:04 PM UTC

    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..

Read the full incident report →