Time: April 22, 2020, 1:26 a.m.

Status: Resolved

Update: Reminders scheduled for the downtime between April 11 and today have now been pushed, meaning this incident is now fully resolved. Please do not hesitate to let us know if there are any questions ([email protected]) and have a nice remainder of the week.

Time: April 21, 2020, 10:15 p.m.

Status: Monitoring

Update: All Send Later emails scheduled to send during the downtime (those in which the underlying Draft was not deleted during the downtime) have now been sent. Reminders scheduled for the downtime will now be processed, with the expectation that all such Reminders will be sent by EOD tomorrow (April 22nd). This is the lone remaining item and all other functionality is now fully available. If there are any questions, please do not hesitate to reach out to us at [email protected].

Time: April 21, 2020, 9:59 p.m.

Status: Monitoring

Update: Reminders and Send Later emails may now be scheduled again for users on the latest version of the Yesware extension- extensions will update automatically over the next several hours, but if you would like to manually update your extension at this time you may do so by navigating to chrome://extensions/ > selecting "Developer Mode" (in the upper-right hand corner) > selecting the "Update" button > relaunching GMail. Send Later emails scheduled during the downtime are now being processed and these emails will be sent over the next few hours (those in which the underlying Draft has not been deleted- as mentioned previously, if the underlying Draft was deleted the Send Later email will not be sent). Reminders from the downtime will be processed after the completion of the Send Later emails, with the expectation that all Reminders from the downtime will be sent by EOD tomorrow (April 22nd). Once again, we apologize for the inconvenience this issue caused. If there are any questions and/or comments, please do not hesitate to reach out to us at [email protected].

Time: April 20, 2020, 5:10 p.m.

Status: Identified

Update: Yesware is finalizing a fix and estimates that the issue will be resolved tomorrow (April 21st, 2020). Once the fix has been implemented, all queued Reminders and Send Later emails from the down period will send. To that end, if there are any Send Later emails that you would not like to be sent once the issue has been resolved, please navigate to your Drafts folder and delete the email at this time (doing so will prevent Yesware from being able to find, and send, the email later). If there are any questions, please do not hesitate to reach out to us at [email protected].

Time: April 17, 2020, 9:09 p.m.

Status: Identified

Update: Yesware continues to work on implementing the fix for this issue, and expects to be live with said fix by mid-week next week. Please do not hesitate to let us know ([email protected]) if there are any questions in the meantime.

Time: April 14, 2020, 7:49 p.m.

Status: Identified

Update: Yesware has identified the cause of the Reminders and Send Later issue, and is working on a fix. We will provide an update when that fix has been implemented and ask that you not hesitate to reach out to us at [email protected] if there are any questions in the meantime. Once again, our apologies for the inconvenience.

Time: April 13, 2020, 10 p.m.

Status: Investigating

Update: Yesware is investigating reports of missed Reminders and failed Send Later emails starting Saturday, April 11th. This is being treated as a top priority and updates will be provided on this page as they become available. We apologize for the inconvenience and ask that you not hesitate to reach out to us at [email protected] if there are any questions.

Time: Jan. 7, 2020, 12:24 a.m.

Status: Resolved

Update: GMail systems have been restored ahead of schedule, meaning all Yesware users on O365 and GMail are now fully operational, with all functionality available and all Tracking events and CRM Sync events from the period of disruption caught-up. This incident is now resolved. We apologize for the convenience today's disruption caused- if there are any questions and/or if there is anything we may do to be of assistance, please don't hesitate to reach out to [email protected].

Time: Jan. 6, 2020, 11:19 p.m.

Status: Monitoring

Update: All Yesware users on O365 are now fully operational, meaning all functionality is available and all Tracking events and CRM Sync events from the period of disruption have been restored. Yesware users on GMail are in the process of being restored, meaning functionality is currently available, but that Tracking events and CRM sync events from the period of disruption are being restored. We will continue to monitor as these systems restore, with the expectation that all systems will be caught-up by the start of business tomorrow for all users in Europe, North America, and South America. Today's disruption was caused by a database indexing operation that caused one of our data ingest pipelines to fall behind. We apologize for the inconvenience and ask that you not hesitate to reach out to [email protected] if there are any questions and/or if there is anything we may do to be of assistance.

Time: Jan. 6, 2020, 6:57 p.m.

Status: Identified

Update: The underlying issue has been identified and a fix implemented. Yesware functionality should now be available, with reply checking and CRM sync delayed as our systems work to fully restore. Please note that no data from the down period will be lost.

Time: Jan. 6, 2020, 6:30 p.m.

Status: Identified

Update: The underlying issue has been identified and a fix implemented. Yesware functionality should now be available, with reply checking and CRM sync delayed as our systems work to fully restore. Please note that no data from the down period will be lost.

Time: Jan. 6, 2020, 6:30 p.m.

Status: Identified

Update: The underlying issue has been identified and a fix implemented. Yesware functionality should now be available, with reply checking and CRM sync delayed as our systems work to fully restore. Please note that no data from the down period will be lost.

Time: Jan. 6, 2020, 6:07 p.m.

Status: Investigating

Update: We are currently investigating reports of Yesware being down for a number of users. The issue is being treated with the highest priority and updates will follow. We apologize for the inconvenience.

Time: Jan. 7, 2020, 12:24 a.m.

Status: Resolved

Update: GMail systems have been restored ahead of schedule, meaning all Yesware users on O365 and GMail are now fully operational, with all functionality available and all Tracking events and CRM Sync events from the period of disruption caught-up. This incident is now resolved. We apologize for the convenience today's disruption caused- if there are any questions and/or if there is anything we may do to be of assistance, please don't hesitate to reach out to [email protected].

Time: Jan. 6, 2020, 11:19 p.m.

Status: Monitoring

Update: All Yesware users on O365 are now fully operational, meaning all functionality is available and all Tracking events and CRM Sync events from the period of disruption have been restored. Yesware users on GMail are in the process of being restored, meaning functionality is currently available, but that Tracking events and CRM sync events from the period of disruption are being restored. We will continue to monitor as these systems restore, with the expectation that all systems will be caught-up by the start of business tomorrow for all users in Europe, North America, and South America. Today's disruption was caused by a database indexing operation that caused one of our data ingest pipelines to fall behind. We apologize for the inconvenience and ask that you not hesitate to reach out to [email protected] if there are any questions and/or if there is anything we may do to be of assistance.

Time: Jan. 6, 2020, 6:57 p.m.

Status: Identified

Update: The underlying issue has been identified and a fix implemented. Yesware functionality should now be available, with reply checking and CRM sync delayed as our systems work to fully restore. Please note that no data from the down period will be lost.

Time: Jan. 6, 2020, 6:30 p.m.

Status: Identified

Update: The underlying issue has been identified and a fix implemented. Yesware functionality should now be available, with reply checking and CRM sync delayed as our systems work to fully restore. Please note that no data from the down period will be lost.

Time: Jan. 6, 2020, 6:30 p.m.

Status: Identified

Update: The underlying issue has been identified and a fix implemented. Yesware functionality should now be available, with reply checking and CRM sync delayed as our systems work to fully restore. Please note that no data from the down period will be lost.

Time: Jan. 6, 2020, 6:07 p.m.

Status: Investigating

Update: We are currently investigating reports of Yesware being down for a number of users. The issue is being treated with the highest priority and updates will follow. We apologize for the inconvenience.

Time: Sept. 5, 2019, 7:40 p.m.

Status: Resolved

Update: All systems are now functioning as normal. Once again, note that no activity or data was lost during the downtime. If there are any questions or concerns, please do not hesitate to reach out to [email protected]. Otherwise note that this issue is resolved. Yesware apologizes for the inconvenience this may have caused any users today.

Time: Sept. 5, 2019, 7:40 p.m.

Status: Resolved

Update: All systems are now functioning as normal. Once again, note that no activity or data was lost during the downtime. If there are any questions or concerns, please do not hesitate to reach out to [email protected]. Otherwise note that this issue is resolved. Yesware apologizes for the inconvenience this may have caused any users today.

Time: Sept. 5, 2019, 5:30 p.m.

Status: Identified

Update: The cause of the issue has been identified and fixed, and systems are currently catching-up. Impacted users will start to see their Campaigns sending, and messages sent with Tracking during the outage will start seeing engagement again. Note that no activity or data was lost during the downtime.

Time: Sept. 5, 2019, 5:30 p.m.

Status: Identified

Update: The cause of the issue has been identified and fixed, and systems are currently catching-up. Impacted users will start to see their Campaigns sending, and messages sent with Tracking during the outage will start seeing engagement again. Note that no activity or data was lost during the downtime.

Time: Sept. 5, 2019, 3:40 p.m.

Status: Investigating

Update: We are currently investigating reports of the Yesware Activity Feed, as well as Campaigns, being unresponsive. We will continue to post updates as they are available.

Time: Sept. 5, 2019, 3:40 p.m.

Status: Investigating

Update: We are currently investigating reports of the Yesware Activity Feed, as well as Campaigns, being unresponsive. We will continue to post updates as they are available.

Time: May 11, 2019, 1:34 p.m.

Status: Resolved

Update: All automated emails have been sent and this incident is now considered resolved. We apologize for the inconvenience and ask that you not hesitate to reach out to [email protected] if there are any questions.

Time: May 11, 2019, 12:45 a.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: May 10, 2019, 9:26 p.m.

Status: Identified

Update: All automated emails from Campaigns and Mail Merge initiated yesterday have been sent, and almost all users should no longer see delays for those sent today. The small percentage of users still seeing delays should expect for these delays to cease by the end of the day. If there are any questions, please do not hesitate to reach out to [email protected].

Time: May 10, 2019, 4:06 p.m.

Status: Identified

Update: Automated emails from Campaigns and Mail Merge are now being sent. Automated emails initiated yesterday will be the first to send, followed by those initiated today. There will be a slight delay as the backlog is processed, but all automated emails sent both yesterday and today are expected to be sent today. If there are any questions, please do not hesitate to reach out to [email protected].

Time: May 10, 2019, 1:46 p.m.

Status: Identified

Update: Automated emails from Campaigns and Mail Merge are slated to start sending shortly, starting with those that were initiated during yesterday's downtime. An update will be provided when these emails begin going out.

Time: May 9, 2019, 9:11 p.m.

Status: Identified

Update: A fix has been pushed. Specifically: - The issue preventing opens from being tracked on emails sent today has been resolved for all users. This fix is retroactive, meaning users will now see opens for emails sent and opened today during the downtime. - The issue preventing emails from being synced to Salesforce on emails sent today has been resolved for all users. This fix is retroactive, meaning emails sent today should now be synced in Salesforce. - There will be a delay in sending automated emails from Campaigns and Mail Merges slated to send during today's downtime. These automated emails will be processed starting tomorrow morning (5/10). Once again, Yesware apologizes for the inconvenience and asks that you not hesitate to reach out to [email protected] if there are any questions.

Time: May 9, 2019, 7:05 p.m.

Status: Identified

Update: Yesware continues to work towards resolution. Note that automated emails are currently not being sent through Campaigns and Mail Merge, but will be sent once the issue is resolved.

Time: May 9, 2019, 5:39 p.m.

Status: Identified

Update: Yesware operations has detected an issue preventing the display of open events and the automatic syncing of send and reply events to Salesforce (for emails sent today). Yesware Engineering is currently working on a resolution and expects one to be deployed within the next few hours. This resolution is expected to work retroactively for missed events during the downtime. Yesware will continue to provide updates as they come available. We apologize for the inconvenience and ask that you not hesitate to reach out to us at [email protected] with any questions or concerns.