平台接入事件(美国)
Outage严重事件
- resolved
在协调世界时8月18日15:50至协调世界时15:56之间,"环球"在美国环境中经历了平台接入事件. 用户登录后无法访问平台 。 我们解决了这个问题,恢复了对所有用户的服务.
自动翻译自官方事件更新。
18 Globality incidents · 2025年7月 — official updates, affected components, duration and resolution details.
在协调世界时8月18日15:50至协调世界时15:56之间,"环球"在美国环境中经历了平台接入事件. 用户登录后无法访问平台 。 我们解决了这个问题,恢复了对所有用户的服务.
自动翻译自官方事件更新。
截至UTC8月18日15:50,"全球化"正在我们的prod.globality.com环境中发生平台接入事件. 用户登录后无法访问平台. 我们正在努力解决这一事件,一旦完成,我们将更新这一页.
在协调世界时8月18日15:50至协调世界时15:56之间,"环球"在我们的prod.globality.com环境中发生了平台接入事件. 用户登录后无法访问平台 。 我们解决了这个问题,恢复了对所有用户的服务.
自动翻译自官方事件更新。
从协调世界时8月2日09:35起,全球正在我们美国环境中发生平台接入事件. 用户登录后无法访问平台. 我们正在努力解决这一事件,一旦完成,我们将更新这一页.
在协调世界时8月2日09:35至协调世界时11:38之间,"环球"在美国环境中发生了平台接入事件. 用户登录后无法访问平台 。 我们缓解了这一问题,恢复了对所有用户的服务.
自动翻译自官方事件更新。
截至UTC7月24日11:01,"环球"正在经历平台登录事件. 用户无法登录到平台 。 我们正在努力解决这一事件,一旦完成,我们将更新这一页.
在协调世界时7月24日11:01至协调世界时11:09之间,"环球"经历了平台登录事件. 用户无法登录到平台 。 这个问题已经解决,所有用户的服务都已恢复.
自动翻译自官方事件更新。
截至协调世界时7月10日08:29,"全球"正在经历一起项目简介创建事件. 用户无法在平台上创建或编辑项目简报. 我们正在努力解决这一事件,一旦完成,我们将更新这一页.
在协调世界时7月10日08:29至协调世界时09:25之间,"环球"经历了一起项目简介创建出的事件. 用户无法在平台上创建或编辑项目简报 。 这个问题已得到解决,所有用户的服务都已恢复.
自动翻译自官方事件更新。
截至协调世界时6月26日06:53,"全球"正在经历平台登录事件. 用户无法登录到平台 。 我们正在努力解决这一事件,一旦完成,我们将更新这一页.
在协调世界时6月26日06:53至协调世界时6月26日07:21之间,"环球"经历了平台登录事件. 用户无法登录到平台 。 我们缓解了这一问题,恢复了对所有用户的服务.
自动翻译自官方事件更新。
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.