pingoru pingoru Nx had 10 outages in the last 2 years totaling 9h 24m of downtime, averaging 0.4 incidents per month.
There were 10 Nx outages since May 15, 2025 totaling 9h 24m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are currently investigating this issue.
All dedicated compute orgs have been moved to a backup region.
We are currently investigating this issue.
We've identified an the issue causing higher error rates
A fix has been implemented and errors processing CIPEs have returned to normal levels. we will continue to monitor.
We are continuing to monitor for any further issues.
Issue as been resolved. We apologies for any inconvenience. Re-running CIPEs that errored out during this time should have them run normally.
We've received alerts about a high number of errors and slow response times on the Nx API. The team is investigate a fix.
We are continuing to investigate this issue.
The issue has been identified and a fix has been issued, we are waiting a few more minutes to verify that the Nx API is healthy.
The Nx API is back to operating as normal. Please restart any pipelines that were disrupted, we apologize for any inconvenience caused.
The nx-api was briefly unavailable. A fix has been implemented but existing work may need to be restarted. We are continuing to monitor.
Some users reported errors from the Nx API, which resulted in not being able to download the runner or failed CIPEs. The team investigated and was able to resolve the issue within 15 minutes. We are monitoring traffic closely, please let us know at [email protected] if you see any additional issues.
We are currently investigating this issue.
Agent runs leveraging docker are experiencing issues pulling images from DockerHub. Please see https://www.dockerstatus.com/
The incident with DockerHub is ongoing and we are awaiting an update. Please see https://www.dockerstatus.com/
Docker has deployed a fix and continues to monitor. At this time we are closing this incident and encourage users to check https://www.dockerstatus.com/ for any further updates
We are currently investigating this issue.
We are continuing to investigate. At this time, issues are isolated to the North American application
We have identified the issue are are working to resolve
We have issues a fix and are monitoring the resolution
All issues have been resolved and operations have returned to normal
We've noticed a small subset of users running into issues with pipelines erroring. The team is investigating
The issue has been identified and a fix is being prepared for release
We're continuing to monitor the deployment and seeing error rates return to normal.
This incident has been resolved.
We are currently investigating this issue.
We have identified the issue with our upstream provider. At this time we are waiting on a resolution from them.
Our provider has reported that they are mitigating and some regions are beginning to recover. We are continuing to monitor. Please see https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW for information on the provider recovery.
Provider issues are ongoing, we are continuing to monitor
We are continuing to monitor the situation. Please find the most up to date status information from Google https://status.cloud.google.com
Our cloud provider is reporting gradual recovery of affected services, we are continuing our monitoring.
Recovery is underway, systems are operational are continuing to monitor
All services are now operational
The Nx API is restored. Thank you for your patience, please reach out to us at [email protected] if you experience any more issues.