Mar 17, 12:44 PDT
Resolved - This incident has been resolved.
Mar 17, 11:43 PDT
Update - We are continuing to monitor for any further issues.
Mar 17, 08:02 PDT
Monitoring - A mitigation has been put in place and SMTP / Inbound email processing in our EU region is back to full working behavior.
Mar 17, 07:22 PDT
Update - We are continuing to work on a fix for this issue.
Mar 17, 04:56 PDT
Identified - The issue has been identified and a fix is being implemented.
Mar 17, 03:29 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 11:43 PDT
Update - We are continuing to monitor for any further issues.
Mar 17, 08:02 PDT
Monitoring - A mitigation has been put in place and SMTP / Inbound email processing in our EU region is back to full working behavior.
Mar 17, 07:22 PDT
Update - We are continuing to work on a fix for this issue.
Mar 17, 04:56 PDT
Identified - The issue has been identified and a fix is being implemented.
Mar 17, 03:29 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 08:02 PDT
Monitoring - A mitigation has been put in place and SMTP / Inbound email processing in our EU region is back to full working behavior.
Mar 17, 07:22 PDT
Update - We are continuing to work on a fix for this issue.
Mar 17, 04:56 PDT
Identified - The issue has been identified and a fix is being implemented.
Mar 17, 03:29 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 07:22 PDT
Update - We are continuing to work on a fix for this issue.
Mar 17, 04:56 PDT
Identified - The issue has been identified and a fix is being implemented.
Mar 17, 03:29 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 04:56 PDT
Identified - The issue has been identified and a fix is being implemented.
Mar 17, 03:29 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 03:29 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 02:48 PDT
Update - We are continuing to investigate this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Mar 17, 02:20 PDT
Investigating - We are currently investigating this issue.
Feb 10, 11:22 PST
Resolved - This incident has been resolved.
Feb 10, 11:20 PST
Update - A fix has been implemented and we are monitoring the results.
Feb 10, 11:19 PST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 10, 09:23 PST
Investigating - Our team is investigating degraded performance in our logs and event APIs.
Feb 10, 11:20 PST
Update - A fix has been implemented and we are monitoring the results.
Feb 10, 11:19 PST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 10, 09:23 PST
Investigating - Our team is investigating degraded performance in our logs and event APIs.