Is StepSecurity down?

We identified a caching issue affecting metadata responses for some npm packages served through Secure Registry. Affected responses may contain package download URLs pointing to a different registry endpoint than the one configured by the customer. This may cause package installation or dependency resolution failures. The issue occurs when registry deployments share cached metadata containing deployment-specific download URLs. We have identified the root cause and are preparing a fix to isolate these cached responses by registry endpoint.

The issue has been resolved, and all affected services are operating normally.

We are currently investigating an increase in 502 errors on our package registry service. Some package installs may intermittently fail or time out. We will share an update as soon as we have more information.

We have deployed a fix for the underlying issue and are closely monitoring the service to confirm it fully resolves the elevated error rate seen earlier. No further impact has been observed since the fix was deployed. We will post a final update once we've confirmed stability.