JFrog

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:04 UTC

   We are currently experiencing service disruptions affecting multiple services in our GCP Europe West region. Google Cloud has confirmed an ongoing infrastructure incident affecting network connectivity in the region. Our teams are actively monitoring the situation and...

2. identified 2026-10-20 08:53 UTC

   The service disruption has been linked to an ongoing Google Cloud infrastructure incident affecting multiple services in the Europe West region. Google Cloud is actively investigating the issue. Our teams are continuing to assess the impact and explore mitigation options to...

3. resolved 2026-10-20 12:10 UTC

   All affected services in our GCP Europe West region have been fully restored, and all customers are operating normally. We have validated the recovery and confirmed that service health and availability have returned to normal, with no further issues identified. We will continue...

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-18 07:08 UTC

   We are currently investigating an issue affecting multiple customers in our Azure Southeast Asia region, resulting in degraded Artifactory and Xray services. Our engineering teams are actively investigating the issue and working to restore normal service as soon as possible.

2. identified 2026-10-18 08:03 UTC

   We have identified an issue affecting Artifactory and Xray services in our Azure Southeast Asia region during scheduled Microsoft Azure maintenance. Our engineering teams are actively working with Microsoft Azure Support to investigate the disruption and restore normal service...

3. resolved 2026-10-18 09:40 UTC

   The issue affecting Artifactory and Xray services in our Azure Southeast Asia region has been resolved. The affected services have been restored, and service health has returned to normal following the recovery of the underlying database infrastructure.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-10-09 22:50 UTC

   We are currently investigating an issue impacting JFrog Platform Our team is actively working to identify the root cause and implement a resolution. We will provide an update in 30 minutes. Thank you for your patience.

2. monitoring 2026-10-09 23:05 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-10-09 23:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Security - Xray, Security - JAS, Security - Curation, Security - Catalog

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-08 11:13 UTC

   During emergency database maintenance in our Azure US East region, we encountered unexpected issues affecting Xray services for approximately 119 customers. We are working closely with Microsoft Azure Support to restore service as soon as possible. We will provide further...

2. monitoring 2026-10-08 12:42 UTC

   The database maintenance issue has been addressed, and Xray services in the Azure US East region are recovering. We are closely monitoring the affected services to ensure they are stable and operating as expected.

3. resolved 2026-10-08 13:13 UTC

   The database recovery has been completed successfully, and Xray services in the Azure US East region have been fully restored. All affected services are operating normally, and the issue is now resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-09-30 19:07 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2026-09-30 21:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. resolved 2026-09-29 08:00 UTC

   We identified an issue affecting Artifactory upload and download functionality for some customers hosted in the Google Cloud Platform (GCP) US Central, US West, and Europe West regions The investigation indicates the issue originated with our cloud provider, Google Cloud....

Excerpts are shortened. Read the full incident on JFrog's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-24 05:30 UTC

   A subset of customers may have faced UI errors in the Packages page, the problem was detected and mitigated in realtime.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-08-05 13:14 UTC

   We are investigating cases of degraded performance for JFrog Cloud Platform customers. We will provide more details within the next hour.

2. resolved 2026-08-05 13:21 UTC

   The issue has been resolved. The service disruption lasted approximately nine minutes, during which some Artifactory services were temporarily unavailable. All affected services have fully recovered and are operating normally. The environment is healthy, and our monitoring...

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. resolved 2026-08-04 13:24 UTC

   The issue affecting some JFrog Cloud Platform customers in the Azure EU West region has been resolved. During the incident, some customers may have experienced a brief service interruption. Our team investigated the issue, validated service stability and continues to monitor the...

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network connectivity – Issues accessing resources in West US.

1. investigating 2026-07-23 15:04 UTC

   We are currently investigating this issue.

2. identified 2026-07-23 15:55 UTC

   Several backend services in Azure are reporting outages, we're working with them to recover.

3. monitoring 2026-07-23 18:44 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-23 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-12 10:45 UTC

   We are investigating a potential service disruption affecting JFrog Xray across all regions. A subset of customers may experience authentication errors or failures when accessing Xray and performing Xray-related operations. Our engineering teams are actively working to restore...

2. resolved 2026-07-12 12:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-06-10 05:32 UTC

   GCP (Cloud Provider) , is currently experiencing an issue with their Object Storage infrastructure, which is affecting Artifactory upload and download operations in the US regions. JFrog engineers are actively monitoring the situation and working closely with GCP toward a...

2. identified 2026-06-10 05:43 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-06-10 06:20 UTC

   The service degradation affecting Artifactory uploads and downloads in the GCP US regions has been resolved. JFrog Engineers are continuing to monitor the service health closely.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-21 06:04 UTC

   We are currently investigating an infrastructure issue in the AWS US East region that may impact a limited number of customers. Our engineering team is actively working to restore full service.

2. resolved 2026-05-21 06:35 UTC

   The issue has been resolved. All services in the AWS US East region are fully operational. JFrog Engineers are continuing to monitor to ensure stability.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-20 10:35 UTC

   JFrog Engineering Team is investigating a network issue which impacted a subset of customers in AWS US West region The services are being recovered

2. monitoring 2026-05-20 11:01 UTC

   The network issue has been resolved & all the customers' services have been recovered. JFrog Engineers are continuing to monitor the service stability.

3. resolved 2026-05-21 06:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-08 01:21 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-05-08 05:07 UTC

   Services have auto-recovered basis our high-availability setup and additional configuration enhancements. JFrog engineers remain on standby monitoring the situation closely until AWS fully resolves the underlying Availability Zone impact.

3. resolved 2026-05-11 04:16 UTC

   This incident was resolved at May 8 5.30am UTC

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Control plane issues in East US.

1. identified 2026-04-24 15:39 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-04-24 16:45 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-24 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-04-22 17:03 UTC

   We are currently investigating this issue.

2. identified 2026-04-22 17:25 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-22 17:30 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-22 17:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

Started during AWS: Multiple services (UAE): Region Availability.

1. monitoring 2026-03-02 08:29 UTC

   JFrog engineers are currently investigating & actively monitoring potential performance impact on the JFrog Cloud Platform in the UAE (Middle East) region due to an ongoing AWS datacenter issue. For AWS Status Updates , Please refer - https://health.aws.amazon.com/health/status

2. resolved 2026-03-18 11:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Power event impacting multiple services – West US.

1. identified 2026-02-07 08:33 UTC

   Summary: We are currently experiencing a partial service disruption affecting customers in the Azure US West region. This is due to underlying compute issues at the Microsoft Azure infrastructure layer. Action: JFrog Engineers are actively working to mitigate the impact and...

2. identified 2026-02-07 08:56 UTC

   Microsoft Azure engineering is actively working on restoring services at the infrastructure layer. JFrog Engg Team is monitoring the progress closely as they address the underlying compute failure. Official Microsoft outage details and status updates can be tracked at:...

3. identified 2026-02-07 10:52 UTC

   JFrog Engg have recovered Artifactory services for all customers in the region Azure US West region. Azure Infrastructure is still not fully stable & Microsoft Team is continuing to work on it.

4. resolved 2026-02-07 15:26 UTC

   Status: Resolved / Post-Recovery Validation Impact: Services Restored JFrog services are now fully operational following the resolution of a significant upstream infrastructure outage within Azure. Our internal automated monitoring confirms that all our core functionalities have...

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: JFrog Connect

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-22 08:51 UTC

   JFrog Engineers are currently investigating an issue causing some devices to appear as offline or disconnected in the dashboard. Our engineering team is actively working on the resolution. Service functionality remains a priority and we will provide a follow-up as soon as we...

2. resolved 2025-12-24 08:44 UTC

   JFrog engineers have applied the fix and all devices are verified to be reporting status accurately.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, US - MyJFrog - JFrog Customer Portal, JFrog Connect

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-11 17:34 UTC

   Identified: We are currently experiencing an issue where a subset of customers are encountering upload failures resulting in HTTP 406 error responses. We have identified the root cause as a false positive within our Web Application Firewall (WAF). We are currently evaluating the...

2. resolved 2025-12-11 19:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2025-11-11 00:29 UTC

   Due to a database maintenance, a brief outage may be experienced by some JFrog Cloud Platform customers.

2. investigating 2025-11-11 00:55 UTC

   We are currently investigating this issue.

3. monitoring 2025-11-11 01:59 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-11 02:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:42 UTC

   We are currently investigating this issue.

2. investigating 2025-10-20 08:01 UTC

   Service disruption confirmed to be caused by an issue with the AWS Cloud vendor. JFrog Engg teams are engaged, analyzing the vendor's progress, and monitoring service stability

3. monitoring 2025-10-20 09:45 UTC

   AWS are resuming their services and we see a positive impact on JFrog services. SLO is almost 100% and all Artifactory transactions have been resumed. We are still monitoring the systems health. AWS Incident status chronology can be referred here:...

4. resolved 2025-10-20 10:57 UTC

   All services are up and running - see also https://health.aws.amazon.com/health/status

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Web UI

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2025-10-10 17:26 UTC

   JFrog Engineers are actively investigating this event and will shortly update

2. monitoring 2025-10-10 17:50 UTC

   JFrog engineers have identified the root cause to the recent brief Azure Cloud service unavailability. All customer services have since recovered and are stable. We have engaged Azure engineering to conduct a deeper analysis and will continue to monitor the stability of the...

3. resolved 2025-10-10 18:19 UTC

   All customer services are fully functional and have remained stable for a substantial period.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Security - Xray

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2025-09-07 12:42 UTC

   Due to a database maintenance JFrog customers could experience a brief outage for some JFrog Cloud Platform customers.

2. identified 2025-09-07 12:52 UTC

   Issue has been identified and we are working with Azure to resolve the issue

3. identified 2025-09-07 12:54 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2025-09-07 13:04 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-09-07 13:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-08-06 03:52 UTC

   We are currently investigating this issue.

2. monitoring 2025-08-06 03:53 UTC

   We are investigating a brief service disruption in the GCP Central region caused by a cloud provider network issue All services are up & running stable now & we are continuing to monitor the service health

3. resolved 2025-08-06 05:17 UTC

   Cloud Provider has confirmed that the issue has been resolved. No further service disruptions were observed since the last update.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, US - MyJFrog - JFrog Customer Portal, JFrog Connect

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-14 13:40 UTC

   We are investigating cases of degraded UI performance for JFrog Cloud Platform customers. We will provide more details within the next hour.

2. identified 2025-07-14 13:41 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2025-07-14 13:42 UTC

   We have identified and resolved the UI issue on JFrog Platform UI

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-07-07 13:43 UTC

   We are currently experiencing service degradation affecting JFrog Artifactory customers who utilise Terraform in their workflows. Users may encounter build failures during this time. JFrog Engineering teams has successfully identified the root cause of the issue and is actively...

2. resolved 2025-07-07 15:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: JFrog Connect

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-06-25 10:00 UTC

   JFrog Connect experienced a momentary outage of device status - devices appeared as offline for 15 minutes.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-06-12 18:42 UTC

   Multiple customers across multiple JFrog's GCP regions are experiencing an outage due to a GCP global outage

2. identified 2025-06-12 19:05 UTC

   Google Cloud Platform report a major outage for Storage, affecting Artifactory's uploads and downloads. ETA for their next update is within the close half an hour.

3. identified 2025-06-12 19:09 UTC

   We're impacted by a global outage affecting Google Cloud's multi-regional services. This incident has been identified by GCP and they are actively working on rolling out an emergency patch to restore service. For real-time updates from Google Cloud, pls refer to:...

4. monitoring 2025-06-12 19:33 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2025-06-12 20:38 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-06-12 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-05-30 19:06 UTC

   Due to an unplanned infrastructure anomaly, an internal network was affected and a subset of US West 2 customers experienced a loss of connection to the platform. Currently all the services are back online

2. resolved 2025-05-30 19:39 UTC

   All Services are back online & fully operational

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2025-05-28 08:51 UTC

   We are investigating cases of degraded performance for JFrog Cloud Platform customers on Azure. We will provide more details within the next hour.

2. identified 2025-05-28 10:20 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-05-28 10:24 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2025-05-28 15:51 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-05-28 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-05-03 08:36 UTC

   We are going to perform some critical database maintenance which could result in a brief outage of up to 10 minute for some JFrog Cloud Platform customers.

2. monitoring 2025-05-03 08:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-03 08:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-01 13:50 UTC

   We are investigating cases of degraded performance for JFrog Cloud Platform customers. This is limited to a specific flow affecting the Set Me Up flow to generate a token affecting JFrog customers. We will provide more details within the next hour.

2. resolved 2025-04-02 14:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-19 14:08 UTC

   We are investigating an availability issue that is impacting some JFrog Connect Cloud Platform customers. The direct login to Connect is currently down. Our team is actively working to resolve the issue as quickly as possible. In the meantime, we recommend that you log in to...

2. identified 2025-03-19 14:08 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-03-19 14:12 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2025-03-20 10:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Web UI, Web UI, Web UI

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-05 13:49 UTC

   We are investigating an availability issue that is impacting some JFrog Cloud Platform customers. Should Impact only UI logins. We will provide more details within the next hour.

2. monitoring 2025-03-05 14:35 UTC

   A fix has been implemented and we are monitoring the results.

3. investigating 2025-03-05 14:35 UTC

   We are currently investigating this issue.

4. monitoring 2025-03-05 14:36 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-03-05 14:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-01-13 18:34 UTC

   A subset of customers in AWS US West 2 have experienced intermittent disruptions.

2. monitoring 2025-01-13 19:52 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-01-13 20:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2024-12-31 02:41 UTC

   We are currently investigating this issue.

2. monitoring 2024-12-31 06:44 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2024-12-31 07:50 UTC

   We are continuing to monitor for any further issues.

4. resolved 2024-12-31 08:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - Xray, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - JAS, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Curation, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Catalog, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Security - Runtime, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, Webhook, US - MyJFrog - JFrog Customer Portal

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-12-22 13:08 UTC

   We are investigating an availability issue that is impacting JFrog Cloud Platform customers. We will provide more details within the next hour.

2. identified 2024-12-22 13:27 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-12-22 14:29 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-12-22 14:38 UTC

   All services are are up and running and JFrog will provide the required root cause analysis upon request

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2024-12-20 03:24 UTC

   We are currently investigating the issue!

2. monitoring 2024-12-20 03:38 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-12-20 03:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-03 13:17 UTC

   We are going to perform some critical maintenance on our infrastructure layer. This is a proactive maintenance as recommended by the cloud provider. which could result in a brief outage of up to 10 minute for some JFrog Cloud Platform customers.

2. resolved 2024-11-03 13:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Security - Xray, Security - Xray, Security - JAS, Security - JAS, Security - JAS

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-31 13:17 UTC

   We are investigating cases of degraded performance for JFrog Cloud Platform customers. We will provide more details within the next hour.

2. monitoring 2024-10-31 13:59 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-10-31 14:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-07-03 12:25 UTC

   We are currently investigating this issue.

2. identified 2024-07-03 12:26 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2024-07-03 12:33 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2024-07-03 13:21 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2024-07-03 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Distribution, Pipelines

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-05-05 05:12 UTC

   JFrog Cloud Platform may experience short service disruption due to planned maintenance on Tokyo (prod-apne-1) region

2. resolved 2024-05-05 06:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2024-05-01 17:31 UTC

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

2. resolved 2024-05-01 18:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Distribution, Pipelines

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-03-28 16:38 UTC

   We are currently investigating this issue.

2. identified 2024-03-28 16:38 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2024-03-28 21:54 UTC

   All services operational

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-27 14:41 UTC

   We are investigating an availability issue that is impacting some JFrog Cloud Platform customers. We will provide more details within the next hour.

2. resolved 2024-03-27 16:43 UTC

   This incident has been resolved, after identifying and resolving our frontend application limitation

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Distribution, Pipelines

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2024-03-27 12:46 UTC

   We are investigating an availability issue that is impacting some JFrog Cloud Platform customers on Azure US East. We will provide more details within the next hour.

2. identified 2024-03-27 13:11 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2024-03-27 14:39 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2024-03-27 16:34 UTC

   A fix was applied a while ago, all the services were observed to be stable and fully operational. Incident stands resolved

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Artifactory, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Distribution, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, US - MyJFrog - JFrog Customer Portal

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-03-23 22:35 UTC

   JFrog will be performing a general maintenance for MyJFrog portal. During this period, MyJFrog portal and new registrations will not be available. JFrog Cloud Platform will not be affected and all existing services will remain operational.

2. resolved 2024-03-24 08:01 UTC

   Planned maintenance for MyJFrog portal is done.

Excerpts are shortened. Read the full incident on JFrog's status page.

Affected: Distribution, Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-03-13 09:52 UTC

   We are investigating an availability issue that has impacted some JFrog Cloud Platform customers. We will provide more details within the next hour.

2. identified 2024-03-13 11:00 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2024-03-13 11:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JFrog's status page.