Tessian 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:13 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:28 PM UTC· resolved Sep 04, 2026, 06:24 PM UTC

1. monitoring Sep 04, 2026, 05:28 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:24 PM UTC

   As of 18:20 UTC, there is no longer any impact to the US servers and all systems are operational.

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 21, 2026, 03:38 PM UTC· resolved Aug 21, 2026, 07:28 PM UTC

1. identified Aug 21, 2026, 03:38 PM UTC

   We are experiencing a check lag on US-based portals at the moment. This issue began at 14:14 UTC Friday 21st August. Engineering is investigating the issue and working on a solution. You may experience timeouts checking messages during this time. We will update this status page with further details and progress.

2. identified Aug 21, 2026, 03:39 PM UTC

   We are experiencing a check lag on US-based portals at the moment. This issue began at 14:14 UTC Friday 21st August. Engineering is investigating the issue and working on a solution. You may experience timeouts checking inbound messages during this time.

3. resolved Aug 21, 2026, 07:28 PM UTC

   Between 14:14 UTC and 18:05 UTC, we experienced a delay in Defender checks affecting inbound email processing. Our Engineering team investigated the issue, and following continued monitoring, checks are now performing as expected. If you have any additional questions, please don't hesitate to open 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. Impact window: Aug 5 2026: 14:00 to 14:30 UTC Impact: During the window, inbound message checks may have been delayed, resulting in corresponding delays in a message being actioned and available in the portal. • Maximum observed delay: ~15 minutes Our team quickly took 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 28, 2026, 02:24 PM UTC· resolved Jul 31, 2026, 01:58 PM UTC

1. identified Jul 28, 2026, 02:24 PM UTC

   We are currently investigating an issue causing delays in live syncing. As a result Email Misdelivery, Exfiltration Protection and Core Email Protection API may experience reduced classification accuracy. Additionally, Core Email Protection API checks are experiencing delays which may result in some missed flags. Our engineering team is actively working to identify the root cause and restore normal service. We will provide further updates as more information becomes available.

2. monitoring Jul 28, 2026, 06:51 PM UTC

   As of 18:18 UTC, all systems are operating within expected limits. Our teams remain actively engaged in monitoring the environment. We appreciate your patience and understanding. If you have further questions or concerns, we'd encourage you to open a Support Case for further assistance.

3. resolved Jul 31, 2026, 01:58 PM UTC

   After continued monitoring, for the last 48 hours all systems remain stable.

Read the full incident report →

Started Jul 22, 2026, 06:28 PM UTC· resolved Jul 24, 2026, 01:18 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. On our US Server, during recovery later on July 22nd, we observed intermittent delays with users releasing emails, where replies did not process right away, which have now been fully resolved. 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. resolved 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.

Read the full incident report →

Started Jul 06, 2026, 04:03 PM UTC· resolved Jul 06, 2026, 05:50 PM UTC

1. investigating Jul 06, 2026, 04:03 PM UTC

   We are currently investigating issues logging into portals on our US Server. What attempting to access your platform, you may receiving the following error "503 Service Temporarily Unavailable". Proofpoint Engineering is actively engaged and investigating.

2. identified Jul 06, 2026, 04:23 PM UTC

   We are seeing signs of recovery, and portals are once again accessible. Proofpoint Engineering is continuing to investigate and monitor to ensure a full and stable recovery. We will continue to update as more information becomes available.

3. resolved Jul 06, 2026, 05:50 PM UTC

   As of 16:15 UTC, Portal Access has fully recovered and we remain stable. If you have not done so already, please feel free to a support case for additional information as needed.

Read the full incident report →

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

1. monitoring Jun 24, 2026, 09:47 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 12, 2026, 06:01 PM UTC· resolved Jun 13, 2026, 12:31 AM UTC

1. monitoring Jun 12, 2026, 06:01 PM UTC

   Proofpoint investigated elevated error rates processing inbound and outbound emails on our US Server. On June 12 2026 from 14:30 UTC to 16:19 UTC, ~2% of emails sent or received failed to process. Proofpoint Engineering have remediated the issue, and is currently monitoring. For Core Email Protection API - this mean impacted inbound emails were not initially submitted for scoring, did not create a security event, and could not be found in Investigation & Respond. Missed emails are currently being re-submitted, effectively translating to a delay in processing and remediation where applicable. For Adaptive Email DLP - this means reporting for M365 add-in user responses may be temporarily inaccurate on the timeline of a security event. A small percentage of checks done by the M365 Add-in quickly timed out and failed open during the impact window. For customers using the Gateway, these check would have been routed to and completed by the Gateway.

2. resolved Jun 13, 2026, 12:31 AM UTC

   After continued monitoring, all systems remain healthy. Please feel free to open a support case if you have additional questions.

Read the full incident report →

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

1. investigating Jun 03, 2026, 01:38 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. investigating Jun 03, 2026, 02:12 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:44 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 29, 2026, 09:05 AM UTC· resolved Jun 02, 2026, 02:46 PM UTC

1. investigating May 29, 2026, 09:05 AM UTC

   We are currently investigating an issue impacting some Core Email Protection API and AEDLP customers. Since 20:48 UTC 28th May 2026, a subset of mailboxes stopped syncing across some customers. A workaround was applied at 02:30 UTC May 29th and we are seeing impacted mailboxes connecting again. We are continuing to work to restore full functionality. The team is working diligently and with urgency on full remediation.

2. identified May 29, 2026, 03:09 PM UTC

   Proofpoint has identified the cause, and continues to work on a resolution for impacted customers. For full details of the impact, please consult here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026 We will continue to update on the progress of resolution via this page and the community article.

3. identified May 29, 2026, 06:26 PM UTC

   By May 29 2026 - 14:00 UTC, Proofpoint Engineering deployed a potential fix and have been monitoring the results. We have now started to see slow recovery across the impacted customer base. We will continue to monitor and explore options to speed recovery. At this stage in recovery we do not yet have an expected timeline, but will continue to evaluate and provide one as able. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

4. identified May 29, 2026, 09:01 PM UTC

   Proofpoint Engineering continues to deploy incremental fixes to speed up recovery, however progress continues slowly. At this time we still do not have an expected timeline, but cross functional teams continue to actively explore all avenues available until we achieve a full recovery. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

5. identified May 30, 2026, 01:32 AM UTC

   Proofpoint Engineering continues to monitor recovery and aide in efforts, in addition to continued optimization, we have engaged 3rd party vendor support to accelerate recovery where relevant. At this time we still do not have an expected timeline, but cross functional teams continue to actively explore all avenues available until we achieve a full recovery. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

6. identified May 30, 2026, 09:59 AM UTC

   Proofpoint Engineering remains engaged with 3rd party vendor support and is actively monitoring recovery. At this time we still do not have an expected timeline, but cross functional teams continue to actively explore all avenues available until we achieve a full recovery. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

7. identified May 30, 2026, 05:16 PM UTC

   Proofpoint Engineering identified additional steps to speed up recovery, and has seen positive results after testing and deploying. As of right now, we tentatively estimate the last of impacted mailboxes to recover after 00:00 UTC June 1st, in the early morning hours. As we progress, we will update accordingly. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

8. identified May 31, 2026, 01:48 AM UTC

   Proofpoint Engineering continues to monitor recovery, and it remains on track. As of right now, we tentatively estimate the last of impacted mailboxes to recover after 00:00 UTC June 1st, in the early morning hours. As we progress, we will update accordingly. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

9. identified May 31, 2026, 01:51 PM UTC

   Proofpoint Engineering continues to monitor an on track recovery, making adjustments as needed. As of right now, we tentatively estimate the last of impacted mailboxes to recover after 00:00 UTC June 1st, in the early morning hours. As we progress, we will update accordingly. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

10. identified May 31, 2026, 07:13 PM UTC

    Proofpoint Engineering continues to monitor as we approach recovery for all mailboxes. As of right now, we tentatively estimate the last of impacted mailboxes to recover after 00:00 UTC June 1st, in the early morning hours. As we progress, we will update accordingly. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

11. identified Jun 01, 2026, 02:02 AM UTC

    At this time, the majority of customers and mailboxes have recovered. For a small number of customers, individual mailboxes remain disconnected, and Proofpoint Engineering is investigating each. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

12. monitoring Jun 01, 2026, 12:10 PM UTC

    Proofpoint Engineering continued to investigate the remaining individual mailboxes overnight, and as of 01-June-2026 07:30 UTC all mailboxes impacted by this Service Interruption are resolved. Proofpoint continues to work on post incident activities and monitoring. As incident is now stable, no further updates will be provided and we will move this to resolved after 24 hours. We'd encourage you to open a Support Case if you have any additional questions or concerns. You can read the full impact per product, here: https://proofpoint.my.site.com/community/s/article/Proofpoint-Service-Interruption-Affecting-Core-Email-Protection-API-Protection-29-May-2026

13. resolved Jun 02, 2026, 02:46 PM UTC

    All systems remain stable, and Proofpoint continues to work on post incident activities and monitoring. We'd encourage you to open a Support Case if you have any additional questions or concerns.

Read the full incident report →

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

1. investigating May 27, 2026, 08:13 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:55 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:52 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 13, 2026, 02:20 PM UTC· resolved May 13, 2026, 02:20 PM UTC

1. resolved May 13, 2026, 02:20 PM UTC

   Between 13:55 and 14:20 UTC , we were alerted to an increase in timeouts on our US server for Outbound checks. Outbound emails sent during the impact period may have timed out and sent unchecked. The team quickly took steps to mitigate and will take the appropriate actions to prevent it in the future.

Read the full incident report →

Started May 13, 2026, 12:10 PM UTC· resolved May 13, 2026, 02:23 PM UTC

1. investigating May 13, 2026, 12:10 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:59 AM UTC· resolved May 14, 2026, 04:33 PM UTC

1. monitoring May 13, 2026, 10:59 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:05 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. We will close this status as resolved after 24 hours monitoring.

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 08, 2026, 07:24 PM UTC· resolved Apr 09, 2026, 07:57 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:04 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:57 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:47 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:47 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 05, 2026, 11:47 AM UTC· resolved Mar 05, 2026, 11:47 AM UTC

1. monitoring Mar 05, 2026, 11:47 AM UTC

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

2. resolved Mar 05, 2026, 11:47 AM UTC

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

Read the full incident report →

Started Feb 24, 2026, 05:19 PM UTC· resolved Feb 26, 2026, 12:37 PM UTC

1. identified Feb 24, 2026, 05:19 PM UTC

   Around 4pm UTC we began seeing delayed Defender checks for inbound emails. For API users, emails may experience up to a 600 second delay for emails to be checked and quarantined. We are looking into this and will provide updates here.

2. monitoring Feb 24, 2026, 06:20 PM UTC

   We are no longer seeing delays in CEPAPI Defender checks. Our team is continuing to monitor this issue.

3. resolved Feb 26, 2026, 12:37 PM UTC

   We are no longer seeing delays in Defender checks.

Read the full incident report →

Started Jan 22, 2026, 09:27 PM UTC· resolved Jan 23, 2026, 01:50 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 15, 2026, 04:17 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 →