Is Sekoia FRA2 down?

Last checked 8m ago
Current status
Sekoia FRA2 is up

No incidents right now.

Official status page: https://status.fra2.sekoia.io · Polled every 5 minutes · 10 components tracked

Sekoia FRA2 is operational right now. Last checked 8m ago; the most recent incident resolved 25d ago.

Real-time Sekoia FRA2 status, recent outages, and incident history — pulled directly from Sekoia FRA2's official status page at https://status.fra2.sekoia.io every 5 minutes. Pingoru tracks 10 Sekoia FRA2 services and has captured 4 incidents in the last 90 days (98.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Sekoia FRA2 reports a new incident — free for 5 monitors, no credit card.

Users who monitor Sekoia FRA2 also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
Sekoia FRA2 uptime 98.33% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 59m
    Started Aug 21, 2026, 02:50 PM UTC · Resolved Aug 21, 2026, 03:49 PM UTC
    Web applicationEvent ingestion
    Timeline · 4 updates
    • investigating · Aug 21, 2026, 02:50 PM UTC

      We're witnessing inability to log in to the platform via SSO and some integrations intakes are experiencing connection issues. The symptoms are ConnectionError, 503 or HTTPSConnectionPool errors. Our engineering team is actively investigating the issue.

    • identified · Aug 21, 2026, 03:01 PM UTC

      The issue has been identified.

    • monitoring · Aug 21, 2026, 03:08 PM UTC

      A fix has been implemented. SSO login is now working as expected. There might be some delay with events being ingested. Our engineering team is monitoring the situation.

    • resolved · Aug 21, 2026, 03:49 PM UTC

      The incident is resolved. SSO and connectors are now working as expected.

    Latest: The incident is resolved. SSO and connectors are now working as expected.

  2. Resolved 1h 16m
    Started Jul 29, 2026, 02:10 PM UTC · Resolved Jul 29, 2026, 03:26 PM UTC
    Event ingestionDetectionQueries
    Timeline · 2 updates
    • monitoring · Jul 29, 2026, 02:59 PM UTC

      We are currently experiencing lag on our FRA2 event ingestion workflow due to the underlying storage layer issue. The issue is fixed, the platform is now catching up slowly on the backlog of events to process. We appreciate your patience and understanding while we work towards resolving this issue.

    • resolved · Jul 29, 2026, 03:26 PM UTC

      The platform has fully consumed the backlog. This incident has been resolved.

    Latest: The platform has fully consumed the backlog. This incident has been resolved.

  3. Resolved 2h 19m
    Started Jul 27, 2026, 06:43 PM UTC · Resolved Jul 27, 2026, 09:03 PM UTC
    Event ingestionEvent storageDetection
    Timeline · 4 updates
    • identified · Jul 27, 2026, 06:43 PM UTC

      We are currently facing an issue affecting our storage infrastructure. Our on-duty team is working to restore full operations as quickly as possible. We thank you for your patience during the resolution of this incident.

    • identified · Jul 27, 2026, 08:31 PM UTC

      Remedial actions have been taken to restore our services, and event ingestion appears to be operational again. We are currently monitoring the system closely to ensure complete stability. Another update will be provided once full recovery is confirmed.

    • identified · Jul 27, 2026, 09:02 PM UTC

      The issues experienced so far appear to be resolved. Core services have stabilized, and systems are currently operating normally. We are continuing to monitor performance closely to ensure sustained stability.

    • resolved · Jul 27, 2026, 09:03 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 7h 34m
    Started Jul 27, 2026, 08:09 AM UTC · Resolved Jul 27, 2026, 03:44 PM UTC
    Web applicationEvent ingestionEvent storageDetectionQueriesAutomationAI
    Timeline · 7 updates
    • investigating · Jul 27, 2026, 08:09 AM UTC

      Since approximately 09:00 UTC today, we are experiencing a performance degradation in our storage and processing infrastructure on FRA2. This is causing a growing delay in our data processing pipeline, which may affect how quickly data is indexed and available in the platform for affected customers.

    • investigating · Jul 27, 2026, 08:59 AM UTC

      Our engineering team is remediating the issue in multiple steps. Compute capacity on the affected storage infrastructure was previously increased and that change is now complete We will post an update within 30 minutes or sooner if the situation changes. Thank you for your understanding

    • investigating · Jul 27, 2026, 09:40 AM UTC

      While a reboot was attempted, it did not fully restore system health. We are currently diagnosing anomalies to ensure a safe recovery. Rest assured that our team is working to resolve this. As a precaution, we encourage you to enable client-side buffering mechanisms wherever possible. Thanks for your understanding

    • identified · Jul 27, 2026, 11:08 AM UTC

      Update - While our team is progressively restarting services ensure a safe recovery, performances are still impacted. Rest assured that our team is working to resolve this. As a precaution, we encourage you to enable client-side buffering mechanisms wherever possible. Thanks for your understanding

    • monitoring · Jul 27, 2026, 11:28 AM UTC

      Service has been restored. Our pipeline is currently processing the backlog, which is causing a temporary delay in event processing and alert creation. We expect this lag to clear over the next day. Our team is actively working to reduce this delay as much as possible. Thanks for your understanding

    • monitoring · Jul 27, 2026, 02:56 PM UTC

      Engineering has deployed additional capacity and fast recovery of the backlog is in progress; full normalization is expected shortly.

    • resolved · Jul 27, 2026, 03:44 PM UTC

      The incident in the region has been resolved. Core services have been restored, backlog processing has completed and event ingestion, alerting, and indexation are operating normally. Monitoring remains active for any residual delays. Thank you for your patience and understanding while we worked to resolve this incident.

    Latest: The incident in the region has been resolved. Core services have been restored, backlog processing has completed and event ingestion, alerting, and indexation are operating normall…

Outage history

Past 90 days · 4 incidents View full outage history →