Salesloft Dialer Disruption & Platform Slowness

Update timeline

1. monitoring Oct 21, 2025, 10:48 AM UTC

   Oct 21, 06:48 EDT Resolved - This incident is now considered resolved. Thank you for your patience and understanding throughout. Oct 20, 09:39 EDT Update - The Salesloft Dialer is still recovering from this morning's incident with AWS (Amazon Web Services). Salesloft users may still experience intermittent issues with the Dialer while our provider's scaling process continues. We are also currently seeing platform performance issues and slowness in other areas of Salesloft, which is related to the ongoing AWS incident. As AWS systems continue to recover, we anticipate that overall platform performance will improve alongside it. We will continue to monitor the situation and provide updates accordingly. Oct 20, 07:32 EDT Monitoring - Our provider, Twilio, has confirmed that they are starting to see partial recovery across their platform following the widespread AWS incident. They are now focused on scaling systems to manage the influx of traffic. As a result, Salesloft users may experience intermittent issues with the Salesloft Dialer while this scaling process continues. We will continue to monitor the recovery closely and will provide our next update once we have confirmation that everything has returned to normal. Thank you for your continued patience in this matter. Oct 20, 05:58 EDT Identified - We've confirmed that the service disruption impacting our dialer is due to a major, ongoing incident within the AWS (Amazon Web Services) infrastructure that is directly impacting our underlying dialer provider, Twilio. This is an extensive outage that's currently affecting numerous services globally. Twilio's engineering teams are actively implementing mitigation and restoration strategies alongside AWS. We are monitoring the situation closely and will continue to share updates here. You can also follow our provider's status page for more details: https://status.twilio.com/ Our sincere apologies for the delayed status update as our status page provider was also temporarily affected by this same incident, which prevented us from posting sooner.