Is GMO GlobalSign Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We would like to inform you that urgent GCC maintenance is scheduled for 28 May 2025, from 12:00 to 14:00 UTC.During this window, the following services may experience processing delays of up to 15 minutes. Scope of impact - Certificate requests, issuance, and revocation - Certificate issuance, revocation, and other requests via API - Domain validation processing※ This includes JCAN certificates and certificates for emails.※ Note: There will be no impact on: The use of already issued certificates Certificate revocation checks.We apologize for any inconvenience this may cause and appreciate your understanding.

This incident has been resolved.

We identified an issue affecting certificate issuance through the GCC platform, causing an intermittent issuance failure. Some of the CAs were successful upon reprocessing. The team had resolved the issue, but we are continually monitoring in case of further problems. The team are planning mitigations in case of re-occurrence.

This incident has been resolved.

The issue has been resolved, but we are continually monitoring in case of further problems. The team are planning mitigations in case of re-occurrence.

The team will prepare to implement a fix and schedule 60 minutes of downtime soon across the GCC and JCAN platform. We will inform you when maintenance starts.

The identified issue is related to an external API integration, which is currently impacting our GCC Certificate Issuance. Our team is actively working to resolve this as quickly as possible. We appreciate your understanding and patience during this time.

We are continuing to investigate this issue.

We identified an issue affecting certificate issuance through the GCC platform, causing an intermittent ca_connection error. Some of the CAs were successful upon reprocessing. The team is still investigating the issue.

No further issues have been seen, and the service is returning to normal throughput levels. We are marking this issue as resolved.

The issue has been resolved and we are closely monitoring as the service returns to normal parameters

The Infrastructure team have identified the cause and are working on a resolution. HVCA and DSS are currently unavailable. TSA services are unaffected.

We are currently investigating an issue affecting Atlas certificate issuance and DSS services. We will provide an update as soon as we have confirmed the scope.

We have confirmed that the fix put in place does address the root cause of the issue, and no further unexpected errors have been seen since this was put in place.

We have identified an issue which was affecting a small amount of certificate issuance through the GCC platform, causing CAA validation to fail in some cases. The team have put a temporary fix in place which seems to have resolved the problem, however we are continuing to monitor and troubleshoot until we can confirm that the root cause has been resolved.

This incident has been resolved.

The team have resolved the issue and are monitoring the situation. No further related errors are being shown.

We are investigating an issue with the Atlas logging subsystem which may cause some API calls to fail intermittently (returning an HTTP 503). The team are working on resolving the problem ASAP.

This incident has been resolved.

The issue has been resolved. We are monitoring to ensure that there are no further errors.

The team have identified the issue and are working to resolve.

The infra team is investigating certificate validity issue due to OCSP. Certificates under R3 are affected.

This incident has been resolved.

The sites are available again and our team are closely monitoring them to ensure they remain up.

We are seeing timeouts when connecting to https://www.globalsign.com and https://partner.globalsign.com. The web team are investigating. Core (e.g. issuance, OCSP, API, timestamping) services are unaffected.

The issue is resolved and all global monitoring points are returning good status.

We are investigating problems with the Atlas portal which seem to be affecting access in some geographies. Access to the APIs themselves is unaffected.

No further authentication errors have been shown so we are considering this issue resolved.

We have identified a problem with one instance of a service relating to authentication and resolved it. It looks like there are no more errors but we are closely monitoring.

We are investigating the failure of a small percentage of authentication (/login) calls on the HVCA and DSS APIs. We will post shortly when we have more information. Most calls are still succeeding.

This incident has been resolved.

We believe the issue is resolved and are performing full testing to confirm.

Following the maintenance today, the portal is now available again but we are investigating issues which are preventing some customers from being able to manage domains or issue certificates through the portal. The team are working on resolving this with the highest priority. Issuance and domain management through the APIs (e.g. HVCA and ACME) is not affected.

We have seen no further problems so are marking this issue as resolved

Our team have resolved the issue and are closely monitoring to make sure it doesn't return. A root cause investigation is still underway.

It looks like the issue is still present and is now causing more /login calls to fail. Our team are working on resolving the issue.

We have seen a spike in errors returned to users sending /login calls to the DSS and HVCA APIs. This started at around 06:50 UTC and looks to have recovered, although our team are closely monitoring and will be investigating the root cause.

The issue has been resolved. The portal should now be fully functional

We have identified an issue which is preventing the Atlas portal from viewing and creating information such as API keys and mTLS certs. The team are working on this with the highest priority and hope to have it resolved ASAP.

Following an investigation we believe the issue is fully resolved.

There was a short window between about 07:30 and 07:40 UTC where a small percentage of /login requests for the DSS and HVCA APIs failed. Everything is working normally at the current time and we are continuing to monitor until we have fully identified the root cause.

We are investigating a possible issue on DSS and HVCA which is causing some API calls to fail. We will post when we have more information.

We have confirmed that the issue is resolved. The total period of the issue was 1 minute 41 seconds, during which a percentage of API calls were affected and will have received an HTTP 503 response.

The team have resolved the issue and are monitoring, however root cause has not yet been identified

We are seeing high levels of errors on both HVCA and DSS API calls. The team are investigating

This incident has been resolved.

Our engineers identified a small number of errors on some particular API endpoints, the issue is resolved and we are continuing to monitor. Certificate issuance was not significantly affected during this period.

We are currently investigating some reports of errors from parts of the GCC platform. We will confirm once we have been able to recreate the issue.

We have experienced a short outage on the /stats and (deprecated) /counters endpoints of the HVCA API, starting at around 12:20 UTC. No core HVCA functionality was affected, but these endpoints returned HTTP 503 for a period. This is due to a failover between servers within the logging subsystem and is expected behaviour in such a case.

After 1:46 am on 10 April 2024 (UTC), we have not received any further alerts. Based on this, we conclude that the incident has been resolved. Thank you for your patience and understanding during this time.

Since 1:46 am on 10 April 2024 (UTC), our system has been operating without any errors. We continue to monitor the system closely to ensure optimal performance and reliability.

From 20:11 on 9 April 2024 (UTC), we noticed that some certificates were being denied for issuance. We are currently investigating the cause of this incident.

The Incident Report for this incident is now available here: [https://media.globalsign.com/Public\_Incident\_Report\_20240320\_Atlas\_certificate\_issuance\_failure](https://media.globalsign.com/Public_Incident_Report_20240320_Atlas_certificate_issuance_failure)

For a period between roughly 05:20 and 06:30 UTC, certificate issuance on Atlas (HVCA, and DSS identities) was failing. This was due to a database cluster issue. A full Incident Report will be attached once the postmortem is complete.

Full Incident Report is available [here](https://media.globalsign.com/en/IncidentsReports/20240130-atlas-dss-outage).

We have had no further issues following implementation of the fix. Root Cause Analysis is continuing and we will post an Incident Report when this is complete.

A fix has been implemented and we are monitoring to make sure no further errors are being reported. The root cause is still under investigation.

We are currently investigating issues which are causing some customers to get TLS errors when connecting to the HVCA and DSS APIs. We will post more as investigations continue.

No more failures have been observed following our changes, so we are considering the incident resolved.

Working with our partner we have implemented a fix. Affected customers are now successfully able to obtain Japan Certified timestamps. We will continue to monitor the situation before marking as fully resolved.

Unfortunately our fix did not prove successful in testing. We are currently awaiting response from our Japan Certified timestamp partner. We will work with them to resolve the issue as soon as we hear back from them. In the meantime our Development team continue to work in parallel to explore options for a workaround from our side.

Working with the Development team, we have identified a potential solution for the affected customers. This is currently being tested and we hope to be able to roll it out shortly.

Following maintenance by one of our Japanese timestamp partners, it appears that requests for Japan Certified timestamps through DSS are failing. All other requests, and other timestamp types, are working correctly. We are investigating with the help of the Development team and will identify a fix or work with our provider on one as appropriate.

Currently DSS service is partially unavailable. Infrastructure team is now investigating the cause.

Incident Report can be found here: [https://media.globalsign.com/en/IncidentReports/20240119\_GCC\_disruption\_and\_outage](https://media.globalsign.com/en/IncidentReports/20240119_GCC_disruption_and_outage)

The SSL-API was temporarily unstable after we placed it in a monitored status, but we have now removed the root cause and stabilized it. We apologize for the long period of system instability. All services are now up and running without any problems. Summary of incident: Start date and time: 2024 January 18, 10:14 PM (UTC) Resolved date and time: 2024 January 19, 09:55 AM (UTC) Total incident time: 11 hours 41 minutes.

SSL API service is restored. All service is operational now. We monitor the system intensively for a while.

SSL API is still under troubleshooting. We apologize for the inconvenience. Next update is at 2024 January 19 7:00 AM UTC.

SSL API is still under troubleshooting. We apologize for the inconvenience. Next update is at 2024 January 19 6:00 AM UTC.

Following services are restored: - GCC GUI - Client API SSL API is still being troubleshooted. We apologize for any inconvenience caused. Next update is at 2024 January 19 5:00 AM UTC.

Internal service disruption has been resolved. We are restarting services one by one and are currently confirming that each is functioning appropriately. Next update is at 2024 January 19 4:00 AM UTC.

Identified internal service disruption. We are actively preparing for failover. Next update is at 2024 January 19 3:00 AM UTC.

We are still investigating the cause of the issue and troubleshooting. We apologize for any inconvenience this may have caused. Next update is at 2024 January 19 2:00 AM UTC.

We are still investigating the cause of the issue and troubleshooting to resolve it as soon as possible. We apologize for any inconvenience this may have caused. We have confirmed that there is an impact to the Client API, the title of this incident notification has been updated. Next update is at 2024 January 19 1:00 AM UTC.

Currently GCC GUI and SSL API are down. We are investigating the cause and troubleshooting to resolve this issue. Time started : 2024 January 18, around 10:14 PM UTC Affected service: GCC GUI, SSL API Next update is at 2024 January 19 0:00 AM UTC.

The issue has been resolved. All /login calls are now being successfully processed by all authentication nodes.

We are investigating an issue which is causing a percentage of /login requests to the Atlas APIs to fail (return HTTP 503). We will post updates as soon as we have confirmed the issue.

This issue has been resolved and timestamps are being returned successfully from the Japanese Certified timestamp services.

We have identified a higher than normal error rate on our TSA services. This relates to customers using Japan accredited (Certified) timestamps in the DSS platform, some timestamp calls for these customers are failing. We will be applying a fix for affected customers in the coming hours.

This incident has been resolved.

The system issues we were experiencing have now been resolved. We understand that this may have caused inconvenience, and we sincerely apologize for any disruption this may have caused. We keep monitoring the system carefully for a while

We are also currently experiencing some instability with My Number system and Site Seal service. Team is aware of the issue and is actively investigating to resolve it as quickly as possible.

We are currently experiencing an incident with GCC GUI and API. Our team is actively investigating the issue and working towards a resolution. We understand the inconvenience this may cause and appreciate your patience during this time. We will continue to provide updates as more information becomes available.

The issue has been resolved, and issuance is now being performed within usual times. The third party CT Log is still unavailable, but this is no longer affecting Atlas issuance.

We are currently experiencing slow TLS certificate issuance in Atlas. This is because of the unavailability of one of the core CT Logs which we need to submit certificates to. TLS certificates may take a longer period than usual to be issued. We are investigating why the impact is as large as it is, given the other logs are available.

The issue has been resolved

A fix has been deployed and the team are monitoring to ensure that all errors have ceased.

The team have identified the cause of the problem and aim to have a resolution in place imminently

We are currently investigating an issue affecting Atlas timestamps (including timestamping for DSS).

The Incident Report for this incident can be found here: [https://media.globalsign.com/l/707663/2023-10-05/9msg7q/707663/16964964437NLoKZOg/Public\_Incident\_Report\_20230827\_Outage\_on\_Atlas\_data\_APIs\_and\_OCSP\_ser.pdf](https://media.globalsign.com/l/707663/2023-10-05/9msg7q/707663/16964964437NLoKZOg/Public_Incident_Report_20230827_Outage_on_Atlas_data_APIs_and_OCSP_ser.pdf)

The incident is considered resolved, and the platform is stable. We will publish an Incident Report as soon as we have it ready.

All services should now be operational. We are monitoring closely as they catch up with customer requests.

Our engineers are on-site and are working on a resolution

We appear to have identified the issue. Certificates are now being queued for issuance, but we need to get engineers on-site at our data center to fully resolve the issue. We have scrambled the on-call team.

We are continuing to investigate the issue. Some services are unable to connect to some core databases, but these databases are operational. Direct TSA services seem to be working. HVCA and DSS are affected.

We are currently affecting an outage that is affecting all Atlas API services (DSS, HVCA, TSA) and OCSP services for Atlas. We will post further updates as soon as we have identified the issue.

This incident has been resolved.

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

Access to GCC webportal and some web services hosted in Japan is currently unstable. We are investigating to resolve this issue.

There is no network issue more than 10 hours. We change the status from Monitoring to Resolved.

Web access is now stable. We will investigate the root cause with our network service providers.

We are continuing to investigate this issue.

As of 13:03 UTC, the following web access is unstable - Official GlobalSign website for Japan - GCC service - JCAN service - Siteseal service - My number service We are currently working to determine the cause of this incident.

The vendor has marked their issue as resolved, and we have seen stability across the production platform since accessibility was restored

We have seen recovery on our production services. We will continue to monitor to ensure that they remain stable

One of our third party vendors is experiencing problems which are causing the Atlas user portal to be inaccessible at the current time. We will keep you updated as we here more. Atlas services themselves (DSS, HVCA / Certificate issuance, TSA, OCSP) are all operating as normal.

Please find the Incident Report for this incident here: [https://media.globalsign.com/en-incident-report-20230816](https://media.globalsign.com/en-incident-report-20230816)

Marking incident as resolved following monitoring period.

The issue has been resolved. We do not believe there will be any recurrence, but are continuing to monitor the affected servers closely for the next hour or so to ensure there are no further issues.

We are currently investigating an issue reported by our monitoring systems affecting multiple Atlas services (HVCA, DSS, TSA). We are currently investigating and will post more information as soon as it is available.

This incident has been resolved.

Our Infrastructure Team are currently investigating issues with the GCC issuance platform, the platform is available but some functionality is not functional or is unavailable sporadically. We will update as soon as we have identified the root cause.

At approximately 14:10 UTC, we experienced a brief outage of Atlas APIs, lasting about 5 minutes. Customers will have experienced HTTP 503 responses to API calls to HVCA and DSS during this time. The Infrastructure team are investigating the root cause.

This incident has been resolved.

Service is restored. We will keep monitoring the service for a while. We apologize for the service unavailability for several hours.

Infrastructure team is still checking restored configration with vendor.

Hardware replacement and configuration restoration are completed. We are now performing final check.

We are currently investigating this issue.

Hardware for replacement has arrived in data center. Infrastructure team starts hardware replacement and configuration restoration.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

Vendor is now preparing hardware for replacement. The hardware will be delivered in 1 -2 hours.

Currently hardware vendor is investigating root cause on site.

We are investigating hardware which are causing issue with vendor.

We are continuing to investigate this issue.

Investigation is still in progress to isolate the root cause of the service unavailability.

We are continuing to investigate this issue.

We are currently investigating an issue that is causing service unavailability of GCC User Portal, Certificate Issuance by GUI and API, Siteseal, Timestamp. We will update as soon as we have isolated the problem.

The backlog has completed and issuance speed is back to normal

The team have identified and resolved the cause of the issue. There is a backlog of orders which are currently being processed - we expect these to clear in the next hour and issuance times to return to normal from that point.

We are currently investigating an issue that is causing delays or errors in issuance for a number of GCC customers. We will update as soon as we have isolated the problem. Other services (e.g. Atlas APIs, Timestamping) are not affected.

The issue has been resolved and validation is working as normal.

We are currently investigating an issue that is causing domain validation by DNS and HTTP to fail in GCC. Atlas domain validation is unaffected. We will post updates as soon as they are available.

We have identified and resolved the issue, which was preventing communication between CIT and the authentication service. CIT is now operational again.

We are engaging with our technology partner to help investigate and resolve the issue, as we have not been able to identify the problem from our side. We will post updates as we get more information.

We are currently investigating an issue with CIT (https://cit.globalsign.com) which is causing a blank page when logging into the portal. We will post as soon as we have further information. No other Atlas or GCC services are affected.

An incident report for this issue is now available to download here: [**GMO GlobalSign Incident Report - HTTP 503 errors returned by Atlas authentication service**](https://media.globalsign.com/incident-reports/20221007/atlas-http-503-errors.pdf)

All services have been restored to normal function. The investigation by the teams showed that a corrupted database index affected the performance of the system for some customers, leading to intermittent 503 errors, while others were unaffected by the issue. The index was re-created and this process completed as of 15:30 UTC, resolving the issue across all the affected customers.

The Infrastructure and Development teams are continuing to work the issue. At the current time a small number of customers are affected. We will continue to update.

The Infrastructure team believe they have identified the issue and have put a workaround in place. Some calls to /login are taking longer than usual to complete but most customers should be seeing successful authentication now. The team are continuing to work on the root cause and we will continue to post updates.

We are continuing to investigate this issue. At the current time we don't have an ETA for complete resolution, but our teams are working on it as the top priority.

We are investigating a potential issue which is giving occasional HTTP 503 ("Service busy") response to login (authentication) calls. We will provide further information as soon as we have identified the cause of the issue.

The system has been confirmed stable and the incident is now closed.

Further to the incident yesterday, there has been a recurrence of the problem, causing HTTP 503 errors for a small number of customers. This has been resolved, however the team are closely monitoring the platform and are performing further investigation into the cause of the index problems.

This incident has been resolved.

The issue seems to be resolved, but we are monitoring while we identify the root cause.

We are investigating an issue with GlobalSign CIT which causes it to display a blank page when users log in.

This incident has been resolved.

We experienced a spike in HTTP 503 errors returned by the Atlas HVCA and DSS APIs between 11:27 and 11:29 UTC. This affected roughly 1% of requests received during this period. We believe the issue has been resolved, but are continuing to closely monitor the situation.

Following work by our service provider, full redundancy and capacity has been restored on the system.

We have found and implemented a fix, so CIT is available again. We are continuing to work with our service provider to regain full redundancy on the service.

The Certificate Inventory Tool (https://cit.globalsign.com) is currently unavailable. We have identified the issue, which relates to a problem at our third party service provider. We will be working with them to get the service back online as soon as possible.

Our CDN partner has resolved the issue on their end, and their availability has been independently verified by our Infrastructure team. We have re-established full CDN redundancy for GlobalSign's systems.

One of our CDN partners is experiencing a network issue, detected our end at about 6:39 UTC. This may have resulted in customers receiving errors on the website and on OCSP/CRL services. As of 07:04 UTC, we have stopped directing traffic to the affected CDN. We are monitoring availability, and will re-enable once it it considered stable.

We have experienced a brief issue between 12:22 and 12:29 UTC which caused the Atlas portal to display a 403 error. The issue has been resolved by our Infrastructure team

Our ISP reports that the cable break has been repaired and the issue is resolved.

Our ISP has provided an ETA on full resolution of 14th March. They have provided alternative bandwidth to affected areas which has negated the effects of the issue, but we are continuing to closely monitor latency globally in case of issues.

Our ISP has re-routed traffic between Japan and Singapore which has resolved issues for GlobalSign customers. However we are continuing to monitor closely until the issue is declared fully resolved.

The issue is cased by a suspected break in an undersea cable but our ISP are keeping us updated with resolution progress. In the meantime, latency to Japan-based services (GCC) is much improved - response times from Singapore are back to normal and those from India are significantly reduced from their peak on 26th/27th December.

One of our ISPs in Japan is experiencing latency issues which are affecting connectivity from some locations. Customers in Singapore and India may experience high latency or timeouts when connecting to GCC. Certificate issuance may take longer than usual in some cases. GlobalSign's Infrastructure team have rerouted traffic between our Japan and Singapore data centres to reduce any delays in issuance, and are communicating directly with the affected ISP, to ensure the issue can be fully resolved for customers in India and Singapore.

We are aware of an issue affecting internal account management services over the weekend. This issue also affected direct customers of the GCC APIs for periods. The issue was resolved as of 05:48 UTC on Sunday 8th May, and the Infrastructure and Development teams are performing the Root Cause Analysis.

The issue has been resolved.

We have identified an issuer affecting the Atlas user portal (https://atlas.globalsign.com). Users may see "500 - Server Error" displayed on some pages. The Development team are investigating the root cause and this will be resolved ASAP. The Atlas services themselves are not affected.

This issue has been confirmed as resolved

On Tuesday 22nd February between about 14:50 and 17:00 UTC we experienced an issue where a percentage of timestamp requests returned an HTTP 504 (timeout) response. The problem has been resolved, but we are continuing to closely monitor the service as we work to identify the root cause.

We experienced 24 minutes of disruption to traffic to the Edge Enroll interface for HVCA between 13:30UTC and 14:15UTC today. This related to a routine database primary election causing problems to the application itself. Our teams are investigating the root cause.

This incident has been resolved.

A fix has been implemented and dashboards and scans are now working. We are continuing to monitor and will work with the vendor to implement further improvements if necessary.

We are aware that CIT is currently experiencing an outage. The AWS server that hosts CIT had a network issue, resulting in the system sending packages of false scan emails and showing blank dashboards upon login. Our infrastructure team is working with the vendor Remme to resolve. We hope the system will be back online by tomorrow.