Tuple incident

Presence Signaling Service Issues

Minor Resolved View vendor source →

Tuple experienced a minor incident on January 25, 2023 affecting API, lasting 1h 58m. The incident has been resolved; the full update timeline is below.

Started
Jan 25, 2023, 05:01 PM UTC
Resolved
Jan 25, 2023, 06:59 PM UTC
Duration
1h 58m
Detected by Pingoru
Jan 25, 2023, 05:01 PM UTC

Affected components

API

Update timeline

  1. identified Jan 25, 2023, 05:01 PM UTC

    We've identified an issue with our signaling server that is preventing the team directory from loading. We're working to resolve the issue now.

  2. identified Jan 25, 2023, 05:13 PM UTC

    We're continuing to work on a fix for this issue.

  3. identified Jan 25, 2023, 05:29 PM UTC

    We've attempted to roll back our signaling service to a previous release, but are still experiencing issues with our load balancer correctly negotiating connections. Our team is still actively working to resolve this issue.

  4. monitoring Jan 25, 2023, 05:36 PM UTC

    Tuple contact directories are loading. We're actively monitoring the service while clients reconnect to ensure that the issue is resolved.

  5. monitoring Jan 25, 2023, 05:48 PM UTC

    We've seen some instances of stale presence data persisting in the directory and are monitoring the relevant queue as it is processed.

  6. resolved Jan 25, 2023, 06:59 PM UTC

    Directory status for all users is up-to-date, and the signaling server has continued to process requests successfully.