GlobalSign: OCSP Status HTTP 530

This case involves GlobalSign's disclosure of an incident affecting their OCSP responder services, which resulted in HTTP 530 errors. The issue was triggered by instability at one of their data centers, leading to intermittent failures in OCSP responses. GlobalSign acknowledged the problem and provided an incident report detailing the timeline of events and the actions taken to mitigate the issue. The CA has since implemented improvements to their disaster recovery plans and incident communication processes to prevent future occurrences. The case is now resolved with the status marked as FIXED.

1. 2020-03-10 GlobalSign's monitoring tools identified issues with OCSP response times.
2. 2020-03-14 All services were restored and operational.

1. 2020-03-14 Community commenter — Reported OCSP server errors while accessing a specific URL.
2. 2020-03-14 GlobalSign nv-sa — Confirmed instability at a data center and stated it would be resolved shortly.
3. 2020-03-19 GlobalSign nv-sa — Attached an incident report detailing the outage.
4. 2020-05-04 GlobalSign nv-sa — Provided a timeline of actions taken in response to the incident.
5. 2020-07-22 GlobalSign nv-sa — Updated on the completion of reviews and improvements to incident communication.
6. 2020-08-10 Mozilla representative — Inquired about the status of the incident report and whether the case could be closed.