Update - The ingestion backlog for Instant Bloomberg and Bloomberg Messaging continues to process. Content is searchable through 6/21.

Next update by June 27, 18:00 PDT
Jun 25, 08:29 PDT
Update - The ingestion backlog for Instant Bloomberg and Bloomberg Messaging continues to decrease. Content is searchable through 6/14.

Next update by June 24, 18:00 PDT.
Jun 17, 15:51 PDT
Update - The ingestion backlog of Instant Bloomberg and Bloomberg Messaging continues to decrease. Content is searchable through June 9.

Next update by June 17, 18:00 PDT.
Jun 14, 16:53 PDT
Update - The ingestion backlog of Instant Bloomberg and Bloomberg Messaging continues to decrease.

Next update by June 14, 18:00 PDT.
Jun 13, 17:33 PDT
Update - The ingestion backlog of Instant Bloomberg and Bloomberg Messaging continues to decrease.

Next update by June 13, 18:00 PDT.
Jun 12, 18:03 PDT
Update - The ingestion backlog of Instant Bloomberg and Bloomberg Messaging continues to decrease. Messages from June 5 are now being processed.

Next update by June 12, 18:00 PDT.
Jun 10, 15:30 PDT
Update - We continue to monitor ingestion delays of Instant Bloomberg and Bloomberg Messaging. Some clients remain delayed multiple days.

Next update for this issue by June 10, 18:00 PDT.
Jun 6, 17:03 PDT
Update - We continue to see Bloomberg ingestion improvement and are monitoring closely.

Next update for this issue by June 6, 18:00 PDT.
Jun 3, 17:00 PDT
Update - Network optimizations last night are yielding improved ingestion performance of Instant Bloomberg and Bloomberg Messaging.



Next update for this issue by June 3, 18:00 PDT.
May 31, 16:39 PDT
Update - Engineering continues to remediate ingestion delays of Instant Bloomberg and Bloomberg Messaging. While most clients are now current, we are focusing resources on several that are still delayed across multiple days.


Next update for this issue by 18:00 PDT, May 31.
May 29, 16:52 PDT
Update - Engineering is engaged in efforts to resolve ingestion delay of Instant Bloomberg and Bloomberg Messaging.

Next update for this issue by 18:00 PDT, May 29.
May 24, 16:32 PDT
Update - We continue to investigate causes of the ingestion delay for Instant Bloomberg and Bloomberg Messaging. Ingestion is delayed up to three days for many clients.  Delays in policy scanning of  Bloomberg Messaging is a result of significant ingestion that was successfully completed over the past weekend.

 

Next update for this issue will be provided by 5 pm Pacific, 5/24.
May 21, 14:56 PDT
Monitoring - We have identified a probable cause of the ingestion delay for Instant Bloomberg and Bloomberg Messaging and have applied a change. We are now monitoring the results.

Next update for this issue will be provided by 5 pm Pacific, 5/17.
May 16, 17:04 PDT
Update - We continue to investigate delays of Instant Bloomberg and Bloomberg Messaging ingestion processing. 

Next update for this issue will be provided by 5 pm Pacific, 5/20.
May 15, 17:47 PDT
Update - We continue to investigate delays of Instant Bloomberg and Bloomberg Messaging ingestion processing.

Next update for this issue will be provided by 5 pm Pacific, 5/15.
May 14, 17:07 PDT
Investigating - We are investigating delays of Instant Bloomberg and Bloomberg Messaging ingestion processing.

 

Next update for this issue will be provided by 5 pm Pacific, 5/14.
May 13, 14:28 PDT
Update - We are continuing to monitor email policy scanning. For many clients, email policy scanning is delayed up to five days.

Next update by June 27, 18:00 PDT
Jun 24, 19:24 PDT
Update - We are continuing to monitor policy scanning progress. For many clients, email policy scanning is delayed up to four days.

Next update by June 24, 18:00 PDT.
Jun 21, 16:03 PDT
Update - We are continuing to monitor policy scanning progress. For many clients, email policy scanning is delayed up to three days.

Next update by June 21, 18:00 PDT.
Jun 17, 15:50 PDT
Update - We are continuing to monitor through the weekend to measure progress. For many clients, email policy scanning is delayed up to four days.

Next update by June 17, 18:00 PDT.
Jun 14, 17:32 PDT
Update - We have deployed an enhancement to the email policy scanning application to improve performance. We will monitor through the weekend to measure the impact. For many clients, email policy scanning is delayed up to three days.

Next update by June 17, 18:00 PDT.
Jun 12, 17:35 PDT
Update - An enhancement to email policy scanning performance is in development. For many clients, email policy scanning is delayed up to three and a half days.

Next update by June 12, 18:00 PDT.
Jun 10, 15:29 PDT
Update - Email policy scanning was interrupted last night during the planned maintenance window, increasing the delay up to two days for many clients.

We expect to return to normal processing windows over the weekend.

Next update for this issue by June 10, 18:00 PDT.
Jun 5, 14:51 PDT
Monitoring - We continue to monitor email policy scanning performance. Many clients are within expected ranges.

Next update for this issue by June 5, 18:00 PDT.
Jun 3, 17:00 PDT
Update - The email policy scanning delay has significantly decreased to at most one and a half days. We expect to return to normal processing windows shortly..

Next update for this issue by June 3, 18:00 PDT.
May 30, 11:32 PDT
Identified - We have identified an issue that impacted policy scanning of email content over the holiday weekend. While the issue has been resolved, email policy scanning is delayed by up to two days for many clients.

Next update for this issue by 18:00 PDT, May 30
May 28, 17:34 PDT

About This Site

Want to stay in the loop? Click the subscribe button at the top right-hand side of this page to get updates and notifications of status changes sent directly to your email inbox or mobile device.

Archiving Services Degraded Performance
Archiving Platform Operational
Email Archiving Degraded Performance
Bloomberg Archiving Degraded Performance
Social Media Archiving Operational
Mobile Archiving Operational
Web Archiving Operational
Instant Message Archiving Operational
Hosting Services Operational
Exchange Hosting (SmarshMail) Operational
Exchange Hosting (SmarshConnect) Operational
POP / IMAP Hosting Operational
DLP Operational
Spam Filters Operational
Presensoft Operational
Smarsh Central Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 27, 2019

No incidents reported today.

Jun 26, 2019

No incidents reported.

Jun 23, 2019

No incidents reported.

Jun 22, 2019

No incidents reported.

Jun 21, 2019
Resolved - Slack archiving has caught up and we are now processing data within 24 hours.
Jun 21, 15:44 PDT
Update - Slack is continuing to process and our backlog has reduced. Customers should now see messages from 6/17 populating in their archive. If progress continues at this rate, backlog is expected to be fully remediated by the end of the week.

Next Update by June 21st 18:00PDT
Jun 19, 16:28 PDT
Update - With our enhanced performance, we estimate that Slack ingestion and searchability will be current as of June 19.

Next update by June 19, 18:00 PDT.
Jun 14, 17:31 PDT
Update - Slack backlog has decreased significantly and we are investigating changes to enhance the burndown rate. Ingestion delays are resolved for Symphony, Thomson Reuter, and Ice Chat.

Next update by June 14, 18:00 PDT.
Jun 12, 18:07 PDT
Update - As a result of the change applied last week, IM ingestion performance is significantly improved. Symphony, Thomson Reuter, and Ice Chat ingestion is now current. Slack backlog has decreased significantly.

Next update by June 12, 18:00 PDT.
Jun 10, 16:36 PDT
Update - Engineering has applied a change to address IM ingestion performance. We are monitoring performance through the weekend to assess the impact of the change on Slack, Symphony, Thomson Reuters, and Ice Chat.

Next update for this issue by June 10, 18:00 PDT.
Jun 6, 16:59 PDT
Update - Engineering is continuing investigations into ingestion of Slack, Symphony, Thomson Reuter, and Ice Chat as performance is less than anticipated after last week's change.

Next update for this issue by June 6, 18:00 PDT
Jun 5, 17:07 PDT
Monitoring - We are continuing to monitor IM ingestion and processing.

Next update for this issue by June 5, 18:00 PDT.
Jun 3, 17:01 PDT
Update - A change was made this afternoon to address ingestion performance of Slack, Symphony, Thomson Reuters, and Ice Chat. Initial results are positive. We will monitor through the weekend to ensure that the change has the intended impact.

Next update for this issue by June 3, 18:00 PDT.
May 30, 17:27 PDT
Update - Ingestion rates for Slack, Symphony, Thomson Reuters, and Ice Chat were lower than expected over the holiday weekend. Messages for these content types continue to be processed but remain delayed several days within the archive. We are pursuing additional resources to assist in processing the backlog.

Next update for this issue by 18:00 PDT, May 30
May 28, 16:59 PDT
Investigating - We continue to investigate the ingestion delay impacting Slack, Symphony, Thomson Reuters, and Ice Chat. Progress is expected over the holiday weekend.

Next update for this issue will be provided by 6 pm Pacific, 5/28.
May 23, 18:00 PDT
Update - We continue to investigate causes of the ingestion delay impacting Slack, Symphony, Thomson Reuters, and Ice Chat. Ingestion and searchability are delayed  multiple days for these content types.

Next update for this issue will be provided by 5 pm, 5/23.
May 21, 17:08 PDT
Monitoring - We are deploying infrastructure solutions to address the issue causing ingestion and searchability delays specific to MS Teams, Slack, Ice Chat, Thomson Reuters Messenger, Symphony, Pivot, and Mobileguard. We will monitor for 24 hours post deployment to ensure remediation.

Next update for this issue will be provided by 5 pm Pacific, 5/17.
May 16, 17:05 PDT
Investigating - We have identified an issue causing delays for MS Teams, Slack, Ice Chat, Thomson Reuters Messenger, Symphony, Pivot, and Mobileguard. We are receiving data for these content types, but ingestion and the ability to search for this content in the Platform is delayed for several days.


Next update for this issue will be provided by 5 pm Pacific, 5/16.
May 15, 14:41 PDT
Jun 20, 2019
Completed - The scheduled maintenance has been completed.
Jun 20, 19:46 PDT
Scheduled - We will be undergoing maintenance starting at 6pm PST. We estimate completion at 12am PST. During this time the Archiving Platform will be unavailable.
Jun 20, 06:12 PDT
Completed - The scheduled maintenance has been completed.
Jun 20, 05:25 PDT
Scheduled - We will be undergoing maintenance starting at 6pm PST. We estimate completion at 12am PST. During this time the Archiving Platform will be unavailable.
Jun 19, 11:13 PDT
Jun 19, 2019
Resolved - This issue has been resolved. The email content indexing backlog is now caught up. Indexing for new email changes are updating within normally expected time periods.
Jun 19, 15:44 PDT
Monitoring - We have identified an issue with email content indexing and are currently monitoring its resolution. Users may experience a delay in changes being applied to messages in relative real time. We are currently projecting to be caught up over night.

Next update: June 19 12:00pm PDT
Jun 18, 17:40 PDT
Jun 18, 2019
Resolved - RESOLVED - Platform is back up and functioning. Sorry for any short term inconvenience and we appreciate your understanding.
Jun 18, 09:43 PDT
Update - We are continuing to investigate this issue.
Jun 18, 09:29 PDT
Investigating - The Platform is temporarily unavailable. During this time all of your data will be securely saved and protected, but access to the platform and search functionality is temporary unavailable.

Thank you,

Smarsh Support Team
Jun 18, 09:29 PDT
Jun 17, 2019
Resolved - We have fixed all known issues for Email Ingestion. Email processing is now back to normal.
Jun 17, 15:52 PDT
Investigating - We are currently investigating an issue delaying email ingestion into the Professional Archive.

Next update by June 17, 18:00 PDT.
Jun 14, 11:02 PDT
Jun 16, 2019

No incidents reported.

Jun 15, 2019

No incidents reported.

Jun 14, 2019
Resolved - We have fixed all known issues for MS Teams ingestion. We are now ingesting as messages come in.
Jun 14, 17:16 PDT
Investigating - We are investigating an issue impacting some clients who continue to experience a significant delay in MS Teams ingestion overall and/or Direct Messages specifically.

Next update by June 14, 18:00 PDT.
Jun 12, 17:58 PDT
Update - As a result of the change applied last week, MS Teams ingestion is now current for many clients. We have identified certain clients who are still experiencing a significant delay and working towards resolution.

Next update by June 12, 18:00 PDT.
Jun 10, 16:38 PDT
Update - Engineering has applied a change to address IM ingestion performance. We are monitoring performance through the weekend to assess the impact of the change on MS Teams ingestion.

Next update for this issue by June 10, 18:00 PDT.
Jun 6, 16:58 PDT
Update - Engineering is continuing investigations into MS Teams ingestion delays as progress is less than anticipated.

Next update for this issue by June 6, 18:00 PDT
Jun 5, 17:06 PDT
Update - MS Teams ingestion backlog continues to decrease.

Next update for this issue by June 5, 18:00 PDT.
Jun 3, 17:02 PDT
Update - MS Teams ingestion backlog continues to decrease.

Next update for this issue by June 3, 18:00 PDT.
May 31, 16:27 PDT
Update - We continue to burn down the MS Teams ingestion backlog. Please note that clients may see newer messages before older content, based on processing order.

Next update for this issue by 18:00 PDT, May 31.
May 29, 17:14 PDT
Update - MS Teams ingestion rates were lower than expected over the holiday weekend. In addition, many messages are awaiting indexing, which impacts searchability in the platform.

Next update for this issue by 18:00 PDT, May 29
May 28, 16:45 PDT
Update - The enhancements to the MS Teams archiving application continues to run successfully in production, burning down the ingestion backlog. We will continue to monitor through the weekend.

Next update for this issue by 6 pm PDT, 5/28.
May 24, 15:53 PDT
Update - We have released a major performance enhancement to our MS Teams archiving application on Friday 5/17 and are seeing large ingestion performance gains. We will continue to monitor as the backlog is burned down. 

Next update for this issue will be provided by 5 pm, 5/24.
May 21, 09:36 PDT
Update - Engineering continues to solve  for MS Teams ingestion delays impacting some clients.

Next update for this issue will be provided by 5 pm Pacific, 5/20.
May 15, 17:58 PDT
Update - Engineering continues to solve for MS Teams ingestion delays impacting some clients.

 
Next update for this issue will be provided by 5 pm Pacific, 5/15.
May 13, 14:31 PDT
Update - Some clients are experiencing multi-day lags in MS Teams ingestion, impacting searchability and policy scanning. Engineering is actively working to increase the ingestion performance of MS Teams.

Next update for this issue will be provided by 5 pm Pacific, 5/13.
May 8, 13:51 PDT
Monitoring - We are ingesting MS Teams and are continuing to monitor performance.

Next update will be provided by 5 pm Pacific, 5/10.
May 7, 16:25 PDT
Update - Ingestion of MS Teams is delayed, impacting searchability.  Ingestion of Slack is now current, as is searchability and policy scanning.

Next update for MS Teams ingestion will be provided by 5 pm Pacific, 5/7.
May 6, 15:33 PDT
Update - We continue to investigate instances of delayed ingestion and searchability, specifically for Slack and MS Teams content.  The next update for this issue will be provided by 5 pm Pacific, 5/3.
Apr 30, 16:32 PDT
Investigating - We are investigating instances of delayed ingestion and searchability, specifically for Slack and MS Teams content. The next update for this issue will be provided by 5pm Pacific 4/30.
Apr 29, 14:10 PDT
Monitoring - Monitoring - We have identified and have corrected an issue causing ingestion delays for all IM content. We are now monitoring the backlog as we move to expected ingestion times. Please note that some users may see a delay in IM Search & Policy scanning until we catch up on the backlog. There is no data loss.
Apr 17, 10:37 PDT
Resolved - Exports from the Professional Archive are completing within normal timeframes based on size, content type, and format.
Jun 14, 16:48 PDT
Update - We have made optimizations to the export process and are seeing improved times to completion. Please report exports processing longer than 24 hours to Smarsh Technical Support.

Next update by June 14, 18:00 PDT.
Jun 13, 17:46 PDT
Update - We continue our efforts to identify the cause of exports taking longer than normal to complete.

Next update by June 13, 18:00 PDT.
Jun 12, 17:25 PDT
Update - We are continuing our investigation of some exports taking longer than normal to complete. Please open a case with Smarsh Technical Support to report exports processing longer than 24 hours.

Next update by June 12, 18:00 PDT.
Jun 11, 17:49 PDT
Investigating - We are investigating an issue causing some exports to appear processing for longer than 24 hours. Please report any such instances to Smarsh Technical Support at 1-866-SMARSH-1 or open a case through Smarsh Central.

Next update by June 11, 18:00 PDT.
Jun 10, 16:57 PDT
Update - We have made further optimizations to the export process and are now seeing increased throughput for exports. We are monitoring closely to ensure full resolution.

Next update for this issue by June 10, 18:00 PDT
Jun 7, 09:30 PDT
Monitoring - The issue has been identified and a fix applied. We are monitoring closely to ensure full resolution.

Next update for this issue by June 7, 18:00 PDT.
Jun 6, 16:40 PDT
Investigating - We are investigating an issue causing exports to appear as pending for extended periods of time.

Next update for this issue today by 17:00 PDT.
Jun 6, 14:51 PDT