CallPotential incident

Storable CRM Connection Issue

Major Resolved View vendor source →

CallPotential experienced a major incident on November 25, 2025 affecting Contact Center V1 and Storable CRM V1 and 1 more component, lasting 1d 7h. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2025, 02:46 PM UTC
Resolved
Nov 26, 2025, 10:26 PM UTC
Duration
1d 7h
Detected by Pingoru
Nov 25, 2025, 02:46 PM UTC

Affected components

Contact Center V1Storable CRM V1Collections V1Storable CRM V2Contact Center V2Collections V2

Update timeline

  1. investigating Nov 25, 2025, 02:46 PM UTC

    We're aware of a login issue causing connection error messages. This appears to be an issue with our communications provider, Twilio, which has an active incident. Thank you for your patience while we work to resolve this matter

  2. monitoring Nov 25, 2025, 04:05 PM UTC

    The Storable CRM connection issue is showing signs of stability, but we are still monitoring some issues. Thanks for your patience, and we will provide updates as we learn more

  3. monitoring Nov 25, 2025, 05:28 PM UTC

    As part of the recovery phase, we are still experiencing some issues with Twilio that may be affecting certain agents, including outbound calling, queue assignments, and other communication-related functions. We are continuing to investigate and will share additional updates as soon as more information becomes available.

  4. monitoring Nov 25, 2025, 08:57 PM UTC

    As a result of the recent Twilio outage, some users may still experience issues with location-level communications, queue assignments, or agent queue priorities. Our teams are actively identifying any impacted accounts and working to resolve the remaining issues as quickly as possible. Thanks for your patience, and we will provide updates as we learn more

  5. monitoring Nov 26, 2025, 02:17 PM UTC

    Working in conjunction with our communications provider, Twilio, we have identified and addressed all known issues related to the recent outage. Out of an abundance of caution, we will continue to closely monitor the system to ensure no additional impacts surface that require further investigation or resolution. If you notice anything unexpected in the meantime, please reach out to our support team.

  6. resolved Nov 26, 2025, 10:26 PM UTC

    This incident has been resolved.