JFrog incident

JFrog Pipelines on AWS may experience service disruption due to Infrastructure upgrades

Minor Resolved View vendor source →

JFrog experienced a minor incident on May 1, 2024 affecting Pipelines and Pipelines and 1 more component, lasting 1h 27m. The incident has been resolved; the full update timeline is below.

Started
May 01, 2024, 05:31 PM UTC
Resolved
May 01, 2024, 06:59 PM UTC
Duration
1h 27m
Detected by Pingoru
May 01, 2024, 05:31 PM UTC

Affected components

PipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelines

Update timeline

  1. identified May 01, 2024, 05:31 PM UTC

    Pipelines users in AWS who rely on the default SaaS buildplane node pools are temporarily unavailable. Custom node pools unaffected.

  2. resolved May 01, 2024, 06:59 PM UTC

    This incident has been resolved.