Bugcrowd 장애 기록

1. 2026년 9월 15일 오전 6:07 UTCinvestigating

   비동기 작업의 처리에 영향을 미치는 플랫폼에 문제가 있습니다. 특히 검색 및 인덱스와 관련이 있습니다. 우리는 현재 투자하고 곧 업데이트됩니다.

2. 2026년 9월 15일 오전 7:05 UTCidentified

   우리는 우리가 원인을 확인 믿는다 (동기적인 색인 전화 내의 느린 의존 서비스) 그리고 수정을 밀어의 과정에서.

3. 2026년 9월 15일 오전 8:21 UTCidentified

   푸시된 변화는 수정을 산출하지 않았습니다, 우리는 문제점에 일하고 더 깊이에 있는 고침을 탐구하기 위하여 계속됩니다.

4. 2026년 9월 15일 오전 9:14 UTCidentified

   수정이 배포되고 비동기 작업 큐는 처리됩니다 (뿐만 아니라 backlog).

5. 2026년 9월 15일 오전 9:15 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

6. 2026년 9월 15일 오전 10:00 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 2월 26일 오전 5: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. 2026년 2월 26일 오전 5:25 UTCmonitoring

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

3. 2026년 2월 26일 오전 5:33 UTCresolved

   This incident has been resolved.

1. 2025년 10월 22일 오전 12: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. 2025년 10월 22일 오전 12:30 UTCmonitoring

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

3. 2025년 10월 22일 오전 12:50 UTCresolved

   This incident has been resolved.

1. 2025년 7월 24일 오후 9: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. 2025년 7월 25일 오전 1:28 UTCmonitoring

   We've implemented a remediation and are now recovering.

3. 2025년 7월 25일 오전 2:15 UTCresolved

   This incident has been resolved.

1. 2025년 4월 10일 오후 6: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. 2025년 4월 11일 오전 6:50 UTCresolved

   Email sending from the platform is functional again.

1. 2025년 4월 9일 오전 1: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. 2025년 4월 9일 오전 5:20 UTCresolved

   Email sending from the platform is functional again.

1. 2024년 11월 14일 오전 3:02 UTCidentified

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

2. 2024년 11월 14일 오전 3:21 UTCresolved

   This incident has been resolved.

1. 2024년 9월 11일 오전 1: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. 2024년 9월 11일 오전 1:51 UTCresolved

   This incident has been resolved.

1. 2024년 8월 8일 오전 1: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. 2024년 8월 8일 오전 1: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. 2024년 7월 4일 오전 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. 2024년 7월 4일 오전 11:21 UTCmonitoring

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

3. 2024년 7월 4일 오전 11:28 UTCresolved

   Backlog processing has completed, systems have returned to normal.

1. 2024년 3월 8일 오전 5: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. 2024년 3월 8일 오전 6: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. 2024년 3월 8일 오전 6:27 UTCresolved

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

1. 2023년 6월 14일 오전 2: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. 2023년 6월 14일 오전 2: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. 2023년 6월 14일 오전 2:40 UTCresolved

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

1. 2023년 3월 14일 오전 6: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. 2023년 3월 14일 오전 7:06 UTCmonitoring

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

3. 2023년 3월 14일 오전 7:46 UTCresolved

   This incident has been resolved.

1. 2023년 2월 8일 오전 1:54 UTCidentified

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

2. 2023년 2월 8일 오전 2:29 UTCidentified

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

3. 2023년 2월 8일 오전 2:48 UTCmonitoring

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

4. 2023년 2월 8일 오전 3:13 UTCresolved

   This incident has been resolved.

1. 2022년 12월 3일 오후 10: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. 2022년 12월 4일 오전 3:08 UTCresolved

   The mail provider has resolved the issue.

1. 2022년 6월 28일 오전 2: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. 2022년 6월 28일 오전 2:33 UTCresolved

   Database maintenance has been completed.

1. 2022년 6월 21일 오전 6: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. 2022년 6월 21일 오전 7:24 UTCmonitoring

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

3. 2022년 6월 21일 오전 9:06 UTCresolved

   This incident has been resolved.

1. 2021년 6월 8일 오전 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. 2021년 6월 8일 오전 11:22 UTCmonitoring

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

3. 2021년 6월 8일 오후 1:30 UTCresolved

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

1. 2021년 2월 11일 오후 11:07 UTCinvestigating

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

2. 2021년 2월 12일 오전 12:07 UTCresolved

   This incident has been resolved.

1. 2020년 9월 13일 오전 7:13 UTCinvestigating

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

2. 2020년 9월 13일 오전 7:29 UTCmonitoring

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

3. 2020년 9월 13일 오전 7:51 UTCresolved

   This incident has been resolved.