InsideSales incident

issues with calls

Minor Resolved View vendor source →

InsideSales experienced a minor incident on September 28, 2022 affecting Playbooks North America Region, lasting 4d 6h. The incident has been resolved; the full update timeline is below.

Started
Sep 28, 2022, 07:50 AM UTC
Resolved
Oct 02, 2022, 02:27 PM UTC
Duration
4d 6h
Detected by Pingoru
Sep 28, 2022, 07:50 AM UTC

Affected components

Playbooks North America Region

Update timeline

  1. investigating Sep 27, 2022, 03:55 PM UTC

    we are aware that some clients in North America may be experiencing issues with inbound and outbound calling. We are investigating the problem and will continue to post updates through this Status Page.

  2. investigating Sep 27, 2022, 04:29 PM UTC

    We continue to investigate this issue and have identified some contributory elements. We will post further updates here as we mitigate the problems.

  3. identified Sep 27, 2022, 06:00 PM UTC

    We have identified the cause of the issue. We are testing a resolution and will continue to post updates here.

  4. monitoring Sep 27, 2022, 06:57 PM UTC

    We have identified a workaround for the issue being experienced by some North American clients and are in the process of implementing it. Some users may experience slowness as this is rolled out. We will continue to post updates through this forum.

  5. monitoring Sep 27, 2022, 09:21 PM UTC

    We are progressing on the implementation of a permanent fix for the present issue being experienced by some North American customers. Some users may experience slowness as this is rolled out. We will continue to post updates through this forum.

  6. monitoring Sep 28, 2022, 02:16 AM UTC

    The implementation of a permanent fix for the present issue (being experienced by some North American customers) is in progress. Some users may experience slowness as this is rolled out. We will continue to post updates through this forum.

  7. monitoring Sep 28, 2022, 07:50 AM UTC

    A permanent fix has been implemented for the present issue through an updated version of the Chrome extension and we're currently monitoring its behavior. We will post an update through this forum once the issue is confirmed to be resolved.

  8. resolved Oct 02, 2022, 02:27 PM UTC

    Dear Customer, After monitoring our systems, we are now confident to say that this incident is resolved! Thank you for your patience!