LibraCyber Outage History

Started Oct 15, 2026, 09:37 AM UTC· resolved Oct 15, 2026, 12:17 PM UTC

1. investigating Oct 15, 2026, 09:37 AM UTC

   Since October 14, around 08:00 UTC, some users who report a phishing simulation receive the confirmation email ("Spot on!") several times. A third-party email delivery service sends the same report to our platform multiple times, and each copy triggers a confirmation email. Reports are recorded correctly, and users don't need to do anything. The repeated emails are harmless and can be ignored. We are deploying a fix so that only one confirmation email is sent per report. We are also working with our email delivery provider on the root cause. We will post an update once the fix is live.

2. identified Oct 15, 2026, 09:43 AM UTC

   We have prepared a fix that sends only one confirmation email per reported simulation, even when the same report reaches our platform several times. It is in review and will be deployed shortly. Until the fix is live, some users may still receive repeated confirmation emails after reporting a simulation. Reports are recorded correctly, and the repeated emails can be ignored. We are also working with our email delivery provider on the root cause. We will post an update once the fix is deployed.

3. monitoring Oct 15, 2026, 10:24 AM UTC

   Since October 14 around 08:00 UTC, some users who reported a phishing simulation received the confirmation email ("Spot on!") several times, sometimes every 20 to 25 minutes for several hours. Our email provider delivered the same report to our platform many times, and we sent a confirmation for each delivery. We have deployed a fix: a simulation now triggers one confirmation email only, however many times the report reaches us. Reports already received are recorded correctly, and simulation results and dashboards are not affected. Users who reported a real (non-simulated) email may still receive the acknowledgement more than once while we finish a second fix. We are working with our email provider on the underlying cause and are monitoring the situation.

4. resolved Oct 15, 2026, 12:17 PM UTC

   Resolved – Since October 14 around 08:00 UTC, some users who reported a phishing simulation received the confirmation email ("Spot on!") several times. Our email provider delivered the same report to our platform many times, and we sent a confirmation for each delivery. We deployed a fix on October 15 at 10:17 UTC: each reported simulation now triggers a single confirmation email, however many times the report reaches us. We have monitored the platform since then and observed no further repeated confirmations. Simulation results were not affected. We are following up with our email provider on the underlying cause and will add further safeguards against repeated deliveries. We apologize for the inconvenience.

Read the full incident report →

Started Sep 10, 2026, 06:25 PM UTC· resolved Sep 10, 2026, 08:56 PM UTC

1. investigating Sep 10, 2026, 06:25 PM UTC

   Since approximately 18:15 CEST on 10 September, videos embedded in courses are not playing. When opening a video lesson, users see the message "Sorry, this video doesn't exist". All other platform functions, including login, navigation, quizzes and reporting, are working normally. We are working with the provider to restore playback and will update this notice as soon as the service is back.

2. identified Sep 10, 2026, 07:57 PM UTC

   Course videos are available again: since 21:45 CEST they are being served through a fallback streaming server. Users who had a lesson open before that time need to close and reopen it. While on the fallback, some users may experience slower video loading, and a very small number of videos may be temporarily unavailable. We are continuing to work with the video provider to restore the standard service, and we will update this notice when it is back.

3. resolved Sep 10, 2026, 08:56 PM UTC

   Video playback has been restored on the standard service as of 22:45 CEST. Course videos are playing normally again. Users who had a lesson open before that time need to close and reopen it. No data was lost and no other action is required. We apologise for the inconvenience.

Read the full incident report →

Started Aug 25, 2026, 04:28 PM UTC· resolved Aug 28, 2026, 06:35 PM UTC

1. identified Aug 25, 2026, 04:28 PM UTC

   As a precautionary security measure, the "Forgot password" self-service function on the platform login page has been temporarily disabled. Impact: users who do not remember their password cannot reset it autonomously. Login with existing credentials and all other platform features are working normally. Workaround: company administrators can reset user passwords directly from the administration panel. Alternatively, please contact our support team: https://support.libracyber.com/hc/en-us/requests/new We are working to safely restore the functionality and will post updates here.

2. identified Aug 26, 2026, 03:10 PM UTC

   The permanent fix for this issue has been fully validated and is scheduled for deployment during a maintenance window on Friday, August 28, 18:00–24:00 CEST. Following the upgrade, self-service password recovery ("Forgot password") will be progressively re-enabled across all customers, and we expect the feature to be fully restored shortly after the maintenance window. In the meantime, password resets performed by your platform administrators continue to work normally.

3. resolved Aug 28, 2026, 06:35 PM UTC

   With tonight's upgrade of the authentication platform completed, the "Forgot password" (self-service password recovery) feature has been re-enabled for all tenants as of 20:20 CEST. The feature had been temporarily suspended on 25 August in preparation for this upgrade. Users can again reset their password through the standard self-service flow. We thank you for your patience.

Read the full incident report →

Started Jul 07, 2026, 12:17 PM UTC· resolved Jul 07, 2026, 03:26 PM UTC

1. identified Jul 07, 2026, 12:17 PM UTC

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

2. monitoring Jul 07, 2026, 12:36 PM UTC

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

3. resolved Jul 07, 2026, 03:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 04, 2026, 04:18 PM UTC· resolved Jul 04, 2026, 04:18 PM UTC

1. resolved Jul 04, 2026, 04:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 19, 2026, 12:31 PM UTC· resolved Jun 19, 2026, 02:44 PM UTC

1. investigating Jun 19, 2026, 12:31 PM UTC

   We are currently investigating this issue.

2. identified Jun 19, 2026, 12:54 PM UTC

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

3. monitoring Jun 19, 2026, 01:16 PM UTC

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

4. resolved Jun 19, 2026, 02:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2026, 11:03 AM UTC· resolved Jun 10, 2026, 04:13 PM UTC

1. investigating Jun 10, 2026, 11:03 AM UTC

   We are currently investigating this issue.

2. resolved Jun 10, 2026, 04:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 09:06 AM UTC· resolved Jun 01, 2026, 02:06 PM UTC

1. identified Jun 01, 2026, 09:06 AM UTC

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

2. identified Jun 01, 2026, 12:19 PM UTC

   A fix has been implemented for most mailboxes.

3. resolved Jun 01, 2026, 02:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 23, 2026, 09:44 AM UTC· resolved May 23, 2026, 05:45 PM UTC

1. identified May 23, 2026, 09:44 AM UTC

   50% of M365 mailboxes are not protected by Smart Banners. A fix is being deployed.

2. monitoring May 23, 2026, 02:55 PM UTC

   Some M365 mailboxes are not protected by Smart Banners. A fix has been deploy and we are monitoring the impact.

3. resolved May 23, 2026, 05:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 09, 2026, 11:09 AM UTC· resolved Feb 09, 2026, 11:09 AM UTC

1. resolved Feb 09, 2026, 11:09 AM UTC

   Between February 4th and February 9th, some URLs in received emails were not rewritten for click-time analysis by URLSand. This issue has been identified and resolved on all Libraesva appliances worldwide. No further action is required from users, but we recommend exercising caution when clicking on links in emails received during this period. For any questions or concerns, please contact our support team.

Read the full incident report →

Started Jul 30, 2025, 03:33 PM UTC· resolved Sep 05, 2025, 01:07 PM UTC

1. investigating Jul 30, 2025, 03:33 PM UTC

   The SMS messaging service is currently not working, SMS campaigns will not be delivered to UK recipients until the issue is solved. The disruption does not impact any other feature of the service.

2. monitoring Jul 31, 2025, 01:45 PM UTC

   We have restored SMS service to normal operating status and continue to monitor the situation.

3. identified Jul 31, 2025, 02:47 PM UTC

   Unfortunately the issue is not fixed yet, the SMS messaging service is not working reliably, SMS campaigns will not be delivered to UK recipients until the issue is solved. The disruption does not impact other features of the service.

4. monitoring Aug 08, 2025, 09:11 AM UTC

   We have restored SMS service to normal operating status and continue to monitor the situation.

5. resolved Sep 05, 2025, 01:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 17, 2025, 09:27 AM UTC· resolved Mar 17, 2025, 09:53 AM UTC

1. investigating Mar 17, 2025, 09:27 AM UTC

   We have identified an issue with network connectivity. The affected cloud servers may experience slow connections or become unreachable. We are working to restore connectivity and resolve the situation as soon as possible.

2. monitoring Mar 17, 2025, 09:41 AM UTC

   The network issues have been resolved, we keep monitoring the situation.

3. resolved Mar 17, 2025, 09:53 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Jan 15, 2025, 05:57 PM UTC· resolved Jan 16, 2025, 10:00 AM UTC

1. identified Jan 15, 2025, 05:57 PM UTC

   The affected cloud servers may experience slow connections or become unreachable. We are working to restore the normal performance and resolve the situation as soon as possible.

2. identified Jan 15, 2025, 08:54 PM UTC

   Routing issues within our upstream network are still ongoing. Affected appliances continue to experience intermittent or degraded network connectivity. We're actively monitoring the situation and will provide further updates as more information becomes available.

3. identified Jan 16, 2025, 12:11 AM UTC

   Unfortunately the incident has not yet been resolved. We are actively addressing the issue, however the resolution is currently outside of our direct control. All of the appliances are operational except for the intermittent or degraded network connectivity. We continue to monitor the situation and will provide further updates as more information becomes available. We apologize for any inconvenience caused by this disruption and appreciate your patience and understanding in this regard.

4. identified Jan 16, 2025, 06:15 AM UTC

   Incident Status Update: Estimated Resolution Time is now 1 hour. We apologize for any inconvenience caused by this disruption and appreciate your patience and understanding in this regard.

5. identified Jan 16, 2025, 08:00 AM UTC

   Incident status update: We are still experiencing issues with upstream connectivity, despite having redundant network systems in place. Our team is working with the networking providers to resolve the issue as quickly as possible and apologize for any inconvenience caused by this unprecedented event.

6. monitoring Jan 16, 2025, 09:12 AM UTC

   The upstream network links have been restored. We are monitoring the situation and will provide updates soon.

7. resolved Jan 16, 2025, 10:00 AM UTC

   The incident has been resolved, all appliances are operational.

Read the full incident report →

Started Dec 12, 2024, 09:22 PM UTC· resolved Dec 12, 2024, 10:00 PM UTC

1. investigating Dec 12, 2024, 09:22 PM UTC

   We have identified an issue with network connectivity. The affected cloud servers may experience slow connections or become unreachable. We are working to restore connectivity and resolve the situation as soon as possible.

2. investigating Dec 12, 2024, 09:24 PM UTC

   We are continuing to investigate this issue.

3. investigating Dec 12, 2024, 09:27 PM UTC

   We are continuing to investigate this issue.

4. resolved Dec 12, 2024, 10:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 15, 2024, 11:13 AM UTC· resolved Nov 15, 2024, 04:52 PM UTC

1. identified Nov 15, 2024, 11:13 AM UTC

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

2. identified Nov 15, 2024, 12:03 PM UTC

   The email messaging service is currently not working, email campaigns will not be delivered until the issue is solved. SMS Smishing campaigns are working as usual. The disruption does not impact any other feature of the service.

3. resolved Nov 15, 2024, 04:52 PM UTC

   This incident has beed resolved.

Read the full incident report →

Started Nov 15, 2024, 11:12 AM UTC· resolved Nov 15, 2024, 02:50 PM UTC

1. identified Nov 15, 2024, 11:12 AM UTC

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

2. identified Nov 15, 2024, 12:02 PM UTC

   The email messaging service is currently not working, alert notifications for LetsDMARC will not be delivered until the issue is solved. The disruption does not impact any other feature of the service.

3. resolved Nov 15, 2024, 02:50 PM UTC

   This incident has been resolved. All services are now up & running.

Read the full incident report →