Breach Secure Now! Outage History

Started Jun 16, 2026, 07:47 PM UTC· resolved Jun 17, 2026, 02:35 AM UTC

1. investigating Jun 16, 2026, 07:47 PM UTC

   We're currently experiencing an issue affecting access to the BSN portal. Our engineering team is actively investigating and working to resolve the issue as quickly as possible. We’ll provide updates as soon as more information is available. Thank you for your patience.

2. monitoring Jun 16, 2026, 09:02 PM UTC

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

3. resolved Jun 17, 2026, 02:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 04:22 PM UTC· resolved Apr 09, 2026, 01:24 AM UTC

1. investigating Apr 08, 2026, 04:22 PM UTC

   We are currently investigating an issue affecting user management within the platform. What’s happening: At this time, users may experience issues when attempting to: Save changes to existing user profiles Create new users manually In some cases, selecting “Save” may not complete the action as expected. Scope: This issue may impact all user types across the platform. Our team is actively working to identify the root cause and implement a resolution as quickly as possible. We will continue to provide updates as more information becomes available. Thank you for your patience and understanding.

2. identified Apr 08, 2026, 07:20 PM UTC

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

3. resolved Apr 09, 2026, 01:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 17, 2026, 05:17 PM UTC· resolved Mar 24, 2026, 10:38 PM UTC

1. investigating Mar 17, 2026, 05:17 PM UTC

   We are currently experiencing an issue on the Manage Client page where users may be unable to access their clients. Affected users may see the following message: “No clients match your search or filter criteria. Try adjusting your search or filter settings.” Our team is actively investigating and working on a fix. Workaround to access clients: Deployment Stats view: disable the Positive Opt-in filter Micro Trainings and Newsletter Engagement view: disable both the Received MT/NL and Positive Opt-in filters Important note: This workaround is only for regaining access to clients. At this time, you will not be able to view these fields globally through those filtered views. You can still review them on an individual client basis. We will share another update as soon as a fix is available.

2. resolved Mar 24, 2026, 10:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 30, 2026, 02:23 AM UTC· resolved Feb 06, 2026, 05:54 PM UTC

1. identified Jan 30, 2026, 02:23 AM UTC

   We are aware of an issue causing some phishing PDF reports to time out during download for very large files. Our team has identified the issue and is actively working on a resolution. CSV reports remain fully operational.

2. monitoring Feb 06, 2026, 02:05 AM UTC

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

3. resolved Feb 06, 2026, 05:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 22, 2026, 02:55 PM UTC· resolved Apr 08, 2026, 04:20 PM UTC

1. investigating Jan 22, 2026, 02:55 PM UTC

   We are currently aware of an issue where users with specific roles that have billing access enabled are still unable to view billing reports as expected. Our team is actively working to identify and resolve the root cause of this issue. Workaround: Partner Admins and Manager Admins are still able to access billing reports normally. Our Operations team can also assist in providing billing reports upon request. We apologize for any inconvenience this may cause and appreciate your patience while we work toward a resolution. Further updates will be shared as progress is made.

2. identified Mar 17, 2026, 03:41 PM UTC

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

3. resolved Apr 08, 2026, 04:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 05:38 PM UTC· resolved Nov 06, 2025, 09:01 PM UTC

1. identified Nov 04, 2025, 05:38 PM UTC

   We have identified an issue preventing some users from accessing Catch Phish and the BSN Microsoft Teams app on desktop. Affected users may see an error message stating that their email address is not recognized. These issues appear to be isolated to desktop applications. Our team has identified the issue and is working on a fix. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding as we work toward resolving this issue.

2. identified Nov 05, 2025, 08:39 PM UTC

   Update: A fix has been developed and is currently being tested. We will provide an update once the fix has passed QA and deployed to production. Thank you again for your patience and understanding as we resolve this issue.

3. resolved Nov 06, 2025, 09:01 PM UTC

   Update: A fix has been developed and deployed to both the Microsoft Teams Application and Catch Phish. Notes: An error occurred when decoding certain security tokens from Microsoft. Thank you for your patience and understanding as we resolved the issue.

Read the full incident report →

Started Oct 29, 2025, 09:13 PM UTC· resolved Oct 31, 2025, 03:00 PM UTC

1. monitoring Oct 29, 2025, 09:13 PM UTC

   Microsoft is currently experiencing an outage affecting several of its services. Since the BSN platform integrates with Microsoft, certain features such as Single Sign-On (SSO), Active Directory (AD) Sync, Direct Mail Delivery, Catch Phish, and Microsoft Teams may be impacted. Our team is actively monitoring the BSN platform and will provide updates if conditions change or issues are identified. Microsoft is currently in the process of implementing a fix. If you are experiencing issues with the BSN platform after Microsoft services have been restored, please open a support ticket. Thank you for your patience and understanding.

2. resolved Oct 31, 2025, 03:00 PM UTC

   The outage affecting several Microsoft services has been resolved. There should be no further impact to the Breach Secure Now portal. Thank you for your patience while we monitored this issue.

Read the full incident report →

Started Oct 20, 2025, 02:58 PM UTC· resolved Oct 27, 2025, 01:54 PM UTC

1. monitoring Oct 20, 2025, 02:58 PM UTC

   The BSN portal is hosted on AWS, which experienced an outage between approximately 4:00 AM and 6:00 AM EST. As a result, the BSN portal and related services, including welcome and notification emails, were temporarily affected. AWS has implemented mitigation measures and is progressing toward full recovery. We are observing continued improvement across the BSN portal and affected systems. Our team will continue to monitor the situation closely to ensure full restoration and stability.

2. resolved Oct 27, 2025, 01:54 PM UTC

   The AWS outage that affected the BSN portal and related services has been resolved. Thank you for your patience during this incident.

Read the full incident report →

Started Oct 15, 2025, 06:26 PM UTC· resolved Oct 27, 2025, 05:31 PM UTC

1. investigating Oct 15, 2025, 06:26 PM UTC

   We’ve received reports of delays and disruptions affecting Active Directory Sync. Our team is currently investigating the issue. We will share additional updates as soon as more information becomes available. Thank you for your patience.

2. monitoring Oct 16, 2025, 02:12 PM UTC

   Our team has identified the root cause of the issue and developed a fix that has been deployed to production. After thorough testing, we have confirmed that the Active Directory sync functionality has been fully restored. We will continue to monitor system performance closely to ensure ongoing stability. Thank you for your patience and understanding while we addressed this issue.

3. resolved Oct 27, 2025, 05:31 PM UTC

   The issue affecting Active Directory sync has been resolved. Thank you for your patience while we addressed this issue.

Read the full incident report →

Started Sep 29, 2025, 09:02 PM UTC· resolved Oct 15, 2025, 06:41 PM UTC

1. investigating Sep 29, 2025, 09:02 PM UTC

   An issue is preventing the deletion or archiving of inactive clients in the portal. When attempting this action as either a Partner Admin or Support Admin, a “Status 400” error is displayed. Our team is actively investigating the issue and will provide updates as more information becomes available. Thank you for your patience.

2. monitoring Oct 08, 2025, 03:02 PM UTC

   We have implemented a permanent fix for the issue that prevented the deletion or archiving of inactive clients in the portal. The fix has been successfully deployed. Our team is following up with partners who have open support tickets related to this issue. We will continue to monitor the platform to ensure client management remains fully operational. Thank you for your patience while we worked to resolve this issue.

3. resolved Oct 15, 2025, 06:41 PM UTC

   The issue preventing the deletion or archiving of inactive clients has been resolved. Thank you for your patience as we addressed this matter.

Read the full incident report →

Started Sep 25, 2025, 02:09 PM UTC· resolved Nov 20, 2025, 02:25 PM UTC

1. monitoring Sep 25, 2025, 02:09 PM UTC

   Microsoft will shut off their legacy Exchange Online Token in October. This change affects older Catch Phish deployments. Partners currently using the workaround (re-enabling Exchange Online Tokens) must upgrade to the latest version of Catch Phish from the Microsoft Add-on Store. Partners who have not yet acted and are just learning about this deadline also need to upgrade. Upgrades can be completed by following the instructions in the Help Center. Alternatively, partners can open a support ticket, and our team will assist with the deployment.

2. resolved Nov 20, 2025, 02:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 22, 2025, 09:33 PM UTC· resolved Oct 27, 2025, 01:57 PM UTC

1. investigating Sep 22, 2025, 09:33 PM UTC

   An issue with SSO setup has been identified. When trying to save the SSO configuration, an error is displayed saying, “Failed to save Federated Login: Failed to save Metadata URL.” This issue only impacts new SSO setups. Existing SSO setups are still working correctly. Our team is investigating the issue and will provide updates as we learn more. Thank you for your patience and understanding.

2. monitoring Sep 25, 2025, 02:04 PM UTC

   Our team has identified and resolved the issue that prevented partners from saving the Metadata URL during SSO configuration in the portal. The error message, “Failed to save Federated Login: Failed to save Metadata URL,” has been addressed, and the fix has been successfully deployed. We will continue monitoring the situation to ensure the feature remains fully operational. Thank you for your patience while we worked to resolve this.

3. resolved Oct 27, 2025, 01:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 19, 2025, 03:40 PM UTC· resolved Oct 03, 2025, 05:51 PM UTC

1. identified Sep 19, 2025, 03:40 PM UTC

   We are currently experiencing issues with simulated phishing emails not being delivered to Google Workspace and Gmail accounts. This may be due to an increased volume of simulated phishing emails being sent to Google-hosted accounts. Google is currently blocking delivery. Our team is actively working with Google to resolve this matter. We will provide updates as soon as more information becomes available. Thank you for your patience.

2. resolved Oct 03, 2025, 05:51 PM UTC

   We have implemented a permanent fix that addresses the phishing campaign scheduling issue. Our Support team is following up with partners who have open tickets related to this matter and will continue monitoring phishing campaign performance to ensure stability.

Read the full incident report →

Started Sep 15, 2025, 03:51 PM UTC· resolved Oct 27, 2025, 08:53 PM UTC

1. identified Sep 15, 2025, 03:51 PM UTC

   We have identified an issue with our simulated phishing system that is causing delays in processing emails in the queue. As a result, simulated phishing emails are taking longer than expected to be sent out. Our team is actively working on a fix and will provide updates as soon as more information is available. We appreciate your patience and understanding as we resolve this matter.

2. identified Sep 19, 2025, 04:47 PM UTC

   We have implemented a workaround for phishing campaigns stuck in the queue and are working towards a permanent solution. For any partners who have not already opened a support ticket reporting their stuck phishing campaigns, please open a ticket and we will apply the workaround. Thank you for your patience as we address this matter.

3. resolved Oct 27, 2025, 08:53 PM UTC

   The issue causing simulated phishing emails to remain in queue status has been resolved. Following the deployment of a fix earlier this month, our team has confirmed that phishing emails are now being sent out as expected. Some residual configuration-related issues may still occur. If you continue to experience any problems, please open a support ticket, and our team will assist on a case-by-case basis. Thank you for your patience and understanding as we resolved this matter.

Read the full incident report →

Started Sep 02, 2025, 02:02 PM UTC· resolved Sep 05, 2025, 05:55 PM UTC

1. identified Sep 02, 2025, 02:02 PM UTC

   We have identified an issue affecting the downloading of reports and certificates from our platform. Our engineers have confirmed the problem and are actively investigating the root cause. We will provide an update as soon as more information becomes available. We apologize for any inconvenience this may cause and appreciate your patience.

2. monitoring Sep 02, 2025, 02:55 PM UTC

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

3. resolved Sep 05, 2025, 05:55 PM UTC

   The issue affecting the downloading of reports and certificates has been resolved. Thank you for your patience as we addressed this matter.

Read the full incident report →

Started Jun 12, 2025, 08:04 PM UTC· resolved Aug 13, 2025, 01:31 PM UTC

1. monitoring Jun 12, 2025, 08:04 PM UTC

   Earlier today, we received reports that users were unable to view Micro Training videos. This temporary issue was caused by an outage affecting our video hosting provider. The platform vendor has since resolved the issue, and Micro Training videos are once again accessible as normal. We will continue to monitor the situation. Thank you for your patience.

2. resolved Aug 13, 2025, 01:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 29, 2025, 02:35 PM UTC· resolved Aug 13, 2025, 01:11 PM UTC

1. investigating May 29, 2025, 02:35 PM UTC

   We are currently investigating an issue affecting the User Edit Profile function. In some cases, the "Check Availability" feature for screen names may inaccurately indicate that a chosen name is available when it is not. If a duplicate screen name is selected, the profile update will not be saved, and the original screen name will remain unchanged. Our team is working to resolve this issue and will provide updates as they become available. Thank you for your patience.

2. resolved Aug 13, 2025, 01:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2025, 08:59 PM UTC· resolved May 23, 2025, 02:12 PM UTC

1. investigating May 21, 2025, 08:59 PM UTC

   We are currently investigating an issue affecting domain submissions for Dark Web Monitoring. Partners are able to add domains, but upon clicking "Save," an error message appears stating: "Failed to create client task." Our team is actively working to identify the root cause and will share updates as more information becomes available. Thank you for your patience.

2. monitoring May 21, 2025, 09:53 PM UTC

   The issue preventing domains from being saved for Dark Web Monitoring has been resolved. Our engineering team will continue to monitor to ensure the feature remains fully operational. Thank you for your patience while we worked to address this.

3. resolved May 23, 2025, 02:12 PM UTC

   The issue preventing domains from being saved for Dark Web Monitoring has been fully resolved. Thank you for your patience while we worked to address this.

Read the full incident report →

Started May 02, 2025, 04:06 PM UTC· resolved May 06, 2025, 08:44 PM UTC

1. identified May 02, 2025, 04:06 PM UTC

   We’ve identified an issue with the Google Cybersecurity Training not loading correctly through the "Go" button in the “Improve your ESS” section of the Dashboard. The training is still accessible through the Training tab. Our team has determined the cause of the issue and is actively working on a permanent fix.

2. resolved May 06, 2025, 08:44 PM UTC

   The issue with accessing the Google Cybersecurity Training from the “Improve your ESS” section on the Dashboard has been resolved. Thank you for your patience as we addressed this matter.

Read the full incident report →

Started Apr 02, 2025, 08:03 PM UTC· resolved May 06, 2025, 08:55 PM UTC

1. monitoring Apr 02, 2025, 08:03 PM UTC

   As a reminder, phase 2 of our brand transition from PII & PHI Protect to Breach Secure Now is now complete. With this transition, users will begin receiving all emails, including Micro Training emails, from Breachsecurenow.com starting on Thursday, April 3rd. Previously, these emails came from the domains security-reminders.com, pii-protect.com, and phi-protect.com. We recommend using the email template below to remind your clients of this brand transition. Brand Transition Email Template: https://portal.breachsecurenow.com/#/marketingResources/PII%20to%20BSN%20Brand%20Transition?assetId=r9cz59f5kwnkps99rxs547g You can also visit the Marketing Resource Center for additional resources related to the brand transition.

2. resolved May 06, 2025, 08:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 25, 2025, 05:41 PM UTC· resolved Aug 13, 2025, 01:11 PM UTC

1. identified Feb 25, 2025, 05:41 PM UTC

   An issue has been identified with the Catch Phish Email Plug-in not loading for some users. The cause of this issue has been linked to an update made by Microsoft which turns off all legacy Exchange user identity and callback tokens by default for Exchange Online tenants, encouraging the adoption of Nested App Authentication (NAA). This change affects Outlook add-ins that rely on these tokens, potentially impacting their functionality. Administrators can temporarily turn legacy tokens back on, but Microsoft will permanently disable them for all tenants by June 2025. We are working to ensure the smooth operation of Catch Phish while looking into options for the future. Thank you for your patience.

2. monitoring Mar 05, 2025, 04:35 PM UTC

   A temporary fix has been discovered for the issue preventing Catch Phish from loading for some users. Once legacy tokens are enabled and Outlook is restarted, Catch Phish should function normally again. A link to the instructions for turning on legacy Exchange Online tokens and re-enabling Outlook add-ins is included below. Our team is currently working on a permanent fix. If you have any additional questions, please reach out to our Support team for assistance. Thank you for your patience and understanding. https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/turn-exchange-tokens-on-off#connect-to-exchange-online-powershell

3. monitoring May 06, 2025, 05:55 PM UTC

   We’re in the final stages of testing a permanent fix for the issue preventing Catch Phish from loading for some users. Our team has been working diligently to ensure the upcoming solution is compatible with Microsoft’s evolving requirements. We expect to roll out the fix shortly. Thank you for your continued patience and partnership. We’ll provide another update as soon as the fix is live.

4. monitoring May 19, 2025, 09:32 PM UTC

   The permanent fix for the Catch Phish Email Plug-in issue is now available. Our team has completed testing and confirmed that the solution resolves the loading issue caused by Microsoft’s recent changes. Applying the fix requires removing the existing version of Catch Phish and re-deploying the updated version. Our Support team will be reaching out to those who have previously opened a ticket related to this issue. For those who have not opened a support ticket but would like detailed instructions on how to implement the permanent fix, please contact our Support team at [email protected]. Thank you for your patience and continued support as we worked toward a long-term solution.

5. resolved Aug 13, 2025, 01:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 18, 2025, 07:51 PM UTC· resolved Apr 28, 2025, 06:42 PM UTC

1. identified Feb 18, 2025, 07:51 PM UTC

   An issue has been identified which is preventing a small percentage of partners using the ESET endpoint security solution from accessing the phishing tab in the portal. There is a workaround to whitelist our AWS URL in ESET. Partners can open a support ticket if they would like our team to guide them through whitelisting ESET. Our team is currently working on a permanent fix and will provide an update as soon as possible. Thank you for your patience.

2. resolved Apr 28, 2025, 06:42 PM UTC

   The issue preventing a small percentage of partners using the ESET endpoint security solution from accessing the phishing tab in the portal has been resolved. Thank you for your patience and understanding as we addressed this matter.

Read the full incident report →

Started Feb 13, 2025, 10:07 PM UTC· resolved Mar 12, 2025, 09:47 PM UTC

1. investigating Feb 13, 2025, 10:07 PM UTC

   An issue has been discovered with the weekly Micro Trainings/Newsletters that is impacting a small percentage of users. Some users who have Micro Trainings and Newsletters disabled are still receiving emails for them. Our team is actively investigating this issue and is working on a fix. We will provide updates as more information becomes available.

2. monitoring Feb 19, 2025, 10:52 PM UTC

   A fix has been discovered for the issue with the disabling of weekly Micro Trainings/Newsletters that was impacting a small percentage of users. The issue will be resolved soon for those who have not already reset the value manually. We will continue to monitor the situation moving forward. Thank you for your patience.

3. resolved Mar 12, 2025, 09:47 PM UTC

   The issue with the disabling of weekly Micro Trainings/Newsletters has been resolved. Thank you for your patience and understanding as we addressed this matter.

Read the full incident report →

Started Feb 06, 2025, 02:51 PM UTC· resolved Feb 25, 2025, 05:33 PM UTC

1. identified Feb 06, 2025, 02:51 PM UTC

   We have identified an issue that is preventing Micro Training emails from being sent for a small percentage of our users. The issue is currently being resolved and we expect full restoration by next week. Micro Trainings are still available through the portal, the Newsfeed, the Teams application, and Catch Phish. We apologize for any inconvenience this has caused. Thank you for your understanding.

2. monitoring Feb 11, 2025, 05:37 PM UTC

   A fix has been completed for the issue that was preventing a small number of Micro Training emails from being sent. The fix will be deployed today (February 11th). We will continue to monitor the situation moving forward.

3. resolved Feb 25, 2025, 05:33 PM UTC

   After monitoring the issue preventing a small number of Micro Training emails from being sent, we have determined that the situation has been resolved. Thank you for your patience.

Read the full incident report →

Started Jan 14, 2025, 08:34 PM UTC· resolved Jan 21, 2025, 03:14 PM UTC

1. identified Jan 14, 2025, 08:34 PM UTC

   We have received reports of users experiencing a "Something Went Wrong" error when attempting to access the Dark Web Remediation Training. The root cause has been identified, and the fix has successfully passed QA. The fix will be deployed at 5 PM EST. We will provide further updates once the deployment is complete. Thank you for your patience.

2. monitoring Jan 14, 2025, 10:06 PM UTC

   The fix has been deployed for the issue preventing access to the Dark Web Remediation Training. The training is now accessible. We will continue to monitor the situation closely. Thank you for your understanding as we address this issue.

3. resolved Jan 21, 2025, 03:14 PM UTC

   The issue preventing access to the Dark Web Remediation Training has been resolved. Thank you for your patience.

Read the full incident report →