Geekbot incident

Private channels not recognized

Minor Resolved View vendor source →

Geekbot experienced a minor incident on March 19, 2020 affecting API, lasting 6h 39m. The incident has been resolved; the full update timeline is below.

Started
Mar 19, 2020, 03:26 PM UTC
Resolved
Mar 19, 2020, 10:05 PM UTC
Duration
6h 39m
Detected by Pingoru
Mar 19, 2020, 03:26 PM UTC

Affected components

API

Update timeline

  1. investigating Mar 19, 2020, 03:26 PM UTC

    While setting up a new standup, private channels are not showing up in the standup configuration as expected. We're actively investigating, and we're sorry for the trouble.

  2. investigating Mar 19, 2020, 03:28 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 19, 2020, 06:49 PM UTC

    Our investigation continues, we will be back with more information very shortly. Thank you for bearing with us

  4. identified Mar 19, 2020, 09:48 PM UTC

    We've identified the cause of the issue and made some changes to get things back to normal as soon as possible.

  5. monitoring Mar 19, 2020, 09:50 PM UTC

    We have pushed out a fix and we are monitoring the situation to make sure everything is running smoothly. We'll provide another update once we confirm that the issue is fully resolved.

  6. resolved Mar 19, 2020, 10:05 PM UTC

    We have fully resolved the issues with private channels not being identified in the standup configuration. Apologies again for the disruption to your day. Thank you for being patient with us.