Histórico de interrupções do Bugcrowd

1. 15 Gwengolo 2026 da 06:07 UTCinvestigating

   Há uma questão na plataforma que afeta o processamento de trabalhos assíncronos, especialmente aqueles relacionados à busca e índices. Estamos a investigar e vamos actualizar em breve.

2. 15 Gwengolo 2026 da 07:05 UTCidentified

   Acreditamos ter identificado a causa (um serviço dependente lento dentro de uma chamada de indexação assíncrona) e estamos no processo de empurrar uma correção.

3. 15 Gwengolo 2026 da 08:21 UTCidentified

   A mudança empurrada não resultou em uma correção, estamos continuando a trabalhar na questão e explorar a correção em mais profundidade.

4. 15 Gwengolo 2026 da 09:14 UTCidentified

   Uma correção foi implantada, e as filas de tarefas assíncronas estão sendo processadas (assim como o backlog).

5. 15 Gwengolo 2026 da 09:15 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

6. 15 Gwengolo 2026 da 10:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Cʼhwevrer 2026 da 05:08 UTCidentified

   We have identified an issue with Hacker / Researcher logins to the platform - currently you may receive a 500 error when logging in. We have applied a fix and are awaiting that to take effect.

2. 26 Cʼhwevrer 2026 da 05:25 UTCmonitoring

   Logins should be functioning as normal, but we will continue monitoring the situation.

3. 26 Cʼhwevrer 2026 da 05:33 UTCresolved

   This incident has been resolved.

1. 22 Here 2025 da 00:14 UTCinvestigating

   There's an ongoing issue in Tracker that is resulting in users experiencing 500 HTTP responses from the server. We have found a potential cause for this and currently working towards fixing this asap.

2. 22 Here 2025 da 00:30 UTCmonitoring

   We have applied a fix for this and currently monitoring the issue.

3. 22 Here 2025 da 00:50 UTCresolved

   This incident has been resolved.

1. 24 Gouere 2025 da 21:33 UTCinvestigating

   We're currently working with a vendor to resolve an issue in our authentication processes, at the moment new users, users who haven't haven't logged in for awhile, and users who have changed their password will be unable to login to the platform.

2. 25 Gouere 2025 da 01:28 UTCmonitoring

   We've implemented a remediation and are now recovering.

3. 25 Gouere 2025 da 02:15 UTCresolved

   This incident has been resolved.

1. 10 Ebrel 2025 da 18:45 UTCidentified

   We've identified another issue that is preventing us from sending platform emails and are working with our vendor to get it resolved but there is no ETA currently.

2. 11 Ebrel 2025 da 06:50 UTCresolved

   Email sending from the platform is functional again.

1. 9 Ebrel 2025 da 01:18 UTCidentified

   We've identified an issue that is preventing us from sending platform emails (e.g. program updates, password resets, etc). We are working on a fix but there is no ETA currently.

2. 9 Ebrel 2025 da 05:20 UTCresolved

   Email sending from the platform is functional again.

1. 14 Du 2024 da 03:02 UTCidentified

   An issue with request rate-limiting is/was preventing POST requests from competing correctly. A fix is being deployed.

2. 14 Du 2024 da 03:21 UTCresolved

   This incident has been resolved.

1. 11 Gwengolo 2024 da 01:24 UTCidentified

   A dependency upgrade has caused unexpected errors in our production environment. The team is reverting the code change and we expect the error to be resolved in the next 20 minutes.

2. 11 Gwengolo 2024 da 01:51 UTCresolved

   This incident has been resolved.

1. 8 Eost 2024 da 01:24 UTCinvestigating

   Currently the tracker portal, researcher portal and even the marketing site is down. We are investigating the issue. We will keep you posted on the progress.

2. 8 Eost 2024 da 01:37 UTCresolved

   We have identified the problem and applied a fix for the issue. The services are now back up and we are currently monitoring the platform.

1. 4 Gouere 2024 da 10:20 UTCidentified

   Monitoring has alerted us to an issue with incoming webhook processing. The issue with the backend service has been identified and we are taking steps to remediate it, but while this is occurring there will be delays in inbound webhook processing.

2. 4 Gouere 2024 da 11:21 UTCmonitoring

   The backend service that processes inbound webhooks has recovered, and is processing the backlog of webhook events.

3. 4 Gouere 2024 da 11:28 UTCresolved

   Backlog processing has completed, systems have returned to normal.

1. 8 Meurzh 2024 da 05:21 UTCinvestigating

   One of our internal services is experiencing errors. We have initiated a workaround and meanwhile investigating the cause. You may notice several parts of the tracker and researcher portal might be resulting in errors as a result of this.

2. 8 Meurzh 2024 da 06:02 UTCinvestigating

   We have applied a temporary fix for the issue and the error rate has dropped. We are continuing to monitor and also investigating the root cause.

3. 8 Meurzh 2024 da 06:27 UTCresolved

   Root cause has been identified and the issue has been resolved. We will continue to monitor though.

1. 14 Mezheven 2023 da 02:01 UTCinvestigating

   We are currently experiencing issues with the outbound webhooks being broken. We are diagnosing this and will update the progress along the way.

2. 14 Mezheven 2023 da 02:34 UTCidentified

   Our proxy was experiencing problems due to unexpected behaviour of the dependant AWS service(s). The exact root cause is still unclear and we have filed a support ticket with AWS to understand the same.

3. 14 Mezheven 2023 da 02:40 UTCresolved

   The issue has resolved automatically. Will co-ordinate with the cloud provider support team for the RCA.

1. 14 Meurzh 2023 da 06:22 UTCidentified

   We've identified that there is an issue with the tracker and researcher portal currently that is causing the site to either not load, or load very slowly. We are working to rectify the problem.

2. 14 Meurzh 2023 da 07:06 UTCmonitoring

   A fix is rolling out and site performance should be returning to normal.

3. 14 Meurzh 2023 da 07:46 UTCresolved

   This incident has been resolved.

1. 8 Cʼhwevrer 2023 da 01:54 UTCidentified

   We are investigating an issue with indexed submissions and search currently - some functions involving submission retrieval are impacted at the moment.

2. 8 Cʼhwevrer 2023 da 02:29 UTCidentified

   We have identified a fix and are currently rolling it out.

3. 8 Cʼhwevrer 2023 da 02:48 UTCmonitoring

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

4. 8 Cʼhwevrer 2023 da 03:13 UTCresolved

   This incident has been resolved.

1. 3 Kerzu 2022 da 22:22 UTCidentified

   A mail provider is having issues which is leading to researcher emails going to bugcrowdninja.com addresses being delayed or not delivered. We are currently working with the provider to rectify the issue.

2. 4 Kerzu 2022 da 03:08 UTCresolved

   The mail provider has resolved the issue.

1. 28 Mezheven 2022 da 02:14 UTCmonitoring

   The previous maintenance was resolved early, and maintenance is still continuing. We will update on this new incident until the maintenance is complete.

2. 28 Mezheven 2022 da 02:33 UTCresolved

   Database maintenance has been completed.

1. 21 Mezheven 2022 da 06:46 UTCidentified

   We have identified a current issue with our CDN that fronts all of the Bugcrowd sites. While this is ongoing, Bugcrowd is currently unavailable. Incoming and outgoing webhooks are unaffected.

2. 21 Mezheven 2022 da 07:24 UTCmonitoring

   The CDN has recovered and our sites are accessible. We are monitoring the situation.

3. 21 Mezheven 2022 da 09:06 UTCresolved

   This incident has been resolved.

1. 8 Mezheven 2021 da 10:24 UTCidentified

   www.bugcrowd.com and numerous other sites on the internet are currently suffering from an external provider's outage. We are continuing to monitor the situation and will provide further updates as they become available.

2. 8 Mezheven 2021 da 11:22 UTCmonitoring

   The external provider issue is reportedly resolved and we are continuing to monitor availability.

3. 8 Mezheven 2021 da 13:30 UTCresolved

   The external provider has resolved the issue, and www.bugcrowd.com is continuing to function normally.

1. 11 Cʼhwevrer 2021 da 23:07 UTCinvestigating

   Our API is experiencing elevated error rates. We are investigating and will keep you posted.

2. 12 Cʼhwevrer 2021 da 00:07 UTCresolved

   This incident has been resolved.

1. 13 Gwengolo 2020 da 07:13 UTCinvestigating

   Our hosting provider for our home page is having issues. We are investigating

2. 13 Gwengolo 2020 da 07:29 UTCmonitoring

   Our provider appears to have resolved the issue. We will continue to monitor

3. 13 Gwengolo 2020 da 07:51 UTCresolved

   This incident has been resolved.