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 - The fix for the issue preventing Facebook activations and re-activations is with Quality Engineering.

Next update for this issue will be provided by 6 pm Pacific, May 30.
May 24, 15:55 PDT
Update - Engineering has developed a fix for this issue. The fix is now with Quality Engineering.  

Next update for this issue will be provided by 5 pm Pacific, 5/23.
May 17, 16:37 PDT
Update - Engineering continues to investigate a fix for the issue preventing Facebook activations and re-activations. 

Next update for this issue will be provided by 5 pm Pacific, 5/20.
May 15, 17:55 PDT
Update - Investigation of a fix for the issue preventing Facebook activations and re-activations continues.

 

Next update for this issue will be provided by 5 pm Pacific, 5/15.
May 13, 14:33 PDT
Update - Engineering continues investigation of a fix for the issue preventing Facebook activations and re-activations.
   
Next update for this issue will be provided by 5 pm Pacific, 5/13.
May 9, 17:20 PDT
Identified - An issue has been identified preventing Facebook pages without a sub page from being activated and re-activated. Engineering is engaged in determining a fix.

 
Next update for this issue will be provided by 5 pm Pacific, 5/9.
May 7, 16:02 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
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
Update - Instant Bloomberg policy scanning is within expected ranges for most clients.  We are monitoring performance while continuing to address backlog unique to a limited number of clients.

Next update for this issue will be provided by 5 pm Pacific, 5/28.
May 21, 16:24 PDT
Update - Instant Bloomberg policy scanning backlog continues to decrease for many clients.


Next update for this issue will be provided by 5 pm Pacific, 5/20.
May 13, 14:27 PDT
Update - The policy scanning backlog for Instant Bloomberg continues to decrease for many clients.  


Next update for this issue will be provided by 5 pm Pacific, 5/13.
May 7, 12:35 PDT
Update - Progress continues to further reduce the policy scanning backlog for Instant Bloomberg, benefiting many clients. The next update will be provided by 5 pm Pacific next Monday, 5/6.
Apr 29, 14:11 PDT
Monitoring - We have identified and resolved an Instant Bloomberg scanning issue which has accelerated the daily burn down rate, positively impacting many clients. We will continue to monitor further progress for this processing.
Apr 23, 10:14 PDT
Update - Instant Bloomberg Policy Scanning remains higher than expected for many clients. We continue to work toward increasing the burn down rate.
Mar 15, 10:37 PDT
Identified - Update: Instant Bloomberg Policy Scanning continues to be significantly delayed for many clients. Additional resources are being deployed this week to enhance performance. The results will be known early next week.

Please note this incident is a continuation of the Bloomberg Delays incident, which was inadvertently updated as resolved when the Bloomberg processing portion of that incident was indeed concluded.

We appreciate your continued patience as we address these delays. For more information specific to your account, please contact Smarsh Support via Smarsh Central or 1-866-SMARSH-1.
Mar 6, 11:12 PST

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 Operational
Bloomberg Archiving Degraded Performance
Social Media Archiving Degraded Performance
Mobile Archiving Degraded Performance
Web Archiving Operational
Instant Message Archiving Degraded Performance
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
May 26, 2019

No incidents reported today.

May 25, 2019

No incidents reported.

May 23, 2019
Resolved - This issue has been resolved.
May 23, 17:53 PDT
Update - The database issue causing timeouts/errors in the Platform repeated this morning and was resolved within 30 minutes. Technical efforts are underway to alert and address the issue more quickly, minimizing impact to clients.   

Next update for this issue will be provided by noon Pacific, 5/23.
May 21, 09:31 PDT
Monitoring - The issue causing timeouts/errors in the Platform has been identified and resolved.  We will continue to monitor the remainder of the day.


Next update for this issue will be 5 pm Pacific, 5/20.
May 20, 11:38 PDT
Investigating - We are currently investigating an issue in which multiple functions within the Professional Cloud Platform are timing out, returning errors, or not responding. We are working as quickly as possible to restore full functionality to the Professional Cloud Platform.
May 20, 05:50 PDT
May 22, 2019

No incidents reported.

May 20, 2019
Resolved - Salesforce.com has restored login permissions for the issue affecting full access to Smarsh Central. Customers can now successfully log in to access all features within Smarsh Central, including the Knowledgebase, Case Management, Billing/Invoicing, and Support Rights. Additional details for this incident are available from Salesforce at trust.salesforce.com
May 20, 08:10 PDT
Update - Salesforce.com continues to work on restoring permissions for the issue affecting full access to Smarsh Central. Please note that access to Smarsh products and services is not affected by this Salesforce service interruption. Smarsh Support remains available to our customers via phone and online via the link provided below. We will post an update when full login access to Salesforce.com (used by Smarsh Central) is restored.
May 17, 16:56 PDT
Update - While remediation of this Salesforce.com issue continues, in addition to phone support, customers can also now temporarily open cases through Smarsh Central without logging in at https://central.smarsh.com/s/contactsupport. Please note that logged in users will not be able to access any features at this time. Additional updates to follow as available.
May 17, 09:59 PDT
Identified - We are currently experiencing a technical issue impacting customer access to Smarsh Central and related cases. While we work with the vendor to resolve this, Smarsh Support is available via phone at 866.762.7741. We will provide regular updates here until this issue is resolved.
May 17, 07:37 PDT
May 19, 2019
Resolved - Ingestion of messages for Partner API content is now occurring without delay.
May 19, 17:44 PDT
Monitoring - The ingestion rate of messages for Partner API content, which includes AT&T, Brosix, Captivated, CellTrust, MyRepChat, Presensoft, and Ticker Tocker, has increased as a result of the deployed change. While messages from these content types are actively being processed, and the backlog is decreasing, delays of several days remain for many clients.

Significant burndown of the backlog is expected over the weekend.

Next update for this issue will be provided by 9 am Pacific, 5/20.
May 16, 17:02 PDT
Identified - A change has been deployed to increase the ingestion performance of Partner API content, including AT&T, Brosix, Captivated, CellTrust, MyRepChat, Presensoft, and Ticker Tocker. Messages from these content types are actively being processed but are delayed for several days within the archive.

Next update for this issue will be provided by 5 pm Pacific, 5/20.
May 15, 17:46 PDT
Investigating - We have identified an issue causing delays for IM message ingestion, impacting Partner API content. Content types affected include AT&T, Brosix, Captivated, CellTrust, MyRepChat, Presensoft, and Ticker Tocker.

Messages from these content types are actively being processed, but are delayed for several days within the archive.

Next update for this issue will be provided by 5 pm Pacific, 5/15.
May 14, 17:16 PDT
May 18, 2019

No incidents reported.

May 12, 2019

No incidents reported.