Service ShareFile non disponible
Pending
- resolved
Le service ShareFile a été restauré et fonctionne à nouveau normalement. Merci de votre patience.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
25 Glesys incidents · février 2026 — official updates, affected components, duration and resolution details.
Le service ShareFile a été restauré et fonctionne à nouveau normalement. Merci de votre patience.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
This maintenance has been cancelled.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
Read the incident report regarding the network issue in Oulu. [Download](https://static.glesys.com/docs/Incident-Report-GleSYS-2026-04-30.pdf)
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete.
We have found the underlying issue and we have now resolved the incident.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
Some customers experienced connectivity issues when accessing the Object Storage service at: https://objects.dc-sto1.glesys.net Clients with older CA certificate bundles may have encountered errors such as: certificate verify failed: unable to get local issuer certificate. The issue was caused by an incomplete TLS certificate chain. After Glesys technicians updated the certificate chain with the required intermediate certificates, affected clients were able to connect again. If you are still experiencing issues, please contact our support team at [email protected]