StepSecurity Outage History

StepSecurity is up right now

Pingoru has recorded 2 incidents for StepSecurity: 2 in the last 12 months and 2 in the last 90 days.

Source: status.stepsecurity.io

2incidents recorded
2last 12 months
2last 90 days
7 hourstypical duration

Incidents, newest first

Minor September 28, 2026 Some npm packages may return incorrect download URLs, causing installation failures. 43m Secure Registry (Secure Registry)

Started Sep 28, 2026, 06:44 PM UTC· resolved Sep 28, 2026, 07:27 PM UTC

  1. investigating Sep 28, 2026, 06:44 PM UTC

    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.

  2. resolved Sep 28, 2026, 07:27 PM UTC

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

Read the full incident report →

Minor September 3, 2026 Elevated 502 Errors on StepSecurity Secure Registry 13h 41m Secure Registry (Secure Registry)

Started Sep 03, 2026, 06:32 PM UTC· resolved Sep 04, 2026, 08:13 AM UTC

  1. investigating Sep 03, 2026, 06:32 PM UTC

    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.

  2. resolved Sep 04, 2026, 08:13 AM UTC

    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.

Read the full incident report →