Critical December 5, 2025 - Detected by Pingoru
- Dec 05, 2025, 08:50 AM UTC
- Resolved
- Dec 05, 2025, 09:13 AM UTC
- Duration
- 23m
Affected: U.S. West0U.S. West1U.S. West2U.S. West3U.S. East0U.S. East1U.S. East2U.S. East3U.S. East4U.S. SouthWest1CAN1 (Canada)UK1 (U.K.)DE1 (Germany)CH1 (Switzerland)AUS2 (Australia)JP1 (Japan)HK1 (East Asia)
Timeline · 3 updates
-
investigating Dec 05, 2025, 03:06 PM UTC
Customers were experiencing a "500" error during this issue
-
investigating Dec 05, 2025, 03:07 PM UTC
We are continuing to investigate this issue.
-
resolved Dec 05, 2025, 03:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 10, 2025, 01:08 PM UTC
- Resolved
- Nov 10, 2025, 03:59 PM UTC
- Duration
- 2h 51m
Affected: U.S. East4
Timeline · 3 updates
-
investigating Nov 10, 2025, 01:08 PM UTC
We are currently investigating this issue.
-
monitoring Nov 10, 2025, 01:37 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 10, 2025, 03:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 07, 2025, 06:45 PM UTC
- Resolved
- Nov 08, 2025, 05:03 PM UTC
- Duration
- 22h 17m
Affected: Bulk Email
Timeline · 4 updates
-
identified Nov 07, 2025, 06:45 PM UTC
Customer may see email blasts delays and failures. Teams working on addressing the issue and have identified the cause.
-
identified Nov 07, 2025, 07:24 PM UTC
Delayed email blasts have processed. The teams are continuing to address root causes of the issue to ensure issues to not resurface.
-
monitoring Nov 07, 2025, 07:53 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 08, 2025, 05:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 31, 2025, 09:03 PM UTC
- Resolved
- Nov 01, 2025, 09:53 AM UTC
- Duration
- 12h 49m
Affected: Learning Web
Timeline · 4 updates
-
investigating Oct 31, 2025, 09:03 PM UTC
We are currently investigating this issue.
-
identified Oct 31, 2025, 11:04 PM UTC
Teams are working on resolution. Customers may see slowness and hanging in some areas of the platform.
-
monitoring Nov 01, 2025, 12:36 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 01, 2025, 09:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 04:26 PM UTC
- Resolved
- Oct 30, 2025, 04:39 AM UTC
- Duration
- 12h 13m
Affected: U.S. West0U.S. West1U.S. West2U.S. West3U.S. East0U.S. East1U.S. East2U.S. East3U.S. East4U.S. SouthWest1Office OnlineOutlook Add-In
Timeline · 4 updates
-
investigating Oct 29, 2025, 04:26 PM UTC
Seismic is seeing issues with services in Microsoft Azure Cloud and AWS services. Any impact to Seismic is being investigated. At this time all regions appear operational.
-
identified Oct 29, 2025, 04:41 PM UTC
We are seeing issues loading the Outlook Add-In due to service issues in Azure Cloud Services. The team is continuing to investigate and in communication with Azure.
-
identified Oct 29, 2025, 05:12 PM UTC
Issues have bee isolated to Azure, no impact to AWS. Azure is currently assessing failover options. At this time Seismic is seeing impact to the Outlook Add-In. They will continue to provide Seismic updates.
-
resolved Oct 30, 2025, 04:39 AM UTC
Azure closed out its incident and full recovery was observed at approximately 4:20 PM PDT. Seismic observed loading issues with the Outlook Add-in during the incident. Details about the incident can be located here. https://azure.status.microsoft/en-us/status/history/
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 04:28 PM UTC
- Resolved
- Oct 21, 2025, 12:04 AM UTC
- Duration
- 7h 35m
Affected: Digital Sales RoomBulk EmailFTP ServiceLearning WebLiveInsightsLiveSend
Timeline · 6 updates
-
investigating Oct 20, 2025, 04:28 PM UTC
We are currently investigating this issue.
-
investigating Oct 20, 2025, 04:35 PM UTC
We are continuing to investigate this issue.
-
identified Oct 20, 2025, 04:43 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Oct 20, 2025, 05:12 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Oct 20, 2025, 09:24 PM UTC
We are seeing recovery from the Amazon AWS outages reported today. We are continuing to monitor all Seismic services running on the Amazon AWS cloud.
-
resolved Oct 21, 2025, 12:04 AM UTC
Amazon AWS has provided a final update on today incident. https://health.aws.amazon.com/health/status
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:55 AM UTC
- Resolved
- Oct 20, 2025, 10:08 AM UTC
- Duration
- 13m
Affected: U.S. East1
Timeline · 2 updates
-
investigating Oct 20, 2025, 09:55 AM UTC
We are currently experiencing limited service impacts due to a third-party vendor incident affecting AWS infrastructure in the us-east-1 region. We are actively monitoring the situation and will provide updates as the vendor works toward resolution.
-
resolved Oct 20, 2025, 10:08 AM UTC
We are starting to see recovery of infrastructure in AWS’ US-East-1 region, and will continue to monitor the recovery progress. We will continue to provide updates as they become available.
Read the full incident report →
- Detected by Pingoru
- Oct 14, 2025, 03:23 PM UTC
- Resolved
- Oct 14, 2025, 04:40 PM UTC
- Duration
- 1h 17m
Affected: U.S. East0U.S. East2U.S. East3
Timeline · 3 updates
-
investigating Oct 14, 2025, 03:23 PM UTC
We are currently investigating this issue.
-
monitoring Oct 14, 2025, 03:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 14, 2025, 04:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 14, 2025, 01:39 PM UTC
- Resolved
- Oct 14, 2025, 04:40 PM UTC
- Duration
- 3h 1m
Affected: U.S. West0U.S. West1U.S. West2
Timeline · 3 updates
-
investigating Oct 14, 2025, 01:39 PM UTC
We are currently investigating this issue.
-
monitoring Oct 14, 2025, 03:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 14, 2025, 04:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 13, 2025, 05:12 PM UTC
- Resolved
- Oct 13, 2025, 05:42 PM UTC
- Duration
- 30m
Affected: Learning Web
Timeline · 4 updates
-
investigating Oct 13, 2025, 05:12 PM UTC
We are currently investigating this issue.
-
identified Oct 13, 2025, 05:25 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 13, 2025, 05:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 13, 2025, 05:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 02:29 PM UTC
- Resolved
- Oct 09, 2025, 04:18 PM UTC
- Duration
- 1h 48m
Affected: U.S. East0U.S. East2U.S. East3
Timeline · 3 updates
-
investigating Oct 09, 2025, 02:29 PM UTC
We are currently investigating this issue.
-
monitoring Oct 09, 2025, 02:40 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 09, 2025, 04:18 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2025, 05:20 PM UTC
- Resolved
- Oct 07, 2025, 08:21 PM UTC
- Duration
- 3h 1m
Affected: LiveSend
Timeline · 3 updates
-
investigating Oct 07, 2025, 05:20 PM UTC
We are currently investigating this issue.
-
monitoring Oct 07, 2025, 06:25 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 07, 2025, 08:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2025, 04:02 PM UTC
- Resolved
- Sep 30, 2025, 06:13 PM UTC
- Duration
- 2h 11m
Affected: U.S. East4
Timeline · 4 updates
-
investigating Sep 30, 2025, 04:02 PM UTC
We are currently investigating this issue.
-
identified Sep 30, 2025, 04:44 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 30, 2025, 04:50 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 30, 2025, 06:13 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 27, 2025 - Detected by Pingoru
- Sep 27, 2025, 01:07 AM UTC
- Resolved
- Sep 28, 2025, 06:56 PM UTC
- Duration
- 1d 17h
Affected: CH1 (Switzerland)
Timeline · 5 updates
-
identified Sep 27, 2025, 01:07 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Sep 27, 2025, 02:04 AM UTC
We are continuing to work on a fix for this issue.
-
identified Sep 27, 2025, 02:38 AM UTC
Microsoft Azure has identified an issue in their Switzerland North region and is currently working on next steps.
-
monitoring Sep 27, 2025, 05:49 AM UTC
Microsoft Azure has restored service in the Switzerland region.
-
resolved Sep 28, 2025, 06:56 PM UTC
Azure fully resolved the incident and all Seismic services were recovered. We will continue to monitor closely and initiate failover plans if needed.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2025, 06:52 PM UTC
- Resolved
- Sep 22, 2025, 10:49 PM UTC
- Duration
- 3h 57m
Affected: U.S. East0U.S. East2U.S. East3
Timeline · 4 updates
-
investigating Sep 22, 2025, 06:52 PM UTC
We are currently investigating this issue.
-
identified Sep 22, 2025, 07:28 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 22, 2025, 09:06 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 22, 2025, 10:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2025, 05:21 PM UTC
- Resolved
- Sep 05, 2025, 12:57 PM UTC
- Duration
- 7d 19h
Affected: Google Drive Sync
Timeline · 4 updates
-
investigating Aug 28, 2025, 05:21 PM UTC
New users receiving "app is blocked" message when connecting to Google drive. We are currently investigating.
-
identified Aug 29, 2025, 04:21 PM UTC
Seismic is working with Google to resolve the issue with new user connections.
-
identified Sep 02, 2025, 09:14 PM UTC
Seismic and Google are continuing to make progress on resolving the access issues for new users connecting Google. Our team is treating it with top priority.
-
resolved Sep 05, 2025, 12:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2025, 01:28 PM UTC
- Resolved
- Aug 27, 2025, 02:35 PM UTC
- Duration
- 1h 6m
Affected: U.S. West3
Timeline · 4 updates
-
investigating Aug 27, 2025, 01:28 PM UTC
We are currently investigating this issue.
-
monitoring Aug 27, 2025, 02:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 27, 2025, 02:01 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 27, 2025, 02:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2025, 10:31 PM UTC
- Resolved
- Aug 14, 2025, 12:12 AM UTC
- Duration
- 1d 1h
Affected: U.S. East3
Timeline · 3 updates
-
investigating Aug 12, 2025, 10:31 PM UTC
We are currently investigating this issue.
-
monitoring Aug 12, 2025, 10:44 PM UTC
Issue is resolved and teams are investigating root cause.
-
resolved Aug 14, 2025, 12:12 AM UTC
Please contact Seismic Support for additional for official RCA.
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2025, 03:25 PM UTC
- Resolved
- Aug 10, 2025, 03:08 PM UTC
- Duration
- 1d 23h
Affected: U.S. West2U.S. West3U.S. East1U.S. East2U.S. East3CAN1 (Canada)
Timeline · 7 updates
-
investigating Aug 08, 2025, 03:25 PM UTC
We are currently investigating this issue.
-
identified Aug 08, 2025, 04:00 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Aug 08, 2025, 04:48 PM UTC
We are continuing to work on a fix for this issue.
-
identified Aug 08, 2025, 07:16 PM UTC
Teams have identified the issue and are working on deploying a fix.
-
identified Aug 08, 2025, 10:59 PM UTC
We estimate the full fix will be deployed to production at approximately 2:00 UTC.
-
monitoring Aug 09, 2025, 06:32 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 10, 2025, 03:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2025, 08:31 PM UTC
- Resolved
- Jul 29, 2025, 02:47 AM UTC
- Duration
- 6h 15m
Affected: Service Platform
Timeline · 3 updates
-
investigating Jul 28, 2025, 08:31 PM UTC
We are currently investigating this issue.
-
monitoring Jul 29, 2025, 02:09 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 29, 2025, 02:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2025, 06:18 PM UTC
- Resolved
- Jul 18, 2025, 05:16 AM UTC
- Duration
- 10h 57m
Affected: LiveSocial Admin ConsoleLiveSocial Application
Timeline · 3 updates
-
identified Jul 17, 2025, 06:18 PM UTC
We are currently experiencing degraded performance impacting the LiveSocial > ProofPoint integration. ProofPoint Engineering has identified the root cause and is actively working on a fix.
-
monitoring Jul 17, 2025, 11:39 PM UTC
ProofPoint has implemented a fix and we are monitoring the results.
-
resolved Jul 18, 2025, 05:16 AM UTC
ProofPoint has resolved this incident.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2025, 02:32 PM UTC
- Resolved
- Jul 17, 2025, 07:36 PM UTC
- Duration
- 5h 3m
Affected: DIY DashboardsLiveInsights
Timeline · 4 updates
-
investigating Jul 17, 2025, 02:32 PM UTC
We are currently investigating this issue.
-
identified Jul 17, 2025, 03:15 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 17, 2025, 04:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 17, 2025, 07:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2025, 05:24 PM UTC
- Resolved
- Jul 12, 2025, 10:07 AM UTC
- Duration
- 16h 42m
Affected: LiveInsights
Timeline · 2 updates
-
investigating Jul 11, 2025, 05:24 PM UTC
We are currently investigating this issue.
-
resolved Jul 12, 2025, 10:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2025, 03:39 PM UTC
- Resolved
- Jul 08, 2025, 06:42 PM UTC
- Duration
- 3h 2m
Affected: Content Downloads
Timeline · 4 updates
-
investigating Jul 08, 2025, 03:39 PM UTC
Our team is looking into reports that some file types are experiencing problems when attempting to download from the application
-
identified Jul 08, 2025, 03:48 PM UTC
Teams are currently working on a fix. This issue only affects files with a & character in the title. File downloads will work if the user adds the correct file extension to the file after it's been downloaded.
-
monitoring Jul 08, 2025, 04:35 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 08, 2025, 06:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2025, 01:40 PM UTC
- Resolved
- Jun 30, 2025, 05:17 PM UTC
- Duration
- 3h 36m
Affected: U.S. East4
Timeline · 4 updates
-
investigating Jun 30, 2025, 01:40 PM UTC
We are currently investigating this issue.
-
monitoring Jun 30, 2025, 02:54 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 30, 2025, 02:54 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 30, 2025, 05:17 PM UTC
This incident has been resolved.
Read the full incident report →