Live / GMO GlobalSign / Incident
GMO GlobalSign: Atlas Certificate Issuance (HVCA API) customer parsing issue
GMO GlobalSign · globalsign.comResolved2026-10-14 09:54 UTC
Public — what happened
Summary
GMO GlobalSign reported on 2026-10-13 at 15:17 UTC that some customers were having trouble handling responses from its Atlas Certificate Issuance (HVCA API) after load balancer maintenance carried out earlier that day. The company said the problem came from an accidental change to one of the HTTP response headers, and noted that certificates could still be issued. By 15:58 UTC GlobalSign said the header had been restored to its pre-maintenance format, and the incident was marked resolved on 2026-10-14 at 09:54.
Affected
Certificate Issuance
Timeline
- Started — 2026-10-13 15:17 UTC
- Identified — 2026-10-13 15:17 UTC
- Monitoring — 2026-10-13 15:58 UTC
- Resolved — 2026-10-14 09:54 UTC · 18h 37m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GMO GlobalSign against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GMO GlobalSign: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GMO GlobalSign report →
More from GMO GlobalSign
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.