Geekbot incident

Bot temporarily not responding as expected.

Critical Resolved View vendor source →

Geekbot experienced a critical incident on November 27, 2019 affecting API, lasting 2h 58m. The incident has been resolved; the full update timeline is below.

Started
Nov 27, 2019, 08:58 AM UTC
Resolved
Nov 27, 2019, 11:56 AM UTC
Duration
2h 58m
Detected by Pingoru
Nov 27, 2019, 08:58 AM UTC

Affected components

API

Update timeline

  1. investigating Nov 27, 2019, 08:58 AM UTC

    Customers may be having trouble when trying to answer their standup questions asked by Geekbot. We are on the case, and will be back with more details as we find the culprit affecting the bot. Apologies for any disruption in the meantime.

  2. identified Nov 27, 2019, 11:26 AM UTC

    We believe we've identified the cause of Geekbot's lack of responsiveness and are working on getting a fix out as soon as possible. We’ll be back with another update soon.

  3. monitoring Nov 27, 2019, 11:38 AM UTC

    We’ve started to see improvements with Geekbot's responsiveness though we’re still monitoring closely. Thanks again for your patience here.

  4. resolved Nov 27, 2019, 11:56 AM UTC

    Good news, we've been given the all-clear! Everyone should be able to interact and respond with Geekbot once more. We're so sorry for disrupting your day. We really appreciate you sticking with us through that.