18 Globality incidents · juillet 2025 — official updates, affected components, duration and resolution details.
Entre le 18 août, 15h50 UTC et 15h56 UTC, Globality a connu un incident avec un accès à la plateforme dans notre environnement américain. Les utilisateurs n'ont pas pu accéder à la plateforme après la connexion. Nous avons résolu le problème et rétabli le service pour tous les utilisateurs.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
En date du 18 août, 15h50 UTC, Globality connaît un incident avec un accès à la plateforme dans notre environnement prod.globality.com. Les utilisateurs ne peuvent pas accéder à la plateforme après la connexion. Nous travaillons à résoudre l'incident et mettrons à jour cette page une fois terminée.
Entre le 18 août, 15h50 UTC et 15h56 UTC, Globality a connu un incident avec accès à la plateforme dans notre environnement prod.globality.com. Les utilisateurs n'ont pas pu accéder à la plateforme après la connexion. Nous avons résolu le problème et rétabli le service pour tous les utilisateurs.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
En date du 2 août, 09h35 UTC, Globality connaît un incident avec un accès à la plateforme dans notre environnement américain. Les utilisateurs ne peuvent pas accéder à la plateforme après la connexion. Nous travaillons à résoudre l'incident et mettrons à jour cette page une fois terminée.
Entre le 2 août, 09h35 UTC et 11h38 UTC, Globality a connu un incident avec un accès à la plateforme dans notre environnement américain. Les utilisateurs n'ont pas pu accéder à la plateforme après la connexion. Nous avons atténué le problème et rétabli le service pour tous les utilisateurs.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
En date du 24 juillet, 11:01 UTC, Globality connaît un incident avec connexion plate-forme. Les utilisateurs ne peuvent pas se connecter à la plateforme. Nous travaillons à résoudre l'incident et mettrons à jour cette page une fois terminée.
Entre le 24 juillet, 11:01 UTC et 11:09 UTC, Globality a connu un incident avec connexion à la plateforme. Les utilisateurs ne pouvaient pas se connecter à la plateforme. Le problème a été résolu et le service a été rétabli pour tous les utilisateurs.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Au 10 juillet, 08:29 UTC, Globality connaît un incident avec une brève création de projet. Les utilisateurs ne peuvent pas créer ou modifier des dossiers de projet sur la plateforme. Nous travaillons à résoudre l'incident et mettrons à jour cette page une fois terminée.
Entre le 10 juillet, 08:29 UTC et 09:25 UTC, Globality a connu un incident avec la création brève du projet. Les utilisateurs n'ont pas pu créer ou modifier des mémoires de projet sur la plateforme. Le problème a été résolu et le service a été rétabli pour tous les utilisateurs.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
En date du 26 juin, 06:53 UTC, Globality connaît un incident avec connexion à la plateforme. Les utilisateurs ne peuvent pas se connecter à la plateforme. Nous travaillons à résoudre l'incident et mettrons à jour cette page une fois terminée.
Entre le 26 juin, 06:53 UTC et le 26 juin, 07:21 UTC, Globality a connu un incident avec la connexion de la plateforme. Les utilisateurs ne pouvaient pas se connecter à la plateforme. Nous avons atténué le problème et rétabli le service pour tous les utilisateurs.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
We are investigating slowness in our project creation & invitation.
We identified the root-cause for the issues, and working on a fix.
We have mitigated the issue and continue to monitor the platform’s health.
On May 27, between 14:11 UTC and 16:29 UTC, Globality users experienced slowness stemming from underlying issues with a service provider's API. Once we identified the issue, we temporarily switched over to another vendor to mitigate. Based on this incident, we are optimizing our platform to handle such incidents in a shorter time.
We are investigating reports from users who are experiencing issues with project creation & invitation.
We identified the root-cause for the issues, and working on a fix.
We have mitigated the issue and continue to monitor the platform’s health.
On May 8, between 16:37 UTC and 23:55 UTC, Globality experienced platform impacts stemming from multiple high-volume operations. Based on this incident, we have optimized our platform to handle such operations without impacting overall platform performance.
We are investigating reports of users unable to access proposals
Between 19:26 UTC and 19:47 UTC, Globality experienced an incident with Proposals, wherein users could not access proposals for some projects. We have mitigated the issue and continue to monitor the platform’s health.
This incident has been resolved. Globality has identified a performance issue during a routine service upgrade, we are implementing guardrails to ensure that future service upgrades do not impact performance.
We are investigating reports from users who are experiencing issues with project creation.
We have mitigated the issue and continue to monitor the platform’s health.
Between March 18, 20:45 UTC and March 19, 1:09 UTC Globality experienced an incident with project creation, wherein the project brief was skipped entirely and users were taken directly to supplier matching with all brief sections empty. Based on this incident, we accelerated and completed the migration of the underlying service from legacy to newer, more robust infrastructure.
We are investigating reports from users who are experiencing issues with project creation.
We have mitigated the issue and continue to monitor the platform’s health.
On March 11, between 21:30 UTC and 23:08 UTC Globality experienced an incident with project creation, wherein the project brief was skipped entirely and users were taken directly to supplier matching with all brief sections empty. Based on this incident, we will be migrating the underlying service from legacy to newer, more robust infrastructure.
We are investigating reports from users who are experiencing performance issues using the Globality platform.
We have mitigated the issue and continue to monitor the platform’s health.
Between January 30, 20:50 UTC and January 31, 00:13 UTC, some users on the Globality platform were experiencing performance issues due to a misconfiguration during a routine service upgrade.
We are investigating reports from users who are experiencing performance issues using the Globality platform.
We identified the root-cause for the slowness, mitigated the issue and continue to monitor the platform’s health.
We are investigating additional reports of slowness with the platform.
On January 15, between 10:00 UTC and 17:00 UTC, users on the Globality platform were experiencing performance issues due to an inadvertent configuration change for multiple services. Based on this incident, we are implementing additional guardrails for configuration changes of this type to prevent future performance impact.
As of 08:11 UTC the Globality platform is down due to an AWS outage.
AWS outage is still in progress.
AWS has identified the root-cause and working to accelerate recovery.
AWS reporting they are seeing significant signs of recovery.
On October 20, between 8:11 UTC and 10:27 UTC, the Globality platform was down due to an AWS outage. https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A
We are investigating reports of users unable to access some project workspaces.
As of as of 6:35 PM GMT, Globality is experiencing an incident with Project Briefs. Users encounter an error when click on “Brief”. We are working to resolve the incident and will update this page once complete.
We are continuing to investigate this issue.
Between 6:35 PM GMT and 7:45 PM GMT, Globality experienced an incident with Projects, wherein users could not access project briefs for some projects. We have mitigated the issue and continue to monitor the platform’s health.
This incident has been resolved. Globality has identified an issue in the service delivery pipeline that resulted in this incident, and will implement improved monitoring and durability for the impacted pipeline.
We are investigating reports of users unable to view provider information.
On August 22, between 4:44 PM GMT and 5:53 PM GMT, Globality experienced a degradation with project invitations. Users may have experienced issues viewing provider information. We mitigated the issue and restored service for all users. Based on this incident, we are implementing enhanced alerting to detect similar issues even sooner and ensure continued reliability.
We are investigating reports of users unable to access the platform.
On August 21, between 10:34 AM GMT and 12:09 PM GMT, the platform experienced login degradation. During this period, some users may have been unable to log in due to an issue with one of our infrastructure components. We mitigated the incident by applying changes to our backend services. Going forward, we are improving monitoring to shorten detection times and addressing gaps in testing to help prevent similar incidents.
We are currently investigating this issue.
On July 15, between 12:01AM GMT and 11:52AM GMT, Globality experienced a degradation with project invitations. Users may have experienced issues with inviting providers to a project due to a change in a project invitation component. We mitigated the incident by rolling back the component change. Based on this incident, we are working on better monitoring to reduce our detection time and fixing gaps in testing to prevent a repeat of incidents such as this one in the future.