Histórico de interrupções do Geekbot

1. 27 Here 2026 da 14:07 UTCresolved

   Em 21 de outubro de 2026, o projeto PHP lançou correções para duas vulnerabilidades críticas, conhecidas como PHP2Shell (CVE-2026-109618 e CVE-2026-109619). A nossa equipa sabia que a actualização estava a chegar e estava pronta. Assim que a correção foi publicada, nós a aplicamos em todos os nossos sistemas. Todos os sistemas Geekbots estão agora totalmente remendados. Não encontramos nenhuma evidência de que nenhum dos nossos sistemas ou dados do cliente foram comprometidos. Você não precisa fazer nada. Se tiver dúvidas, contacte-nos em [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Cʼhwevrer 2025 da 15:59 UTCinvestigating

   Slack has announced that workspaces are experiencing connectivity issues that have affected our service. Their team is on the case and hopefully they will have a quick turnaround. You can follow updates here: https://slack-status.com/2025-02/1b757d1d0f444c34

2. 26 Cʼhwevrer 2025 da 16:55 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 27 Cʼhwevrer 2025 da 12:35 UTCresolved

   Slack has communicated that they've resolved all issues and things should be working as expected. Thank you for your patience while Slack worked to resolve this issue.

1. 11 Meurzh 2023 da 12:11 UTCinvestigating

   The Geekbot team will be working on service maintenance. In the next hour you may experience minor outages during the process. We will keep you posted on our progress. Thank you for your understanding.

2. 11 Meurzh 2023 da 12:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 11 Meurzh 2023 da 15:50 UTCresolved

   Good news! Service maintenance has been completed and things should be running as expected but feel free to contact us at [email protected] if you experience any lag moving forward.

1. 17 Cʼhwevrer 2023 da 17:31 UTCinvestigating

   We've been experiencing latency and bot lag issues in the past few hour. Our engineers have found the culprit and are working to resolve this at the soonest. Please bear with us a bit longer. 🙏

2. 17 Cʼhwevrer 2023 da 17:52 UTCinvestigating

   Our engineers have pushed a fix and things are looking stable for now. We will keep monitoring the bot's behavior to ensure stability. Thank you for your patience and understanding!

3. 20 Cʼhwevrer 2023 da 11:39 UTCresolved

   We are seeing signs that the fix that was implemented has improved all latencies related to the bot's responsivity. Our engineers will keep monitoring our logs to ensure that this will not happen again. Thank you for your patience and understanding!

1. 17 Here 2022 da 10:50 UTCinvestigating

   We've been experiencing latency and bot lag issues. Our engineers are working hard to pinpoint the culprit and push a fix in place. Please bear with us a bit longer. 🙏

2. 17 Here 2022 da 11:46 UTCmonitoring

   Our engineers have pushed a fix and things are looking stable for now. We will keep monitoring the bot's behavior to ensure stability. Thank you for your patience and understanding!

3. 17 Here 2022 da 15:44 UTCresolved

   We are seeing signs that the fix that was implemented has improved all latencies related to the bot's responsivity. Our engineers will keep monitoring our logs to ensure that this will not happen again. Thank you for your patience and understanding!

1. 7 Mezheven 2022 da 19:15 UTCidentified

   We've been experiencing latency and bot lag issues in the past hour. Our engineers have found the culprit and are working to resolve this at the soonest. Please bear with us a bit longer. 🙏

2. 7 Mezheven 2022 da 21:23 UTCmonitoring

   Things should be back to normal and the bot should be responsive as expected once again. Our engineers will keep monitoring the bot's behavior to ensure this will not happen again. Thank you for your patience and understanding!

3. 7 Mezheven 2022 da 21:23 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7 Mezheven 2022 da 22:27 UTCresolved

   We deployed a fix, resolving the issue for all affected customers. We apologize for any disruption this has caused and thank you for your continued patience.

1. 5 Du 2021 da 20:23 UTCinvestigating

   We've been experiencing latency and bot lag issues in the past hour. Our engineers have found the culprit and are working to resolve this at the soonest. Please bear with us a bit longer. 🙏

2. 6 Du 2021 da 00:06 UTCresolved

   Looks like we're out of the woods and things should be working as expected from now on. If you're still experiencing issues please let us know at [email protected]. Thank you for your patience and understanding!

1. 30 Gwengolo 2021 da 16:44 UTCinvestigating

   We’re currently investigating this connection issue and we’ll keep you posted as soon as we have more information. Thanks for your patience and we apologize for the disruption.

2. 30 Gwengolo 2021 da 17:13 UTCidentified

   Our engineers have identified the issue and are working hard to resolve it. We’ll keep you posted as soon as we have more information. Thanks for your patience and understanding.

3. 30 Gwengolo 2021 da 17:59 UTCmonitoring

   We deployed a fix for the connection issue, resolving the issue for all affected customers. We will keep monitoring our logs to ensure this does not happen again. Thank you for your patience and understanding!

4. 30 Gwengolo 2021 da 18:46 UTCresolved

   On September 30, 2021, a small group of customers experienced issues where the bot was not visible in broadcast channels. We deployed a fix, resolving the issue for all affected customers. We apologize for any disruption this has caused and thank you for your continued patience.

1. 22 Here 2020 da 12:22 UTCidentified

   We are currently deploying a new release and a few teams may be affected by this deployment (bot not responsive, notifications not sent). It should be working as expected very soon - please bear with us as our engineers do their magic to bring the service back up and running.

2. 22 Here 2020 da 12:22 UTCidentified

   We are continuing to work on a fix for this issue.

3. 22 Here 2020 da 13:37 UTCresolved

   Things should be back to normal and the bot should be responsive as expected once again. Our engineers will keep monitoring the bot's behavior to ensure this will not happen again. Thank you for your patience and understanding!

1. 28 Eost 2020 da 10:31 UTCinvestigating

   Some customers may be experiencing issues while trying to access the dashboard. We are very sorry for the disruption. We are investigating, and we'll be back with an update as soon as we have more information. Thank you for bearing with us.

2. 28 Eost 2020 da 14:55 UTCidentified

   Our engineer team seems to have identified the culprit and they're working to hard resolve this issue. We’ll be back with another update within the day. We appreciate your patience.

3. 28 Eost 2020 da 15:31 UTCmonitoring

   Customers should no longer be having trouble accessing the dashboard and managing their standups. For the time being our engineers are monitoring our logs to ensure this does not happen again. Please reach out to us at [email protected] if you have any further hassles. We’re sorry for the disruption this has caused.

4. 28 Eost 2020 da 16:45 UTCresolved

   Great news! Geekbot's dashboard is fully operational again after we fixed the problem causing connection trouble. Thanks for bearing with us and sorry about the hassle.

1. 19 Meurzh 2020 da 15:26 UTCinvestigating

   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. 19 Meurzh 2020 da 15:28 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 Meurzh 2020 da 18:49 UTCinvestigating

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

4. 19 Meurzh 2020 da 21:48 UTCidentified

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

5. 19 Meurzh 2020 da 21:50 UTCmonitoring

   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. 19 Meurzh 2020 da 22:05 UTCresolved

   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.

1. 9 Kerzu 2019 da 19:25 UTCinvestigating

   We're looking into reports of performance and lag issues for some customers. We'll keep you in the loop as we continue to investigate this further.

2. 9 Kerzu 2019 da 19:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 Kerzu 2019 da 09:10 UTCidentified

   For those affected, we're happy to report that the issue has been identified and a fix has been implemented.

4. 10 Kerzu 2019 da 12:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results. Please bear with us a bit longer.

5. 11 Kerzu 2019 da 19:42 UTCmonitoring

   A new fix is about to deploy, please bear with us a little longer.

6. 12 Kerzu 2019 da 13:25 UTCmonitoring

   We are happy to say that we are seeing signs of improvement. For those affected, we apologize for keeping you away from your work during this time.

7. 13 Kerzu 2019 da 13:32 UTCresolved

   Thank you so much for your patience as we worked on this. Looks like we're finally out of the woods after numerous failed attempts to fix the issue. We tracked down that Slack was not sending requests to the correct events URL which affected the bot's responsiveness and caused performance issues. Once we settled this with Slack's support and ensured that requests are sent to the correct events URL we determined that this had resolved the issue for all customers.

1. 27 Du 2019 da 08:58 UTCinvestigating

   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. 27 Du 2019 da 11:26 UTCidentified

   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. 27 Du 2019 da 11:38 UTCmonitoring

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

4. 27 Du 2019 da 11:56 UTCresolved

   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.

1. 30 Here 2019 da 12:39 UTCinvestigating

   Customers may be seeing errors 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. 30 Here 2019 da 13:42 UTCidentified

   We’re still working towards a full resolution, but we're seeing improvements. Our support engineer team has predicted that we will be fully functional in the next couple of hours. We'll report back here once this is completely resolved.

3. 30 Here 2019 da 14:09 UTCresolved

   We’ve rolled out a fix and have confirmed that everything is back to normal and working as expected. If you continue to experience issues, please send a note to [email protected]

1. 29 Gouere 2019 da 15:14 UTCinvestigating

   Slack has announced that some workspaces might be experiencing issues with messages sending and loading. Their team is on the case and hopefully they will have a quick turnaround.

2. 29 Gouere 2019 da 16:32 UTCresolved

   Slack update: We're pleased to report that we have the all clear, and all functionality is now restored. Thanks so much for bearing with us in the meantime.

1. 19 Mezheven 2019 da 13:58 UTCinvestigating

   We're having trouble with the dashboard and landing page not loading. Apologies for the hassle - our team is investigating the problem.

2. 19 Mezheven 2019 da 14:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 Mezheven 2019 da 14:09 UTCmonitoring

   We're seeing some positive signs and people should be able to connect again. However, if you're still having issues, please let us know at [email protected]

4. 19 Mezheven 2019 da 14:15 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 19 Mezheven 2019 da 14:16 UTCresolved

   Things should now be back to normal and fully functional once again. We truly appreciate your patience through this and apologize for any disruption to your day.