Seesaw incident

Messaging: Issue with real-time updates

Resolved after 16 hours 9 minutes, affecting Seesaw, on February 22, 2024.

investigating Feb 22, 2024, 05:02 PM UTC

We've confirmed that the issue has resolved itself. An upstream provider had an outage from 2/21/24 13:57 PT to 2/21/24 19:01 PT. Our logs show normal activity resumed by 19:15 PT, and we've made an improvement to prevent this issue from occurring if the provider were to have an issue again.

Started
Feb 22, 2024, 02:32 AM UTC
Resolved
Feb 22, 2024, 06:41 PM UTC
Duration
16h 9m
Detected by Pingoru
Feb 22, 2024, 02:32 AM UTC

Affected components

Seesaw

Update timeline

  1. investigating Feb 22, 2024, 02:32 AM UTC

    A small set of users are likely not receiving real-time updates in Messaging. The team is looking into this, and the current workaround is to refresh to receive new messages. Thank you for your patience.

  2. investigating Feb 22, 2024, 05:01 PM UTC

    We've confirmed that the issue has resolved itself. An upstream provider had an outage from 2/21/24 13:57 PT to 2/21/24 19:01 PT. Our logs show normal activity resumed by 19:15 PT, and we've made an improvement to prevent this issue from occurring if the provider were to have an issue again.

  3. investigating Feb 22, 2024, 05:02 PM UTC

    We've confirmed that the issue has resolved itself. An upstream provider had an outage from 2/21/24 13:57 PT to 2/21/24 19:01 PT. Our logs show normal activity resumed by 19:15 PT, and we've made an improvement to prevent this issue from occurring if the provider were to have an issue again.

  4. resolved Feb 22, 2024, 06:41 PM UTC

    This incident has been resolved.

Your product runs on more than Seesaw

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →