Bugcrowd experienced a notice incident on October 17, 2018 affecting bugcrowd.com && tracker.bugcrowd.com, lasting 3h 16m. The incident has been resolved; the full update timeline is below.
Affected components
bugcrowd.com && tracker.bugcrowd.com
Update timeline
- monitoring Oct 17, 2018, 07:39 PM UTC
At 11:28am PDT we lost our primary database server. Our database cluster failed over to our hot standby in another Availability Zone in about 3 minutes. It took another 7 minutes for our application servers to restart and pickup the new DNS record. We were down for approximately 10 minutes. This may be related to the current AWS EC2 connectivity issues in us-east-1. We are actively monitoring the situation.
- resolved Oct 17, 2018, 10:56 PM UTC
This incident has been resolved.