Tessian EU Outage History

Started Oct 09, 2026, 07:57 PM UTC· resolved Oct 16, 2026, 06:50 PM UTC

1. monitoring Oct 09, 2026, 07:57 PM UTC

   Starting October 7th 2026 at ~07:20 UTC Proofpoint began to receive Graph API failures when attempting to create a user's Quarantine folder for Core Email Protection API. Impact: For less than 600 individual mailboxes in total across all customers and environments, this resulted in some emails failing to quarantine. As of October 9th 2026 17:30 UTC all impacted messages have now been quarantined. Remediation: As of October 9th 2026 16:48 UTC - To prevent broader impact, Proofpoint has pushed a change where all quarantined messages are moved to a hidden folder within the user's inbox. This is how quarantine for Core Email Protection API functioned up until July 2026. Although the user can't access this folder, if they go searching for a mail item it may show in the search results. Proofpoint has escalated the issue to Microsoft to understand the initial cause. As impact is now remediated, we will only look to update the quarantine logic back once we are confident we will be able to create the required folder as expected and without error. We will hold this page open in a monitoring state until we have a better understanding of the long term timeline. Feel free to open a support case with any questions or concerns.

2. resolved Oct 16, 2026, 06:50 PM UTC

   As of October 16th 2026 13:30 UTC, Proofpoint restored Quarantine logic for Core Email Protection API to its previous state. After working closely with Microsoft, we were able to restore this functionality and create Quarantine folders without failures. After monitoring for the past few hours without issue, we will now move this to resolved.

Read the full incident report →

Started Sep 23, 2026, 04:33 PM UTC· resolved Sep 24, 2026, 04:59 PM UTC

1. identified Sep 23, 2026, 04:33 PM UTC

   We've discovered an issue with the Gateway sending Block notifications to end users. Since August 25 2026 - Any policy set to Block (not Warn), correctly blocked the sending of the email and created a security event. However, if the email was checked by the Gateway, the end user did not receive a notification that their email violated a policy and was blocked. As of September 23 2026 - Our team is correcting the issue across all customers. Block notifications will start sending to end users going forward, and backlogged block notifications from the last month are will go start to go out. For customers using the Gateway who have policies set to block, they may get reports from these end users due to the delay in the notifications. Please feel free to reach out to Support with any questions.

2. identified Sep 24, 2026, 11:11 AM UTC

   We have begun rolling out a change to restore Gateway block notifications for affected customers. Based on customer feedback, we have limited notification backfills to emails that were blocked within the last 48 hours. As the rollout progresses, some end users may receive delayed block notifications for messages that were blocked during that timeframe. If you have any questions, please contact Support.

3. resolved Sep 24, 2026, 04:59 PM UTC

   We've completed a restore of Gateway block notifications for affected customers. Block notifications are now sending to end users going forward, and backlogged notifications for the last 48 hours have sent. We appreciate your patience, and please feel free to contact support with any additional questions.

Read the full incident report →

Started Sep 04, 2026, 05:27 PM UTC· resolved Sep 04, 2026, 06:07 PM UTC

1. investigating Sep 04, 2026, 05:27 PM UTC

   Proofpoint is recovering from an issue impacting multiple services: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Cloud-Service-Portal-Access-04-SEP-2026 As a knock on effect, we have seen a slight delay in a small number of post delivery checks. The system is currently recovering and we will update once all systems are operational.

2. resolved Sep 04, 2026, 06:07 PM UTC

   As the team continues to review and monitor, they no longer see any delays on the EU Sever.

Read the full incident report →

Started Sep 03, 2026, 02:31 PM UTC· resolved Sep 04, 2026, 01:26 PM UTC

1. identified Sep 03, 2026, 02:31 PM UTC

   We've identified an issue impacting the following service and scenario: • For Adaptive Email DLP Custom Policies • Set to Silently Track • Configured to send Compliance Alerts • And scanned by the Gateway Since September 1, 2026, at 12:30 PM UTC - Compliance Alerts were not sent for policies set to Silently Track and configured to send them, when the check was done by the Gateway. Polices set to Warn, or checks done by other integrations, have no impact and Compliance Alerts function as expected. Our team is actively correcting the issue and all Alerts will be send momentarily. If you were impacted, you will notice the backlog of alerts come in all at once. We will update once complete.

2. resolved Sep 04, 2026, 01:26 PM UTC

   A fix has been applied to all customer Gateways. Compliance Alerts are now sending as expected on Custom Policies set to Silent Track which are checked by the Gateway. All backlogged Compliance Alerts impacted by this issue have now sent. If you have any additional questions, please feel free to raise a support case.

Read the full incident report →

Started Aug 05, 2026, 02:00 PM UTC· resolved Aug 05, 2026, 02:00 PM UTC

1. resolved Aug 05, 2026, 02:00 PM UTC

   We experienced an issue resulting in inbound check delays and outbound check timeouts. Impact window: Aug 5 2026: 14:00 to 17:00 UTC Impact: • Core Email Protection API: • During the window, inbound message checks may have been delayed, resulting in corresponding delays in a message being actioned and available in the portal. • Adaptive Email DLP: • During the window, outbound messages checks by the Office Add-in may have been delayed, resulting in slightly elevated timeouts. • Up to 5% of checks may have timed out and failed open via the Add-in. Our team worked quickly to take steps to address the issue and it is since resolved. Please feel free to open a support case with any additional questions.

Read the full incident report →

Started Jul 22, 2026, 06:28 PM UTC· resolved Jul 31, 2026, 03:04 PM UTC

1. monitoring Jul 22, 2026, 06:28 PM UTC

   We identified an issue impacting a subset of customer's Adaptive Email DLP Gateway. Impacted customers may have experienced a delay in end users receiving Held email notifications. Impact: • Starting July 22nd 2026 ~10:00 UTC, when an email triggered a policy and was held by the Adaptive Email DLP Gateway, the end user (sender) may not have received a timely notification that their email was held by the Gateway. • This would delay users from replying to the Held email notification and releasing the original email to the intended recipient. Proofpoint Engineering identified the issue and deployed a fix. Through close monitoring, we see new email held notifications sending without delay, and previously delayed notifications being delivered. We will continue to monitor to ensure all end user notifications are being sent as expected. Please feel free to open a support ticket with any additional questions or concerns.

2. monitoring Jul 23, 2026, 01:34 PM UTC

   Proofpoint continues to monitor, and has seen no reoccurrence of the initial issue. We have identified a lingering cosmetic issue within customer portals. Under the Gateway > Monitoring tab, customers may observe an abnormally high number of "Pending delivery" emails back to their mail server. • Emails which were held during the initial issue are incorrectly showing in this tab. • Checking our backend mail logs, we can confirm these emails have been successfully delivered back to your server, even though they may still show in the UI. • Customers are welcome to double check by doing a mail trace against the message ID We are currently working on a fix, and will hold this open in a monitoring state until the number of Pending delivery entries is corrected in customer portals is corrected.

3. monitoring Jul 24, 2026, 01:18 PM UTC

   As of 10:00 UTC July 24th 2026 - the remaining UI issue with the "Pending delivery" tab incorrectly showing emails which had already been delivered has been resolved. Please feel free to open a case with any additional questions and concerns.

4. resolved Jul 31, 2026, 03:04 PM UTC

   After extended monitoring through the week, there have been no additional delays is sending held emails. Please open a new case if you observe any new issues, we're happy to help.

Read the full incident report →

Started Jun 29, 2026, 08:38 AM UTC· resolved Jun 29, 2026, 02:31 PM UTC

1. investigating Jun 29, 2026, 08:38 AM UTC

   We are aware of an issue affecting EU portal logins on Google chrome. We are currently working with Google to have this reclassified as safe. At present, the issue appears limited to Google Safe Browsing, primarily impacting EU tenants. Other browsers, such as Safari and Firefox, are generally not affected, although some Safari users may see warnings depending on their security settings.

2. investigating Jun 29, 2026, 08:58 AM UTC

   We are aware of an issue affecting EU portal logins on Google Chrome. We are currently working with Google to have this reclassified as safe. At present, the issue appears limited to Google Safe Browsing, primarily impacting EU tenants. Other browsers, such as Safari and Firefox, are generally not affected, although some Safari users may see warnings depending on their security settings. Please note that the site itself is not compromised, and this warning is due to a misclassification.

3. identified Jun 29, 2026, 11:48 AM UTC

   Google has applied an Emergency Allowlist for the EU portals, which should immediately stop "Dangerous site" warnings from appearing to users in Chrome and other browsers using Google Safe Browsing. This action is a temporary fix while Google investigates the root cause of the false positive. Their product engineering team is working on a permanent resolution. Testing from multiple stakeholders now shows that the error is gone in Chrome, Safari, and Firefox. Google has also confirmed that the EU portal is no longer listed as dangerous on their Transparency Report. We are checking with impacted customers to confirm the resolution from their side. Please report any continued issues so we can escalate with Google if needed.

4. resolved Jun 29, 2026, 02:31 PM UTC

   Proofpoint has confirmed the Emergency Allowlist has resolved the issue for impacted customers. We will continue to work with Google to understand what caused the false positive and prevent such issues in the future. Please feel free to open a support case if you have any additional questions.

Read the full incident report →

Started Jun 24, 2026, 09:49 PM UTC· resolved Jun 24, 2026, 10:41 PM UTC

1. monitoring Jun 24, 2026, 09:49 PM UTC

   One of the detection services utilized by CEPAPI is currently experiencing delays. Emails are still being processed, checked, and actioned, but a subset of the detection stack may take up to 5-10 mins to complete analysis. Our team is actively investigating and monitoring the issue and will provide updates as more information becomes available.

2. resolved Jun 24, 2026, 10:41 PM UTC

   As of 22:30 UTC, all systems are functioning normally and impacted detection services are scanning emails without delay after remedial action by Proofpoint Engineering. Please feel free to open a support case if you have any additional questions or concerns.

Read the full incident report →

Started Jun 03, 2026, 01:37 PM UTC· resolved Jun 04, 2026, 10:19 AM UTC

1. investigating Jun 03, 2026, 01:37 PM UTC

   We are currently investigating the degradation of some features, including Silent outbound API and the Abuse Mailbox. The team is actively working to mitigate and we will follow up with more details soon.

2. identified Jun 03, 2026, 02:11 PM UTC

   Proofpoint Engineering is actively working to mitigate customer impact. We've engaged 3rd party support to address the cause, and will continue to update on progress. Full list of potential impact can be found here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-elements-of-Core-Email-Protection-API-and-Adaptive-Email-DLP-03-June-2026

3. identified Jun 03, 2026, 04:00 PM UTC

   Proofpoint Engineering is continues to mitigate customer impact per item. We remain engaged 3rd party support to address the cause and resolve the overall issue. Full list of potential impact can be found here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-elements-of-Core-Email-Protection-API-and-Adaptive-Email-DLP-03-June-2026

4. identified Jun 03, 2026, 08:46 PM UTC

   The majority of customer symptoms have been manually mitigated by Proofpoint Engineering. We continue to work with 3rd party support to address the initial cause. Full list of potential impact can be found here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-elements-of-Core-Email-Protection-API-and-Adaptive-Email-DLP-03-June-2026

5. monitoring Jun 03, 2026, 10:04 PM UTC

   Working with 3rd party vendor support, Proofpoint was able to determine this was caused by a vendor side issue, who have since deployed a fix. The underlying third party issue has been resolved as of 21:30 UTC June 3rd 2026. Proofpoint is continuing to closely monitor a full recovery. Full list of potential impact can be found here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-elements-of-Core-Email-Protection-API-and-Adaptive-Email-DLP-03-June-2026

6. resolved Jun 04, 2026, 10:19 AM UTC

   Working with 3rd party vendor support, Proofpoint was able to determine this was caused by a vendor side issue, who have since deployed a fix. The underlying third party issue has been resolved as of 21:30 UTC June 3rd 2026. Full list of potential impact can be found here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-elements-of-Core-Email-Protection-API-and-Adaptive-Email-DLP-03-June-2026

Read the full incident report →

Started May 27, 2026, 08:12 AM UTC· resolved May 28, 2026, 12:40 AM UTC

1. investigating May 27, 2026, 08:12 AM UTC

   We are aware of an issue with the Gateway journal servers at the moment. This problem is isolated to journaling and does not affect inbound or outbound mail delivery. Our teams are currently investigating, and we will follow up as soon as we have more information.

2. identified May 27, 2026, 10:54 AM UTC

   The cause of the problem with the Gateway journal servers has been identified and engineering is now rolling out a fix. This problem is limited to journaling only, and does not affect inbound or outbound mail delivery. We will follow up as soon as we have further information.

3. monitoring May 27, 2026, 12:51 PM UTC

   A fix has now been applied in both EU and US regions. Journaling services are recovering. A very small number of tenants in the EU and US are still experiencing issues and we continue to work on finding the cause for those tenants. Journal emails are flowing again for the majority customers, but please bear in mind that some queuing for journaling may persist for affected tenants for a while. This problem is limited to journaling only, and does not affect inbound or outbound mail delivery.

4. resolved May 28, 2026, 12:40 AM UTC

   As of 00:35 UTC - the small number of remaining Journal servers have returned to operational. Proofpoint will continue to monitor, but please feel free to open a case if you have any additional questions.

Read the full incident report →

Started May 22, 2026, 12:40 PM UTC· resolved May 26, 2026, 01:25 PM UTC

1. investigating May 22, 2026, 12:40 PM UTC

   We’ve been made aware of a potential issue impacting mail delivery through the Gateway. Our teams are currently investigating, and we will follow up as soon as we have more information. Emails sent to the Tessian Inbound or Outbound gateway may not be accepted and route correctly. We would encourage customers to check their Tenant's status by logging into their platform and going to Integrations > Email Deployments > Gateway > Alerting. (your platform URL)/0/admin/integrations/email_deployments/gateway_alerting If you are impacted, we would encourage you to disable routing to the Tessian Gateway to temporarily reduce the impact to your organization. O365/Exchange: 1. Go to: Exchange Admin Center (in O365: Admin → Admin Centers → Exchange) 2. Select "mail flow" in the left vertical menu 3. Select "rules" in the top horizontal menu 4. Locate your Tessian inbound/outbound rule, e.g. “Tessian Inbound”, "Tessian Outbound” 5. Un-check the tick-box to disable the rule > To resume routing to the Gateway, check the tick-box to re-enable the rule. G Suite: 1. Go to: G Suite → Gmail → Advanced Settings 2. In the Compliance section, disable the following rule: > “Tessian Inbound”

2. monitoring May 22, 2026, 01:36 PM UTC

   The team has confirmed a subset of customers were impacted on the EU. They took manual steps to resolve for impacted customers, and as of 13:30 UTC email should be flowing again for all customers. The team is continuing its investigation as it monitors our systems closely. We will provide more updates as they become available.

3. monitoring May 22, 2026, 08:05 PM UTC

   We have seen no additional failures since 13:05 UTC, and services remain healthy. Out of an abundance of caution, we will continue to monitor through the weekend.

4. resolved May 26, 2026, 01:25 PM UTC

   All systems remain operational with no regressions. The team continues its work on post incident cause, evaluations, and steps to prevent in the future. Please feel free open a support case if you would like additional information.

Read the full incident report →

Started May 16, 2026, 01:49 PM UTC· resolved May 16, 2026, 03:52 PM UTC

1. investigating May 16, 2026, 01:49 PM UTC

   We're investigating reports of Adaptive Email DLP Events being delayed showing in the portal and external API after todays Maintenance window. Checks are still being completed, actioned, and recorded. The team is working to restore full functionality.

2. identified May 16, 2026, 03:33 PM UTC

   We have identified the issue and applied a fix and are seeing signs of recovery.

3. resolved May 16, 2026, 03:52 PM UTC

   As of May 16th 2026, 15:45UTC - We've confirmed the corrective actions have lead to recovery. Adaptive Email DLP Security Events from 08:00 UTC to 15:45 UTC now show in the Security Events tab of customer portals, and calling the external API will now returns events from those time periods. Thank you for your patience, and feel free to open a support case with any follow up questions.

Read the full incident report →

Started May 13, 2026, 12:09 PM UTC· resolved May 13, 2026, 02:28 PM UTC

1. monitoring May 13, 2026, 12:09 PM UTC

   Between approximately 07:30 UTC and 08:36 UTC, some customers experienced an outage where inbound and outbound server statuses were shown as 'Unavailable'. The issue was caused by a capacity limitation encountered during the application of a routine security patch. This has been fully resolved — server statuses should now show as 'Available'. Any emails queued during the incident are expected to be delivered automatically without intervention. No data loss occurred, and we anticipate minimal delivery delays. We apologise for any disruption caused.

Read the full incident report →

Started May 13, 2026, 10:58 AM UTC· resolved May 14, 2026, 04:33 PM UTC

1. monitoring May 13, 2026, 10:58 AM UTC

   Between 07:30 UTC to 08:56 UTC, 13th May 2026 a Gateway outage occurred for customers that manifested as inbound and outbound server status being 'Unavailable'. This has since been resolved and the server statuses should now all be 'Available' once more. Emails in the queue are expected to clear themselves automatically. We are still working through how this happened and will share further details as soon as possible. Please open a support case if you are still experiencing delays. Thank you for your on-going patience.

2. monitoring May 13, 2026, 02:04 PM UTC

   Between approximately 07:30 UTC and 08:36 UTC, some customers experienced an outage where inbound and outbound server statuses were shown as 'Unavailable'. The issue was caused by a capacity limitation encountered during the application of a routine security patch. This has been fully resolved — server statuses should now show as 'Available'. Any emails queued during the incident are expected to be delivered automatically without intervention. No data loss occurred, and we anticipate minimal delivery delays. We apologise for any disruption caused, please open a support ticket if you have any questions.

3. resolved May 14, 2026, 04:33 PM UTC

   The team has been monitoring closely for the last day, and no new issues have been observed. If you have not done so already, please open a support case if you have any additional questions or concerns - we're happy to help.

Read the full incident report →

Started May 13, 2026, 04:00 AM UTC· resolved May 13, 2026, 04:00 AM UTC

1. resolved May 13, 2026, 04:00 AM UTC

   Proofpoint discovered and fixed an issue impacting Email Exfiltration efficacy for a subset of customers. From May 12th 2026 till May 22st 2026, the daily job to identify new Unauthorized address failed to successfully update for a subset of customers. This meant no new unauthorized addresses were associated with end users for those tenants - reducing efficacy over time. • Email Exfiltration still ran against outbound emails, using the list of unauthorized addresses as of May 12th. • Zero day detection was still running, catching potential unauthorized addresses not yet associated with a specific user. Once Proofpoint discovered the issue, we worked quickly to correct the issue moving forward and update all tenants with a current list of Unauthorized Addresses as of May 22nd 2026. Our team investigated the critical miss in monitoring, and is deploying a redesigned method to address the fundamental failure and catch such things in the future. Please feel free to open a support ticket if you have any additional questions.

Read the full incident report →

Started Apr 27, 2026, 02:59 PM UTC· resolved Apr 28, 2026, 07:17 PM UTC

1. investigating Apr 27, 2026, 02:59 PM UTC

   We are actively investigating an issue with the Gateway on our EU server. Emails sent to the Tessian Inbound or Outbound gateway may not be accepted and route correctly. We would encourage customers to check their Tenant's status by logging into their platform and going to Integrations > Email Deployments > Gateway > Alerting. (your platform URL)/0/admin/integrations/email_deployments/gateway_alerting Impact would have started around 14:00 UTC If you are impacted, we would encourage you to disable routing to the Tessian Gateway to temporarily reduce the impact to your organization. O365/Exchange: 1. Go to: Exchange Admin Center (in O365: Admin → Admin Centers → Exchange) 2. Select "mail flow" in the left vertical menu 3. Select "rules" in the top horizontal menu 4. Locate your Tessian inbound/outbound rule, e.g. “Tessian Inbound”, "Tessian Outbound” 5. Un-check the tick-box to disable the rule > To resume routing to the Gateway, check the tick-box to re-enable the rule. G Suite: 1. Go to: G Suite → Gmail → Advanced Settings 2. In the Compliance section, disable the following rule: > “Tessian Inbound”

2. identified Apr 27, 2026, 04:44 PM UTC

   Our team has identified the issue, and continues to work to mitigate. We have taken steps to prevent any additional customers from being impacted. For impacted customers, mitigation efforts are underway. Once complete, queued mail impacted by this issue will flow through your Tessian Gateway again. At that time, you can look to re-enable your routing rules and send new messages to the Gateway, if you've previously disabled them. We will update here as mitigations efforts continue for impacted customers.

3. identified Apr 27, 2026, 07:43 PM UTC

   Remediation of impacted customers continues. As the remediation task runs, additional individual customers fully recover. Customers who have recovered will observe mail queued from earlier start to flow through their Gateway. As a general estimate, we expect recovery of all remaining customers within the next 1-2 hours.

4. monitoring Apr 27, 2026, 08:58 PM UTC

   As of April 27th 2026, 20:45 UTC - all impacted customer Gateways have been remediated. - Mail sent to a Gateway while it was unresponsive will now be accepted, processed, and delivered. - New mail can now be safely routed to the Gateway again. If you were impacted and have additional questions or concerns, we'd encourage you to open a support ticket if you have not done so already. Although there is not longer an active impact; Proofpoint will continue with heightened monitoring for the next 24 hours to be safe.

5. resolved Apr 28, 2026, 07:17 PM UTC

   After continued monitoring, impacted Gateway servers remain healthy and no additional customers have been impacted. If you continue to have issues, please contact Support for assistance.

Read the full incident report →

Started Apr 08, 2026, 07:24 PM UTC· resolved Apr 09, 2026, 07:56 PM UTC

1. investigating Apr 08, 2026, 07:24 PM UTC

   Over the last couple hours, we've seen an increase in reports from customers who use Gsuite as their email environment. For impacted customers, the Proofpoint Inbound or Outbound gateway is rejecting connections from Gsuite, meaning mail may be delayed. Engineering is actively engaged and investigating the cause. In the meantime, we would encourage customers to disable routing to the Gateway in their Google Admin center to minimize impact. This can be done in the admin center by following these instructions: Go to: G Suite → Gmail → Advanced Settings In the Compliance section, disable the following rule(s): - “Tessian Inbound” & “Tessian Outbound” We will update once we have identified the cause, or additional viable workarounds.

2. monitoring Apr 08, 2026, 10:03 PM UTC

   For impacted customers, we observed mail began to flow through their Tessian Gateway again sometime after 20:00 UTC. On Proofpoint's end, Engineering investigated, but saw no changes and no errors in logging. In fact, despite the mail logs saying the Tessian Gateway had refused the connection, we did not even see the attempts to connect reach our servers. In parallel, we were tracking an open Google Workspace incident related to Gmail: https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT Although the description and start time roughly lined up, there weren't enough details to say it was certainly the cause. However, with the most recent update, we see that they've applied mitigation and have since seen recovery. Based off the update timestamp, this would have started sometime after 20:03 UTC. Since the timeline of the Google incident aligns with recovery we've seen on our end, it appears this Google Incident is the cause. Proofpoint will continue to monitor, and look for additional information from Google to understand why this impacted the Tessian Gateway for Gsuite customers. Customers can observe the backlog of emails processing through their gateway in their portal under Integrations > Email Deployments > Gateway > Alerting Customers who disabled their routing rules, can consider re-enabling them as desired.

3. resolved Apr 09, 2026, 07:56 PM UTC

   We have not seen additional issues since Google moved to resolved at Wednesday, 2026-04-08 14:49 PDT. At this time, we do not have additional details beyond what Google has provided on their incident page. https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT If you have additional questions, we'd encourage you to open a support case with us, and we will respond once more information is available.

Read the full incident report →

Started Apr 08, 2026, 04:44 PM UTC· resolved Apr 09, 2026, 02:48 PM UTC

1. monitoring Apr 08, 2026, 04:44 PM UTC

   Today, April 8th 2026, between 14:31 and 14:48 UTC, we experienced an issue impacting the visibility of Internal Emails in the Investigate & Respond tab of Core Email Protection API. Impact: • All emails received, sent internally, April 8th 2026 between 14:31 and 14:48 UTC. • These emails were successfully checked by Core Email Protection API. • If it triggered detection, a Security Event was successfully created and can be found in your portal. • Any associated remediation actions, such as Warn or Quarantined according to your configuration, were successfully actioned. • If you attempt to search for these internal emails in Investigate & Respond, it will not return any results. • External emails, or internal emails outside the impact window, will still show in I&R. The team took quick action to alleviate the issue and minimize the impact window. After thorough investigation, we've determined we will not be able to restore the missing emails. Proofpoint will continue to monitor closely overnight.

2. resolved Apr 09, 2026, 02:48 PM UTC

   The team has been monitoring, and all systems remain stable without recurrence. Feel free to open a support case if you have any additional questions.

Read the full incident report →

Started Mar 02, 2026, 01:58 PM UTC· resolved Mar 05, 2026, 11:39 AM UTC

1. investigating Mar 02, 2026, 01:58 PM UTC

   In the Core Email Protection (CEPAPI) Security Events view, some threat event details processed cannot be viewed in full. The timeframe for when these events were received and processed is Friday 27th Feb 10:33 am to 2nd March 10:59am For events meeting this criteria, the following error may be displayed: "event details are currently unavailable for this email. We are working on the issue to get it fixed as soon as possible" Engineering is aware of this problem and is currently working on a solution.

2. identified Mar 02, 2026, 03:26 PM UTC

   As of 14:10 UTC March 2nd - all events and triggered emails from the impact window can now be viewed in the Investigate & Respond tab. Customers are encouraged to review and action impacted events via I&R in the short term. The team is currently working to restore the same emails in the Security Events tab. As a reminder, this impacts triggered emails from Friday 27th Feb 10:33am UTC - Monday 2nd March 10:59am UTC.

3. identified Mar 02, 2026, 08:19 PM UTC

   Our team has identified a potential way to restore events from Friday 27th Feb 10:33am UTC - Monday 2nd March 10:59am UTC in the Security Events tab. The team is currently conducting rigorous testing, and will look to deploy it over the course of the week if testing goes well. We will update once this restoration is underway. In the meantime, all triggered emails remain available in the Investigate & Respond tab of your portal.

4. identified Mar 03, 2026, 03:22 PM UTC

   The process to restore missing Security Events has passed all testing, and Proofpoint will begin the remediation process momentarily. We will update again once all Security Events from the impact window have been restored.

5. identified Mar 04, 2026, 06:55 PM UTC

   As an update, the majority of Security Events have been backfilled successfully. The process continues for a couple final events, and we will update once fully complete and validated.

6. resolved Mar 05, 2026, 11:39 AM UTC

   All security events have now been successfully restored and validated. Remediation is now completed.

Read the full incident report →

Started Jan 30, 2026, 06:07 PM UTC· resolved Feb 03, 2026, 10:48 AM UTC

1. monitoring Jan 30, 2026, 06:07 PM UTC

   We observed intermittent email check timeouts on our EU server earlier today. Between 11:00-1:00 UTC: Adaptive Email DLP - up to 6% of Outbound emails may have sent partially or fully unchecked. Core Email Protection API - up to 2% of Inbound emails may have been delivered partially or fully unchecked. The issue has stabilized, and our team has not seen a recurrence as we closely monitor. We will continue to monitor through the weekend and update if anything changes.

2. monitoring Feb 02, 2026, 11:59 AM UTC

   A small number of email check timeouts were seen on our EU server earlier today. Between 08:22-09:52 UTC: Core Email Protection API - up to 0.06% of Inbound emails may have been delivered partially or fully unchecked. We will continue to monitor and update if anything changes.

3. resolved Feb 03, 2026, 10:48 AM UTC

   After monitoring for the past day no further increase in timeouts has been observed and email checks have returned to normal.

Read the full incident report →

Started Jan 22, 2026, 09:27 PM UTC· resolved Jan 23, 2026, 02:06 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 21, 2026, 04:33 PM UTC· resolved Jan 22, 2026, 03:13 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 15, 2026, 04:18 PM UTC· resolved Jan 15, 2026, 05:09 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 11, 2026, 12:25 AM UTC· resolved Jan 11, 2026, 11:58 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 12, 2025, 05:31 PM UTC· resolved Dec 12, 2025, 07:37 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →