Todyl Outage History

Todyl is up right now

Todyl had 53 outages in the last 2 years totaling 352h 5m of downtime — averaging 2.2 incidents per month.

There were 53 Todyl outages since October 20, 2025 totaling 352h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.todyl.com

Minor October 5, 2026

SASE Connectivity impacting subset of Windows Server 2016/2019

Detected by Pingoru
Oct 05, 2026, 02:54 PM UTC
Resolved
Oct 06, 2026, 03:12 PM UTC
Duration
1d
Affected: Secure Global Network
Timeline · 4 updates
  1. investigating Oct 05, 2026, 02:54 PM UTC

    A small subset of agents running on Windows Server 2016/2019 are reporting connectivity issues. We are investigating this right now and will update when we have more information.

  2. identified Oct 05, 2026, 06:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 05, 2026, 09:51 PM UTC

    A fix has been implemented and we are monitoring the results. Please reach out to our Technical Support Team if you are seeing any further issues at all.

  4. resolved Oct 06, 2026, 03:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 16, 2026

SIEM and Cases Loading Issues

Detected by Pingoru
Sep 16, 2026, 01:47 PM UTC
Resolved
Sep 21, 2026, 11:16 PM UTC
Duration
5d 9h
Affected: Todyl.com & Management PortalSIEM Dashboard & Portal
Timeline · 4 updates
  1. investigating Sep 16, 2026, 01:47 PM UTC

    We are currently conducting an active investigation into an issue affecting our SIEM platform. Users may be experiencing delays or failures when loading SIEM results. As a result of this delay, cases may also appear delayed or time out in the portal. Our team is aware of the impact and is actively investigating the affected components. Further updates will be provided as more information becomes available.

  2. identified Sep 16, 2026, 09:28 PM UTC

    Todyl engineering team has identified a fix for the issue and implemented it, initial results are positive and we should see responsiveness increase due to these changes. It will take some time for the system to catch up completely. No data was lost as a result of this issue and should be available shortly.

  3. monitoring Sep 17, 2026, 12:58 PM UTC

    The fix for the issue impacting search, dashboards and integrations has addressed the issue, and the system should be operating normally. We will continue to monitor to see if there are any further challenges, and close once fully confirmed.

  4. resolved Sep 21, 2026, 11:16 PM UTC

    This incident has been resolved. We have been monitoring over the weekend and throughout today and confirm normal operational state for display of data across dashboards, widgets, and integrations pages.

Read the full incident report →

Notice September 2, 2026

LA PoP Packetloss and Routing Errors

Detected by Pingoru
Sep 02, 2026, 03:15 PM UTC
Resolved
Sep 03, 2026, 02:10 PM UTC
Duration
22h 54m
Affected: Hong KongSingapore, SINTokyo, JPNAuckland, NZ
Timeline · 3 updates
  1. identified Sep 02, 2026, 03:15 PM UTC

    Due to an upstream outage at the LA PoP, we are seeing intermittent connectivity challenges across several routes to other PoPs. We have identified the impacted routes and are working on options to improve performance. Will update as soon as we have more information.

  2. monitoring Sep 02, 2026, 05:50 PM UTC

    This incident appears to be directly related to the Cogent fiber cuts (https://ecogent.cogentco.com/network-status) that are impacting traffic in the region. We have seen improvements as traffic gets rerouted in the region, but it appears that the Aukland PoP is still impacted. We will continue to monitor and update as we have more information.

  3. resolved Sep 03, 2026, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 31, 2026

Degraded SIEM Loading Issues

Detected by Pingoru
Aug 31, 2026, 01:00 PM UTC
Resolved
Sep 02, 2026, 08:42 PM UTC
Duration
2d 7h
Affected: SIEM Dashboard & Portal
Timeline · 4 updates
  1. investigating Aug 31, 2026, 01:00 PM UTC

    We are currently investigating an issue where SIEM data loading is degrade in the Todyl portal. Data is still being ingested into SIEM, however either not displaying or has a delayed display in the UI. We will update once we have identified the root cause of the issue.

  2. identified Aug 31, 2026, 08:40 PM UTC

    We continue to experience above-average query volume which is resulting in intermittent delays with data loading into the SIEM. The problem has been identified and we are in the process of implementing changes to alleviate the resource demand. We will provide an update once the changes are implemented.

  3. monitoring Sep 01, 2026, 03:26 AM UTC

    A fix for the issue impacting the display of data has been implemented. We will continue to monitor to see if there are any further challenges. We will resolve once fully confirmed.

  4. resolved Sep 02, 2026, 08:42 PM UTC

    This incident has been resolved. We have been monitoring overnight and throughout today and confirm normal operational state for display of data across dashboards, widgets, and integrations pages within SIEM.

Read the full incident report →

Notice August 27, 2026

Intermittent SIEM loading issues

Detected by Pingoru
Aug 27, 2026, 08:22 PM UTC
Resolved
Aug 29, 2026, 03:39 AM UTC
Duration
1d 7h
Affected: SIEM Dashboard & Portal
Timeline · 5 updates
  1. investigating Aug 27, 2026, 08:22 PM UTC

    We are currently investigating an issue where SIEM data is not loading in the Todyl portal. Data is still being ingested into SIEM, just not displayed in the UI. We will update once we have identified the root cause of the issue.

  2. identified Aug 28, 2026, 02:26 PM UTC

    We are currently experiencing above-average query volume which is resulting in intermittent delays with data loading into the SIEM. Additional resources have been allocated to the system and conditions have improved; however, the service remains in a degraded state. We are continuing to investigate the root cause and will provide a follow-up update within 2-3 hours

  3. identified Aug 28, 2026, 08:32 PM UTC

    Todyl Engineering team has identified timing and resource adjustments for this issue and we are rolling out the necessary changes in the coming hour. We will post another update here after the remediation steps are validated.

  4. monitoring Aug 28, 2026, 11:02 PM UTC

    Implemented changes has significantly improved the degradation, and the system is on its way to normal operational state. Changing status to monitoring.

  5. resolved Aug 29, 2026, 03:39 AM UTC

    Todyl has been monitoring since implementing the changes a few hours ago. Everything is looking to be back to normal operational state, marking this issue as resolved.

Read the full incident report →

Notice August 26, 2026

Intermittent Portal Configuration Errors

Detected by Pingoru
Aug 26, 2026, 04:58 PM UTC
Resolved
Aug 27, 2026, 05:25 AM UTC
Duration
12h 27m
Affected: Todyl.com & Management Portal
Timeline · 4 updates
  1. investigating Aug 26, 2026, 04:58 PM UTC

    We are currently investigating some replication delays on internal servers. These delays can possibly cause errors when creating or updating configurations in the Todyl portal. Will update here when we have identified a resolution.

  2. identified Aug 26, 2026, 06:43 PM UTC

    We identified an issue creating some replication delays on internal servers. These delays can possibly cause errors when creating or updating configurations in the Todyl portal. Will update here when we have implemented a resolution.

  3. monitoring Aug 27, 2026, 05:13 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 27, 2026, 05:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 20, 2026

Intermittent SASE Tunnel Errors

Detected by Pingoru
Aug 20, 2026, 03:50 PM UTC
Resolved
Aug 20, 2026, 10:32 PM UTC
Duration
6h 42m
Affected: Secure Global Network
Timeline · 4 updates
  1. investigating Aug 20, 2026, 03:50 PM UTC

    Investigating intermittent reported SASE tunnel errors. Please let technical support know if you are experiencing any tunnel issues. We will update here with more information shortly.

  2. identified Aug 20, 2026, 04:39 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 20, 2026, 05:16 PM UTC

    A fix has been implemented and we are monitoring tunnels for any other issues. Please let us know if you are experiencing any further challenges.

  4. resolved Aug 20, 2026, 10:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 6, 2026

SASE connection failures for Windows Server 2012

Detected by Pingoru
Aug 06, 2026, 02:14 PM UTC
Resolved
Aug 06, 2026, 04:01 PM UTC
Duration
1h 46m
Affected: Secure Global Network
Timeline · 4 updates
  1. investigating Aug 06, 2026, 02:14 PM UTC

    We are currently investigating reports of SASE connection errors on Windows Server 2012 devices. We will update as we have more information.

  2. identified Aug 06, 2026, 02:43 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 06, 2026, 03:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 06, 2026, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 4, 2026

SIEM Results Loading Delay Impacting Case Portal Visibility

Detected by Pingoru
Aug 04, 2026, 03:33 PM UTC
Resolved
Aug 04, 2026, 06:16 PM UTC
Duration
2h 43m
Affected: SIEM Processing & Alerting
Timeline · 4 updates
  1. investigating Aug 04, 2026, 03:33 PM UTC

    We are currently conducting an active investigation into an issue affecting our SIEM platform. Users may be experiencing delays when loading SIEM results. As a result of this delay, cases may also appear delayed in the portal. Our team is aware of the impact and is actively investigating the affected components. Further updates will be provided as more information becomes available.

  2. identified Aug 04, 2026, 04:25 PM UTC

    We have identified the root cause of the delays affecting SIEM results loading. The issue has been traced to a third-party upstream provider, and we are actively working with them to implement a fix. Users may continue to experience delays in SIEM results loading and cases appearing in the portal in the interim. Data integrity is not affected. Further updates will be provided as progress is made.

  3. monitoring Aug 04, 2026, 04:46 PM UTC

    The platform has returned to normal operation. We are continuing to monitor the situation to ensure full stability. Further updates will be provided if necessary.

  4. resolved Aug 04, 2026, 06:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 30, 2026

SASE Reconnections - follow on

Detected by Pingoru
Jul 30, 2026, 06:04 PM UTC
Resolved
Jul 30, 2026, 10:54 PM UTC
Duration
4h 49m
Affected: Secure Global Network
Timeline · 3 updates
  1. identified Jul 30, 2026, 06:04 PM UTC

    We have identified a subsequent issue related to the previous SASE incident. We are implementing a fix, but some users could still have intermittent SASE connection issues. We will update as soon as we know more on the fix.

  2. monitoring Jul 30, 2026, 09:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 30, 2026, 10:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 30, 2026

SASE reconnections

Detected by Pingoru
Jul 30, 2026, 09:21 AM UTC
Resolved
Jul 30, 2026, 03:11 PM UTC
Duration
5h 49m
Affected: Secure Global Network
Timeline · 6 updates
  1. investigating Jul 30, 2026, 09:21 AM UTC

    We are currently investigating performance degradation affecting the Secure Global Network (SASE). A subset of users connecting may be experiencing disconnect and connect loop. Our engineering team is actively investigating the root cause.

  2. identified Jul 30, 2026, 09:46 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jul 30, 2026, 11:37 AM UTC

    We have deployed a fix to stabilize the SASE environment and are continuing to investigate the underlying root cause. SASE connections are currently stable once established. As a precaution, tenant and policy updates remain temporarily paused while we complete validation and work toward full resolution. We will provide additional updates as new information becomes available.

  4. identified Jul 30, 2026, 12:04 PM UTC

    The team is now re-enabling tenant and policy changes across all PoPs. We will provide another update once the rollout is complete and stability has been validated.

  5. monitoring Jul 30, 2026, 01:31 PM UTC

    The team has re-enabled tenant and policy changes across all PoPs and are monitoring the results.

  6. resolved Jul 30, 2026, 03:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 27, 2026

Bash Shell Profile Modification alerts

Detected by Pingoru
Jul 27, 2026, 03:33 PM UTC
Resolved
Jul 27, 2026, 09:33 PM UTC
Duration
6h
Affected: Todyl.com & Management PortalSIEM Processing & Alerting
Timeline · 5 updates
  1. investigating Jul 27, 2026, 03:33 PM UTC

    We are currently investigating an influx of Bash Shell Profile Modification alerts. These are all benign. Will update here as we know more.

  2. identified Jul 27, 2026, 03:34 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jul 27, 2026, 03:54 PM UTC

    The alert influx is impacting performance within the Todyl Management portal. Affected components include the portal experience and reporting widgets, which are experiencing slower than expected loading times. We are working to resolve this issue and will provide updates as the situation develops.

  4. monitoring Jul 27, 2026, 06:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 27, 2026, 09:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 24, 2026

Investigating intermittent URL resolution issue

Detected by Pingoru
Jul 24, 2026, 03:35 AM UTC
Resolved
Jul 24, 2026, 08:46 PM UTC
Duration
17h 11m
Affected: Secure Global Network
Timeline · 3 updates
  1. investigating Jul 24, 2026, 03:35 AM UTC

    We are currently investigating reports of certain URLs intermittently failing to resolve correctly. Some domains, including those in the Google domain family, may be impacted. Our team is actively investigating and we will provide updates as more information becomes available.

  2. monitoring Jul 24, 2026, 02:01 PM UTC

    A third party provider has implemented a fix that appears to have resolved the intermittent URL failure. We will continue to monitor for any other issues and update here as needed.

  3. resolved Jul 24, 2026, 08:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 23, 2026

Microsoft API Ingestion Delays

Detected by Pingoru
Jul 23, 2026, 06:38 PM UTC
Resolved
Jul 23, 2026, 08:19 PM UTC
Duration
1h 41m
Affected: SIEM Processing & Alerting
Timeline · 2 updates
  1. monitoring Jul 23, 2026, 06:38 PM UTC

    Microsoft is currently experiencing an incident affecting their M365 API. As a result, O365 data ingestion is delayed, temporarily impacting O365-sourced events. We are monitoring the upstream Microsoft incident and will update as it progresses.

  2. resolved Jul 23, 2026, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026

Investigating Bogota Point of Presence (PoP) Connectivity Issue

Detected by Pingoru
Jul 07, 2026, 07:28 PM UTC
Resolved
Jul 07, 2026, 10:34 PM UTC
Duration
3h 6m
Affected: Bogota, COL
Timeline · 4 updates
  1. investigating Jul 07, 2026, 07:28 PM UTC

    We are currently investigating connectivity issues with the Bogota Point of Presence (PoP). Devices will automatically route to the next nearest and fastest PoP and Static IP traffic will egress from the configured secondary location. Will update here as we the investigation continues.

  2. identified Jul 07, 2026, 07:51 PM UTC

    The connectivity issue was caused by a power outage from a third party provider. The provider is aware and currently working to restore power as soon as possible.

  3. monitoring Jul 07, 2026, 08:31 PM UTC

    The connectivity issue with the Bogota Point of Presence (PoP) has been restored. We will continue to monitor to ensure no other issues.

  4. resolved Jul 07, 2026, 10:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 2, 2026

Investigating partial connectivity issues impacting Oceania region

Detected by Pingoru
Jul 02, 2026, 01:15 AM UTC
Resolved
Jul 02, 2026, 03:43 AM UTC
Duration
2h 28m
Affected: Hong KongSydney, AUS
Timeline · 3 updates
  1. investigating Jul 02, 2026, 01:15 AM UTC

    This issue is currently under investigation, but possibly related to a known Microsoft outage in the region - https://downdetector.com.au/status/microsoft-365/ We will post more information here as soon as we have better insight.

  2. monitoring Jul 02, 2026, 02:37 AM UTC

    It appears the 3rd party issues have been restored. Will continue monitoring until we are clear that it is fully resolved.

  3. resolved Jul 02, 2026, 03:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 23, 2026

Investigating Miami Point of Presence (PoP) Connectivity Issue

Detected by Pingoru
Jun 23, 2026, 10:43 PM UTC
Resolved
Jun 24, 2026, 12:43 AM UTC
Duration
2h
Affected: Secure Global NetworkMiami, FL USA
Timeline · 4 updates
  1. investigating Jun 23, 2026, 10:43 PM UTC

    We are currently investigating connectivity issues with the Miami Point of Presence (PoP). Devices will automatically route to the next nearest and fastest PoP and Static IP traffic will egress from the configured secondary location. Will update here as we the investigation continues.

  2. identified Jun 23, 2026, 11:00 PM UTC

    The connectivity issue was caused by a power outage from a third party provider. The provider is aware and currently working to restore power as soon as possible.

  3. monitoring Jun 23, 2026, 11:21 PM UTC

    The connectivity issue with the Miami Point of Presence (PoP) has been restored. We will continue to monitor to ensure no other issues, but SASE, tunnels, and Static IP traffic should be connecting now.

  4. resolved Jun 24, 2026, 12:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 22, 2026

Cloudflare error causing intermittent portal delays

Detected by Pingoru
Jun 22, 2026, 02:52 PM UTC
Resolved
Jun 22, 2026, 09:01 PM UTC
Duration
6h 9m
Affected: Todyl.com & Management Portal
Timeline · 7 updates
  1. investigating Jun 22, 2026, 02:52 PM UTC

    Some partners may be experiencing intermittent latency when using the Todyl portal. Currently there is a partial Cloudflare system error being reported, leading to the intermittent errors on the Todyl portal. We are monitoring the situation closely and getting updates from Cloudflare. We will be be providing regular updates. For more information, please also refer to the Cloudflare status page - https://www.cloudflarestatus.com/.

  2. identified Jun 22, 2026, 02:56 PM UTC

    The issue has been identified and awaiting on a Cloudflare resolution. For more information, please also refer to the Cloudflare status page - https://www.cloudflarestatus.com/.

  3. monitoring Jun 22, 2026, 04:45 PM UTC

    Cloudflare has successfully mitigated the majority of congestion and packet drops. We are continuing to monitor any possible impacts to the Todyl portal. For more information, please also refer to the Cloudflare status page - https://www.cloudflarestatus.com/.

  4. identified Jun 22, 2026, 04:48 PM UTC

    Cloudflare has successfully mitigated the majority of congestion and packet drops. We are continuing to monitor any possible impacts to the Todyl portal. For more information, please also refer to the Cloudflare status page - https://www.cloudflarestatus.com/.

  5. monitoring Jun 22, 2026, 04:48 PM UTC

    majority of congestion and packet drops has been mitigated. Services are stable, with only minor residual impact remaining. A small number of intermittent errors may still be observed for services with origins in North America. We are putting this into a monitoring state.

  6. monitoring Jun 22, 2026, 05:03 PM UTC

    Cloudflare has successfully mitigated the majority of congestion and packet drops. We are continuing to monitor any possible impacts to the Todyl portal. For more information, please also refer to the Cloudflare status page - https://www.cloudflarestatus.com/.

  7. resolved Jun 22, 2026, 09:01 PM UTC

    This incident is considered resolved as we see no impact on Todyl portal anymore, despite Cloudflare still continuing to monitor the issue.

Read the full incident report →

Notice June 15, 2026

Secure Global Network (SASE) - Houston, HOU

Detected by Pingoru
Jun 15, 2026, 08:18 PM UTC
Resolved
Jun 16, 2026, 04:29 AM UTC
Duration
8h 10m
Affected: Houston, TX
Timeline · 3 updates
  1. investigating Jun 15, 2026, 08:18 PM UTC

    We are currently investigating performance degradation affecting the Secure Global Network (SASE) - Houston, HOU region. A subset of users connecting through this region may be experiencing elevated latency or reduced throughput. Our engineering team is actively investigating the root cause.

  2. monitoring Jun 15, 2026, 08:53 PM UTC

    Performance has returned to normal operation for the Secure Global Network (SASE) - Houston, HOU region. The system has self-recovered and affected users should no longer be experiencing elevated latency or reduced throughput. We are continuing to monitor the environment to ensure sustained stability.

  3. resolved Jun 16, 2026, 04:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 4, 2026

Management Portal Sign In Issues

Detected by Pingoru
Jun 04, 2026, 12:08 PM UTC
Resolved
Jun 04, 2026, 12:43 PM UTC
Duration
34m
Affected: Todyl.com & Management Portal
Timeline · 3 updates
  1. investigating Jun 04, 2026, 12:08 PM UTC

    We are currently investigating an issue affecting Management Portal sign ins. A subset of users may experience intermittent failures when attempting to load the portal. All other Todyl services are operating normally. Our engineering team is actively investigating the root cause.

  2. monitoring Jun 04, 2026, 12:38 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 04, 2026, 12:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 22, 2026

Delayed EDR Policy Updates on Some Endpoints

Detected by Pingoru
May 22, 2026, 02:47 AM UTC
Resolved
May 22, 2026, 05:34 AM UTC
Duration
2h 47m
Affected: NGAV/EDR
Timeline · 4 updates
  1. investigating May 22, 2026, 02:47 AM UTC

    We're investigating a delay in EDR policy updates affecting a small subset of endpoints. Impacted agents remain fully connected and continue enforcing current policies. Detection, prevention, and response functionality are unaffected.

  2. identified May 22, 2026, 05:14 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 22, 2026, 05:18 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 22, 2026, 05:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 7, 2026

Intermittent data load errors in portal

Detected by Pingoru
May 07, 2026, 09:00 PM UTC
Resolved
May 07, 2026, 09:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 07, 2026, 10:31 PM UTC

    Intermittent loading errors were seen on portal between 3PM MT and 4PM MT. The errors affected SIEM search, SIEM dashboards, Cases alert data and SOAR playbook execution. The errors have been addressed since.

Read the full incident report →

Notice May 1, 2026

SIEM Processing & Alerting — Alert Volume Anomaly

Detected by Pingoru
May 01, 2026, 08:41 PM UTC
Resolved
May 01, 2026, 10:14 PM UTC
Duration
1h 32m
Affected: SIEM Processing & Alerting
Timeline · 3 updates
  1. investigating May 01, 2026, 08:41 PM UTC

    We are currently investigating an anomalous spike in alert volume affecting SIEM Processing & Alerting. Beginning at roughly 19:30 UTC a large number of cases were generated across a portion of partner tenants, associated with endpoint detection activity. The volume of alerts generated is inconsistent with expected baseline behavior. Our engineering team is actively investigating the issue.

  2. monitoring May 01, 2026, 09:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 01, 2026, 10:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 28, 2026

Case creation

Detected by Pingoru
Apr 28, 2026, 01:29 PM UTC
Resolved
Apr 28, 2026, 03:16 PM UTC
Duration
1h 46m
Affected: SIEM Processing & Alerting
Timeline · 4 updates
  1. investigating Apr 28, 2026, 01:29 PM UTC

    We identified and resolved an issue that caused delays in case creation. No alerts were lost, and MXDR is actively reviewing and addressing all open cases. We are maintaining heightened monitoring until all delayed cases have been fully processed, reviewed, and addressed.

  2. investigating Apr 28, 2026, 01:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 28, 2026, 01:46 PM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 28, 2026, 03:16 PM UTC

    Delays in case Creation and reporting issue is resolved. System and MXDR team is fully up to speed in reviewing the delayed cases. We are continuing to monitor but we consider the issue resolved.

Read the full incident report →

Minor April 1, 2026

Case Generation Delay

Detected by Pingoru
Apr 01, 2026, 04:47 PM UTC
Resolved
Apr 01, 2026, 05:22 PM UTC
Duration
35m
Affected: SIEM Processing & Alerting
Timeline · 4 updates
  1. investigating Apr 01, 2026, 04:47 PM UTC

    We are currently investigating delays in case creations. Please be assured that all delayed cases will be fully processed and reviewed.

  2. identified Apr 01, 2026, 04:59 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 01, 2026, 05:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 01, 2026, 05:22 PM UTC

    This incident has been resolved.

Read the full incident report →