Pypestream incident

We are investigating intermittent issues with chats escalating to Web Pype Manager

Minor Resolved View vendor source →

Pypestream experienced a minor incident on January 16, 2020 affecting AgentPro, lasting 41m. The incident has been resolved; the full update timeline is below.

Started
Jan 16, 2020, 04:24 PM UTC
Resolved
Jan 16, 2020, 05:06 PM UTC
Duration
41m
Detected by Pingoru
Jan 16, 2020, 04:24 PM UTC

Affected components

AgentPro

Update timeline

  1. investigating Jan 16, 2020, 04:24 PM UTC

    We are investigating intermittent issues with chats escalating to Web Pype Manager

  2. investigating Jan 16, 2020, 04:24 PM UTC

    We are continuing to investigate this issue.

  3. identified Jan 16, 2020, 04:29 PM UTC

    We identified one of our WPM containers was stuck in an unhealthy position. We are in the process restarting the unhealthy node and recover chats.

  4. monitoring Jan 16, 2020, 04:35 PM UTC

    Systems should all be up and running again we are monitoring a few chats that where routed to the unhealthy node to make sure they restart on the new healthy nodes.

  5. resolved Jan 16, 2020, 05:06 PM UTC

    As of now all systems are operational please open a ticket if you experience issues.