SalesLoft Status

SalesLoft Status and Maintenance

All Systems Operational

SalesLoft Web Application Operational

3rd Party Integrations Operational

Twilio Web Client Operational

Vidyard Operational

LinkedIn Operational

Nylas Operational

G-Suite Applications Operational

SalesLoft.com Website Operational

SalesLoft Connect (Chrome Extension) Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

System Metrics Month Week Day

Application Response Time

Fetching

Past Incidents

Jun 25, 2019

No incidents reported today.

Jun 24, 2019

Twilio Degraded Service

Resolved - We have confirmed with multiple SalesLoft Teams that the dialer is operational. If you continue to have an issue dialing, please contact our Support Team - https://support.salesloft.com/hc/en-us/requests/new
Jun 24, 09:40 EDT

Monitoring - Twilio has reported seeing a full recovery of the CDN error since 8:30 am EST. Twilio has resolved their status incident (https://status.twilio.com/incidents/tp5z53dx8jrr) as well. We are continuing to monitor with our customer base to confirm systems are operating normally.
Jun 24, 09:14 EDT

Identified - Twilio has posted the following: "Identified - We’re currently working on an issue with intermittent failures accessing Twilio’s JavaScript libraries for Client, Video, and TaskRouter, Programmable Fax media files, and Flex static assets. A portion of global Internet traffic is not able to reach our CDN. We’re working with our CDN partner to resolve the issue. We will provide further updates as they become available." This means that some calls using the Salesloft Dialer may not connect. We will continue to communicate with Twilio about this issue and post updates here as we get them.
Jun 24, 08:27 EDT

Jun 23, 2019

No incidents reported.

Jun 22, 2019

No incidents reported.

Jun 21, 2019

No incidents reported.

Jun 20, 2019

No incidents reported.

Jun 19, 2019

No incidents reported.

Jun 18, 2019

Google Calendar

Resolved - Google has confirmed that they have resolved the Google Calendar issue. All Salesloft features that integrate with calendar are now operational.
Jun 18, 13:28 EDT

Identified - Google expects to resolve the problem affecting a majority of users of Google Calendar at 6/18/19, 1:40 PM EST. Please note that this time frame is an estimate and may change. The affected users are unable to access Google Calendar.

We will continue to monitor the G-Suite dashboard at: https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f for updates.
Jun 18, 12:56 EDT

Update - We have identified another symptom of the Google Calendar issue. Meeting Intelligence bots are unable to join scheduled meetings pulled from user connected Google Calendars. We will continue to monitor the G-Suite dashboard at: https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f for updates.
Jun 18, 12:21 EDT

Investigating - Google is currently investigating reports of an issue with Google Calendar. The affected users are unable to access Google Calendar. Affected SalesLoft customers may experience issues with the SalesLoft / Google Calendar integration including Meeting Scheduling Links and "Insert Availability" features. We will continue to monitor the G-Suite dashboard at: https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f for updates.
Jun 18, 11:24 EDT

Jun 17, 2019

No incidents reported.

Jun 16, 2019

No incidents reported.

Jun 15, 2019

No incidents reported.

Jun 14, 2019

No incidents reported.

Jun 13, 2019

CRM Sync Issues

Resolved - Meeting Intelligence queues are now completely caught up and all systems are stable. This incident has been resolved.
Jun 13, 14:01 EDT

Monitoring - All systems working as expected once again. Currently, the Meeting Intelligence call recording queue is catching up. For now, you may expect a lag in MI recording availability. Engineering will continue to monitor to ensure the queue clears and that services continue to be stable.
Jun 12, 16:10 EDT

Update - The CRM Sync queue and Live Website Tracking are improving. The team is working to resolve the Meeting Intelligence bot issue still. We will update this page as more progress is made.
Jun 12, 15:04 EDT

Update - Progress is being made toward resolution. Items in CRM sync are catching up. Live Website Tracking and Meeting Intelligence bot issues to persist. We will continue to update this site as progress is made.
Jun 12, 13:40 EDT

Identified - We have identified a few other symptoms that appear to be part of this issue. This includes Live Website Tracking is not working properly as well as Meeting Intelligence bots not joining calls.
Engineering has identified the root of the issue and is working toward a resolution.
Jun 12, 12:34 EDT

Investigating - We are currently investigating an issue where some customers using Salesloft sync for CRMs are experiencing errors and/or lag with the connection. We will update this page as we make progress toward solving this issue.
Jun 12, 11:48 EDT

Jun 11, 2019

Meeting Intelligence - Bots Not Joining Meetings

Resolved - Our engineering team has confirmed that the Meeting Intelligence issue is resolved. We will continue to monitor post-call-recordings that are currently processing.
Jun 11, 20:04 EDT

Monitoring - Engineering is continuing to actively resolve the Meeting Intelligence issue. We are seeing a high success rate of Meeting Intelligence joining meetings, however we expect a delay in post-meeting-processing of recorded calls. We will continue to monitor and provide updates when fully resolved.
Jun 11, 18:33 EDT

Identified - The Engineering team has identified the cause and is working to resolve the issue currently. They have been able to increase the amount of times bots join but are still working towards solving the issue completely.
Jun 11, 16:11 EDT

Investigating - We are currently investigating an issue where some customers using Meeting Intelligence are experiencing an issue where bots are not joining calls and thus will not capture meetings. We will update this page as we make progress to solving this issue.
Jun 11, 15:33 EDT