Sekoia FRA1 Outage History
Sekoia FRA1 is up right nowPingoru has recorded 64 incidents for Sekoia FRA1: 64 in the last 12 months and 27 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 7 | 43 of 720 (6%) |
| May 2026 | 9 | 49 of 744 (7%) |
| June 2026 | 3 | 34 of 720 (5%) |
| July 2026 | 3 | 41 of 744 (6%) |
| August 2026 | 13 | 28 of 744 (4%) |
| September 2026 | 8 | 19 of 720 (3%) |
| October 2026 | 6 | 4 of 590 (1%) |
Incidents, newest first
Minor October 24, 2026 Delay in Events processing 33m Event ingestion, Detection
Started Oct 24, 2026, 05:46 PM UTC· resolved Oct 24, 2026, 06:20 PM UTC
- identified Oct 24, 2026, 05:46 PM UTC
Our engineering team has identified an issue with our ingestion pipeline. Remediation actions are in progress.
- resolved Oct 24, 2026, 06:20 PM UTC
Our Engineering team has completed remediation actions. All systems are operating in real time.
Minor October 22, 2026 Degraded performance – SOL and Elevate detection rules 58m Detection, AI
Started Oct 22, 2026, 08:02 AM UTC· resolved Oct 22, 2026, 09:01 AM UTC
- investigating Oct 22, 2026, 08:02 AM UTC
We are currently experiencing an issue affecting the service responsible for running SOL detection rules and Elevate. As a result, some detections may be delayed or not triggered as expected. Our team is actively working on resolving this issue as a top priority. We will provide an update as soon as we have more information. We apologize for any inconvenience this may cause.
- monitoring Oct 22, 2026, 08:09 AM UTC
The service responsible for running SOL detection rules and Elevate is gradually recovering. The backlog of pending events is currently being processed, so some detections may still be delayed for a short period. Our team is closely monitoring the situation until processing is fully back to normal. We will provide a final update once the backlog has been fully cleared. We apologize for any inconvenience this may cause.
- resolved Oct 22, 2026, 09:01 AM UTC
The issue affecting the service responsible for running SOL detection rules and Elevate has been resolved. The backlog has been fully processed and detections are now running normally, with no remaining impact. We will continue to monitor the service closely. We apologize for any inconvenience this may have caused and thank you for your patience.
Major October 14, 2026 Issues in loading events and alerts pages 40m Event ingestion, Detection
Started Oct 14, 2026, 03:15 PM UTC· resolved Oct 14, 2026, 03:55 PM UTC
- investigating Oct 14, 2026, 03:15 PM UTC
We are currently investigating issues in loading events and alerts pages. Our teams are working on identifying the issue. We'll provide an update as soon as we have more to share.
- identified Oct 14, 2026, 03:37 PM UTC
Our teams have identified the issue and are applying remediation actions. We expect loading to return to normal in the upcoming minutes.
- monitoring Oct 14, 2026, 03:41 PM UTC
The issue has been resolved, and loading seems to be working as expected. We are continuing to monitor the loading of both alerts and events pages.
- resolved Oct 14, 2026, 03:55 PM UTC
The service is operational. Thank you for bearing with us while we worked through the investigation and resolution.
Minor October 14, 2026 Web application slowness 9m Web application
Started Oct 14, 2026, 03:14 PM UTC· resolved Oct 14, 2026, 03:23 PM UTC
- investigating Oct 14, 2026, 03:14 PM UTC
Our Engineering team is investigating an issue impacting users experiencing slwness navigating the web application
Minor October 8, 2026 Latency on correlation process 30m Detection
Started Oct 08, 2026, 02:41 PM UTC· resolved Oct 08, 2026, 03:12 PM UTC
- identified Oct 08, 2026, 02:41 PM UTC
The event correlation service is currently experiencing delays. Some communities may receive correlation analyses later than expected. Our teams have identified the issue and are working to resolve it. We cannot provide an estimated resolution time yet, but we will share further updates as soon as more information is available.
- monitoring Oct 08, 2026, 02:47 PM UTC
The issue has been resolved, and the delay is beginning to clear. We are continuing to monitor the event correlation service to confirm that it remains stable.
- resolved Oct 08, 2026, 03:12 PM UTC
The remaining delay continues to clear, and the service is stable. The incident is resolved.
Major October 7, 2026 Some AI analyses may be unavailable 1h 12m Queries, AI
Started Oct 07, 2026, 12:44 PM UTC· resolved Oct 07, 2026, 01:56 PM UTC
- identified Oct 07, 2026, 12:44 PM UTC
We are investigating an issue affecting some AI-powered analyses following a deployment earlier today. Some analyses may be delayed or may not complete successfully. Our teams are working to restore normal operation and will provide an update as soon as more information is available.
- identified Oct 07, 2026, 12:47 PM UTC
We have identified the issue and are currently applying a fix. We expect AI analysis to return to normal within approximately 15 minutes.
- identified Oct 07, 2026, 01:06 PM UTC
An issue affecting our cloud provider is currently preventing us from deploying the fix as planned. Some AI analyses may therefore remain affected and the incident is also affecting SOL queries now. Our teams are investigating the situation and will provide another update as soon as more information is available.
- monitoring Oct 07, 2026, 01:24 PM UTC
The cloud provider incident has been resolved, and the fix for the AI analysis issue has been deployed. We are monitoring the affected services to confirm that they continue to operate normally.
- resolved Oct 07, 2026, 01:56 PM UTC
Incident resolved
Minor September 29, 2026 Assets page and playbook creation degraded 19m Web application, Automation
Started Sep 29, 2026, 08:25 AM UTC· resolved Sep 29, 2026, 08:44 AM UTC
- investigating Sep 29, 2026, 08:25 AM UTC
Our teams are actively investigating an issue affecting the Assets page loading and playbook creation in the FRA1 region. Rest assured that current playbook runs are not impacted. We will share further updates as soon as more information becomes available.
- identified Sep 29, 2026, 08:38 AM UTC
The issue root cause has been identified and mitigation actions have been implemented.
- monitoring Sep 29, 2026, 08:39 AM UTC
The services impacted are showing positive signs of recovery. Our teams are monitoring the situation following the remediation actions.
- resolved Sep 29, 2026, 08:44 AM UTC
The services are operational. Thank you for bearing with us while we worked through the investigation and resolution.
Minor September 28, 2026 Unstable event search 49m Queries
Started Sep 28, 2026, 09:01 AM UTC· resolved Sep 28, 2026, 09:50 AM UTC
- investigating Sep 28, 2026, 09:01 AM UTC
Our Engineering team is investigating intermittent unstability with event search.
- identified Sep 28, 2026, 09:15 AM UTC
We are investigating an issue affecting event searches for multiple communities. A complex query is currently impacting the event search service. Other functionality is not affected at this stage.
- identified Sep 28, 2026, 09:20 AM UTC
Our Engineering team has identified the culprit application causing degraded search experience. A fix is in progress and will be deployed as soon as possible.
- monitoring Sep 28, 2026, 09:38 AM UTC
A fix has been deployed. The service may need some time to process the requests that were queued during the incident. We are monitoring the service to confirm that event search returns to normal and remains stable.
- resolved Sep 28, 2026, 09:50 AM UTC
Event search has returned to normal. The incident is resolved.
Minor September 15, 2026 Delay in loading events and events not attached to alerts 1h 16m Detection, Queries
Started Sep 15, 2026, 01:16 PM UTC· resolved Sep 15, 2026, 02:32 PM UTC
- investigating Sep 15, 2026, 01:16 PM UTC
We are currently investigating an issue that may cause event details to load slowly. In some cases, alerts may also be raised without their related events being attached. Our engineering teams are actively working to identify the root cause and resolve the issue. We will provide further updates as soon as more information becomes available.
- identified Sep 15, 2026, 01:38 PM UTC
Our teams have identified the issue and are working through remediation actions.
- monitoring Sep 15, 2026, 01:56 PM UTC
All remediation actions have been performed and impacted services are showing positive signs of recovery. Our teams are monitoring the situation.
- resolved Sep 15, 2026, 02:32 PM UTC
The situation is stable and the incident is resolved. The remediation actions put in place have restored service stability.
Minor September 14, 2026 Events not attached to alerts 6h 31m Event ingestion, Detection
Started Sep 14, 2026, 10:24 AM UTC· resolved Sep 14, 2026, 04:55 PM UTC
- investigating Sep 14, 2026, 10:24 AM UTC
We are currently investigating an issue affecting our event pipeline : alerts are being raised without the related events being attached to them. Our teams are currently investigating. We'll keep you posted as soon as possible.
- investigating Sep 14, 2026, 10:37 AM UTC
We have resumed normal operations across both the workflow and search systems. We are currently investigating why we had some issues in the first place
- monitoring Sep 14, 2026, 10:42 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 14, 2026, 04:55 PM UTC
The situation remains stable, and the incident is resolved. We identified an issue in the way some services were managing database connections. The mitigations put in place have restored service stability. Our teams will continue working on a permanent fix to prevent the issue from recurring.
Minor September 7, 2026 Event ingestion delays 5h 50m Event ingestion, Detection
Started Sep 07, 2026, 12:56 PM UTC· resolved Sep 07, 2026, 06:46 PM UTC
- investigating Sep 07, 2026, 12:56 PM UTC
Our engineering teams have detected and investigating an issue. Some of our customers might experience delay in events ingestion. An update will be provided as soon as possible to inform about remediation actions. We thank you for your patience during resolution.
- identified Sep 07, 2026, 01:15 PM UTC
The issue affecting our KeyDB infrastructure has recurred and may affect detection services. Our teams are restarting the affected components as a temporary measure to restore service while we continue investigating the root cause. The service should be partially restored soon. We will provide another update as soon as more information is available.
- identified Sep 07, 2026, 01:48 PM UTC
Restarting the affected components has not fully restored service. Detection may be delayed while the issue persists. Our teams are investigating a problem that appears to be related to the underlying cache management component. We are evaluating workarounds and possible solutions.
- monitoring Sep 07, 2026, 02:37 PM UTC
A fix was implemented and allowed detection and ingestion services to restart. We expect lag to resorb gradually. Our engineering teams are monitoring the situation.
- resolved Sep 07, 2026, 06:46 PM UTC
This incident is resolved. Detection process is back in real-time. All events and alert are stored and searchable in real-time. Overall the event ingestion process is in real time. We thank you for your patience during resolution.
Major September 7, 2026 Event processing delays 2h 20m Event ingestion, Event storage, Detection
Started Sep 07, 2026, 08:38 AM UTC· resolved Sep 07, 2026, 10:58 AM UTC
- investigating Sep 07, 2026, 08:38 AM UTC
Our Engineering team has identified an issue impacting event processing. Users may experience some delays for events to appear in the console. An update will be provided as soon as possible to inform about resolution actions. We thank you for your patience during resolution.
- identified Sep 07, 2026, 09:08 AM UTC
Some services may be unavailable or experience degraded performance because they are unable to establish new connections to a required cache component. Our teams are restarting the affected services to restore normal operation. We will provide an update as soon as more information is available.
- identified Sep 07, 2026, 09:15 AM UTC
Further analysis indicates that this incident may affect our detection services. Our teams are continuing restoration efforts and will provide another update as soon as more information is available.
- monitoring Sep 07, 2026, 09:25 AM UTC
Service appears to be returning to normal following the restart of an affected backend component. Our initial findings point to an issue affecting our cloud provider’s infrastructure. We are continuing to monitor the service to confirm full stability.
- identified Sep 07, 2026, 09:37 AM UTC
The situation has improved slightly, but ingestion and detection services continue to experience disruptions. The services remain available, although some functionality may be affected. Our teams are continuing to work on restoring normal service.
- monitoring Sep 07, 2026, 10:05 AM UTC
Following the restart of the affected backend components, some services took longer than expected to reconnect. They have since reconnected automatically, and we are continuing to monitor the service.
- resolved Sep 07, 2026, 10:58 AM UTC
The incident has been resolved. Ingestion and Detection services have been recovered.
Major September 2, 2026 Unexpected Load on Authentication Services 1h 49m Web application
Started Sep 02, 2026, 07:33 PM UTC· resolved Sep 02, 2026, 09:23 PM UTC
- investigating Sep 02, 2026, 07:33 PM UTC
We are investigating an unexpected increase in load on our authentication endpoints. Our teams are actively investigating the situation.
- identified Sep 02, 2026, 08:11 PM UTC
We have identified the source of the unexpected load and are currently evaluating a proper long-term solution. The additional load is being successfully absorbed, and our teams continue to investigate the situation.
- monitoring Sep 02, 2026, 09:09 PM UTC
We scaled the database infrastructure bottleneck identified during the investigation and are now able to fully absorb the increased authentication load. The situation is resolved and services are stable. We will continue monitoring closely.
- resolved Sep 02, 2026, 09:23 PM UTC
The incident is now resolved. Authentication services are operating normally and the platform is stable. We will continue to monitor the service, but no further impact is expected.
Major September 1, 2026 Issue accessing intelligence objects 14m CTI Search
Started Sep 01, 2026, 12:03 PM UTC· resolved Sep 01, 2026, 12:18 PM UTC
- investigating Sep 01, 2026, 12:03 PM UTC
We are currently investigating an issue where intelligence objects are not accessible (returning 404 errors).
- identified Sep 01, 2026, 12:06 PM UTC
We've identified the root cause and are working on deploying a fix to restore intelligence objects access promptly.
- monitoring Sep 01, 2026, 12:07 PM UTC
Objects are displayed as expected and showing positive signs or recovery, we're monitoring the situation.
- resolved Sep 01, 2026, 12:18 PM UTC
The incident is resolved, intelligence objects are now loading as expected.
Minor August 28, 2026 Issue with event ingestion 1h 25m Event ingestion
Started Aug 28, 2026, 03:30 PM UTC· resolved Aug 28, 2026, 04:56 PM UTC
- identified Aug 28, 2026, 03:30 PM UTC
We are currently experiencing an issue with our event ingestion pipeline, causing delays or failures in processing incoming events. Our engineering team is actively investigating the root cause and working to restore full service as quickly as possible. We will share further updates as soon as we have more information.
- monitoring Aug 28, 2026, 03:42 PM UTC
Mitigation actions have been applied to our components, and event ingestion is currently recovering. Our team is actively monitoring the pipeline to ensure full stability as the processing backlog clears. We will provide a final update once the system has completely recovered.
- monitoring Aug 28, 2026, 04:20 PM UTC
Processing lag is still present, but it is gradually resolving. We will provide a final update once full performance is completely restored.
- resolved Aug 28, 2026, 04:56 PM UTC
The processing lag has been fully resolved, and all services are now operating normally. We apologize for the disruption and thank you for your patience.
Critical August 27, 2026 Event ingestion outage 42m Event ingestion
Started Aug 27, 2026, 10:19 AM UTC· resolved Aug 27, 2026, 11:02 AM UTC
- identified Aug 27, 2026, 10:19 AM UTC
Event ingestion is currently unavailable due to an issue affecting our Kafka infrastructure. Our teams are working to restore the service and will provide an update as soon as more information is available.
- identified Aug 27, 2026, 10:32 AM UTC
Event ingestion has resumed for some communities. Our teams are continuing to work on the remaining impact and restore normal processing for all affected communities.
- monitoring Aug 27, 2026, 10:49 AM UTC
The issue has been resolved, and event ingestion has returned to normal. The delay affecting event ingestion is gradually clearing. We continue to monitor the service to confirm that it remains stable.
- resolved Aug 27, 2026, 11:02 AM UTC
Service has resumed successfully. Some residual lag may remain, but it is gradually clearing. The incident is now resolved.
Minor August 25, 2026 Event Ingestion degraded 4h 23m Event ingestion, Event storage, Detection
Started Aug 25, 2026, 08:09 AM UTC· resolved Aug 25, 2026, 12:33 PM UTC
- identified Aug 25, 2026, 08:09 AM UTC
Our Engineering team has identified an issue impacting our Event Ingestion and preventing the platform to manage some incoming queries. The team has resolved the event ingestion and is now monitoring the situation. We thank you for your patience during the resolution and apologize for inconvenience caused.
- monitoring Aug 25, 2026, 08:28 AM UTC
Our Engineering team has stabilized the platform and Ingestion is fully operational. Event storage and detection are being affected by delays as a consequence of the prior Ingestion instability. The situation is currently recovering.
- monitoring Aug 25, 2026, 10:01 AM UTC
Our Engineering team continues to monitor the recovery while the delay in events availability in the platform is decreasing. We thank you for your patience during resolution.
- monitoring Aug 25, 2026, 11:32 AM UTC
Our Engineering team have completed all recovery operations. The platform is now performing under normal conditions. We thank you again for your patience during resolution, and apologize for inconvenience caused.
- resolved Aug 25, 2026, 12:33 PM UTC
The platform is now performing under normal conditions. We thank you again for your patience during resolution, and apologize for inconvenience caused.
Minor August 24, 2026 Intake issue: "Loss of parsing" and "Cannot find a parser for event" 3h 48m Event ingestion
Started Aug 24, 2026, 10:03 AM UTC· resolved Aug 24, 2026, 01:52 PM UTC
- investigating Aug 24, 2026, 10:03 AM UTC
The issue that was preventing the ingestion of all intake formats with the following error "Loss of parsing" and "Cannot find a parser for event" on Monday 17/08 (see: https://status.fra1.sekoia.io/incidents/gchpynrx43rz) has resurfaced around 9:20 PM UTC today.
- identified Aug 24, 2026, 10:06 AM UTC
The root cause has been identified and patched. Events will be replayed.
- monitoring Aug 24, 2026, 10:31 AM UTC
The solution has been patched and a long-term fix has been deployed to prevent this from happening again. We're still replaying events.
- resolved Aug 24, 2026, 01:52 PM UTC
All events has been replayed. The incident is resolved
Minor August 24, 2026 Latency on events 3h 20m Web application, Detection
Started Aug 24, 2026, 09:12 AM UTC· resolved Aug 24, 2026, 12:33 PM UTC
- investigating Aug 24, 2026, 09:12 AM UTC
We are currently investigating latency and timeouts (on events and alerts) on our application.
- investigating Aug 24, 2026, 09:32 AM UTC
We are continuing to investigate this issue.
- investigating Aug 24, 2026, 11:13 AM UTC
We have reduced request latency and timeouts, which has decreased the impact on users. Our investigation is ongoing as we work to identify the root cause and restore normal performance. We will provide another update when the situation changes.
- monitoring Aug 24, 2026, 11:59 AM UTC
Events requests are showing positive signs of recovery. Our engineering team will keep monitoring for the next half hour.
- resolved Aug 24, 2026, 12:33 PM UTC
The issue has been fixed and events are loading normally. The incident is closed.
Minor August 20, 2026 Investigating: Delays in event ingestion for some communities 22m Event ingestion
Started Aug 20, 2026, 04:50 PM UTC· resolved Aug 20, 2026, 05:13 PM UTC
- investigating Aug 20, 2026, 04:50 PM UTC
Some communities may experience slower event ingestion. The issue is not affecting all customers. Our teams are investigating to assess the scope and impact of the incident. We will provide an update as soon as more information is available.
- identified Aug 20, 2026, 05:00 PM UTC
We have identified the cause of the event ingestion delays. An incorrectly formatted community data was preventing some messages from being published correctly. Our teams are working on a fix and will provide another update once the service has returned to normal.
- monitoring Aug 20, 2026, 05:07 PM UTC
We have applied a mitigation to bypass a corrupted message. Event ingestion has resumed normally, and we are monitoring the service to confirm its stability.
- resolved Aug 20, 2026, 05:13 PM UTC
The event ingestion delays have been resolved. Event ingestion is operating normally again, and the incident is now closed.
Minor August 20, 2026 Intake issue: "Cannot find a parser for event" 2h 2m Event ingestion
Started Aug 20, 2026, 01:04 PM UTC· resolved Aug 20, 2026, 03:06 PM UTC
- investigating Aug 20, 2026, 01:04 PM UTC
The issue that was preventing the ingestion of all intake formats with the following error "Cannot find a parser for event" on Monday 17/08 (see: https://status.fra1.sekoia.io/incidents/gchpynrx43rz) has resurfaced around 12:32 PM (GMT+2) due to a deployment issue.
- identified Aug 20, 2026, 01:05 PM UTC
Our engineering team has fixed the root cause and new logs and events are properly being ingested. Our team is currently working on replaying events.
- monitoring Aug 20, 2026, 01:37 PM UTC
New events have now been properly ingested for over 30 minutes. The events impacted are still being replayed, we'll update the incident to resolved as soon as the replay is done.
- resolved Aug 20, 2026, 03:06 PM UTC
Events have now fully been replayed. Incident is resolved.
Major August 19, 2026 Query functionality outage 47m Queries
Started Aug 19, 2026, 02:45 PM UTC· resolved Aug 19, 2026, 03:32 PM UTC
- investigating Aug 19, 2026, 02:45 PM UTC
Ongoing incident impacting our query functionality. Users may experience failures when running queries (including in notebooks and dashboards).
- identified Aug 19, 2026, 03:01 PM UTC
We have identified the likely cause of the issue and are working on a solution. Queries may still be unavailable or experience degraded performance while the fix is being prepared and applied.
- identified Aug 19, 2026, 03:19 PM UTC
The fix has been applied, and the affected services are showing positive signs of recovery.
- monitoring Aug 19, 2026, 03:19 PM UTC
Our teams are monitoring the platform to confirm that the services remain stable and that the issue does not reoccur.
- resolved Aug 19, 2026, 03:32 PM UTC
The issue has been fixed, and the affected services are operating normally. The incident is now closed.
Minor August 15, 2026 Ingestion performance degradation 2h 3m Event ingestion
Started Aug 15, 2026, 06:57 AM UTC· resolved Aug 15, 2026, 09:01 AM UTC
- investigating Aug 15, 2026, 06:57 AM UTC
Our Engineering team is currently investigating an Ingestion performance latency. Users may observe limited delays in Events display.
- monitoring Aug 15, 2026, 07:59 AM UTC
Ingestion performance is back to normal. Our Engineering team is performing some adjustments to ensure the situation is durably stabilized.
- resolved Aug 15, 2026, 09:01 AM UTC
Our Engineering team has completed all remediation actions. Situation is stabilized and event ingestion is in real-time. We thank you for your demonstrated patience during incident resolution, and apologize for any inconvenience caused.
Critical August 10, 2026 Global Latency on FRA1 5h 41m Web application, Event ingestion, Event storage, Detection and 8 more
Started Aug 10, 2026, 08:38 AM UTC· resolved Aug 10, 2026, 02:20 PM UTC
- investigating Aug 10, 2026, 08:38 AM UTC
Investigating - Performance degradation on FRA1 Starting at 08:45 UTC+2 on August 9, we are investigating a performance degradation affecting our FRA1 region. Our team is actively working to identify the exact scope of impacted services. We will provide an update as soon as we have more information.
- investigating Aug 10, 2026, 08:53 AM UTC
Investigating - Service unavailability on FRA1 Update: Our investigation is ongoing. We are currently experiencing a full service outage on FRA1. Our team is actively working to identify the root cause. We will share another update as soon as we have more information.
- investigating Aug 10, 2026, 09:14 AM UTC
Investigating - Service unavailability on FRA1 Update: Our investigation is still ongoing. Our team is actively working to identify the root cause.
- investigating Aug 10, 2026, 09:55 AM UTC
Investigating - Service unavailability on FRA1 Update: Our investigation is ongoing. We have identified a heavy load on one of our databases that is failing to scale, causing the current outage on FRA1. Our team is actively working on a fix. We will share another update shortly.
- investigating Aug 10, 2026, 10:26 AM UTC
Investigating - Service unavailability on FRA1 Update: Our investigation is still ongoing. We have identified a heavy load on one of our databases that is failing to scale, causing the current outage on FRA1. Our team is actively working on a fix. We will share another update shortly.
- investigating Aug 10, 2026, 11:01 AM UTC
Investigating - Service unavailability on FRA1 Update: Our investigation is still ongoing. We have identified a heavy load on one of our databases that is failing to scale, causing the current outage on FRA1. Our team is actively working on a fix. We will share another update shortly.
- monitoring Aug 10, 2026, 11:18 AM UTC
A fix was applied and appears to have restored service on FRA1. We are continuing to monitor the situation closely to confirm full stability. We will share a final update once we have confirmed the incident is resolved.
- resolved Aug 10, 2026, 02:20 PM UTC
The platform is still stable. Incident resolved.
Major August 6, 2026 Indexation is not working properly 1h 56m Event ingestion
Started Aug 06, 2026, 10:10 AM UTC· resolved Aug 06, 2026, 12:06 PM UTC
- investigating Aug 06, 2026, 10:10 AM UTC
We are currently experiencing an issue with our event indexing system, which may prevent new or updated events from appearing. Our engineering team is actively investigating and working on a fix.
- monitoring Aug 06, 2026, 10:21 AM UTC
Event indexing has recovered and is currently processing backlogged events. Our team is actively monitoring performance.
- resolved Aug 06, 2026, 12:06 PM UTC
Event indexing is back to normal and all backlogged events have been processed. Systems are fully stable.