JFrog Outage History

JFrog is up right now

JFrog had 30 outages in the last 2 years totaling 615h 25m of downtime — averaging 1.2 incidents per month.

There were 30 JFrog outages since July 3, 2024 totaling 615h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.artifactoryonline.com

Critical May 21, 2026

JFrog Cloud Platform outage affecting subset of customers in AWS US East region

Detected by Pingoru
May 21, 2026, 06:04 AM UTC
Resolved
May 21, 2026, 06:35 AM UTC
Duration
31m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 2 updates
  1. investigating May 21, 2026, 06:04 AM 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 May 21, 2026, 06:35 AM 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.

Read the full incident report →

Notice May 20, 2026

JFrog Cloud Platform outage affecting subset of customers in AWS US West region

Detected by Pingoru
May 20, 2026, 10:35 AM UTC
Resolved
May 21, 2026, 06:01 AM UTC
Duration
19h 26m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 3 updates
  1. identified May 20, 2026, 10:35 AM 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 May 20, 2026, 11:01 AM 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 May 21, 2026, 06:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

JFrog platform services degradation affecting a subset of AWS US East 1 customers due to AWS infrastructure issues

Detected by Pingoru
May 08, 2026, 01:21 AM UTC
Resolved
May 11, 2026, 04:16 AM UTC
Duration
3d 2h
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionWeb UIWebhook
Timeline · 3 updates
  1. identified May 08, 2026, 01:21 AM UTC

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

  2. monitoring May 08, 2026, 05:07 AM 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 May 11, 2026, 04:16 AM UTC

    This incident was resolved at May 8 5.30am UTC

Read the full incident report →

Minor April 24, 2026

JFrog platform services outage affecting a subset of Azure customers in US East

Detected by Pingoru
Apr 24, 2026, 03:39 PM UTC
Resolved
Apr 24, 2026, 06:05 PM UTC
Duration
2h 25m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 3 updates
  1. identified Apr 24, 2026, 03:39 PM UTC

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

  2. monitoring Apr 24, 2026, 04:45 PM UTC

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

  3. resolved Apr 24, 2026, 06:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026

JFrog platform services outage affecting a subset of AWS customers due to AWS infrastructure issues

Detected by Pingoru
Apr 22, 2026, 05:03 PM UTC
Resolved
Apr 22, 2026, 05:59 PM UTC
Duration
56m
Affected: Artifactory
Timeline · 4 updates
  1. investigating Apr 22, 2026, 05:03 PM UTC

    We are currently investigating this issue.

  2. identified Apr 22, 2026, 05:25 PM UTC

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

  3. monitoring Apr 22, 2026, 05:30 PM UTC

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

  4. resolved Apr 22, 2026, 05:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

JFrog Cloud Platform potential impact due to AWS Datacenter issues in UAE Region

Detected by Pingoru
Mar 02, 2026, 08:29 AM UTC
Resolved
Mar 18, 2026, 11:40 AM UTC
Duration
16d 3h
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 2 updates
  1. monitoring Mar 02, 2026, 08:29 AM 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 Mar 18, 2026, 11:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 22, 2025

JFrog Connect partial disruption with subset of devices appearing offline

Detected by Pingoru
Dec 22, 2025, 08:51 AM UTC
Resolved
Dec 24, 2025, 08:44 AM UTC
Duration
1d 23h
Affected: JFrog Connect
Timeline · 2 updates
  1. investigating Dec 22, 2025, 08:51 AM 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 have more information. We apologize for the interruption.

  2. resolved Dec 24, 2025, 08:44 AM UTC

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

Read the full incident report →

Notice December 11, 2025

Our WAF may block <0.01% of uploads for select customers

Detected by Pingoru
Dec 11, 2025, 05:34 PM UTC
Resolved
Dec 11, 2025, 07:24 PM UTC
Duration
1h 49m
Affected: ArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactorySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookUS - MyJFrog - JFrog Customer PortalJFrog Connect
Timeline · 2 updates
  1. identified Dec 11, 2025, 05:34 PM 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 necessary steps for resolution and updates will follow.

  2. resolved Dec 11, 2025, 07:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 11, 2025

Partial outage in JFrog Cloud Platform Database affecting services on Azure Israel

Detected by Pingoru
Nov 11, 2025, 12:29 AM UTC
Resolved
Nov 11, 2025, 02:31 AM UTC
Duration
2h 2m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 4 updates
  1. identified Nov 11, 2025, 12:29 AM UTC

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

  2. investigating Nov 11, 2025, 12:55 AM UTC

    We are currently investigating this issue.

  3. monitoring Nov 11, 2025, 01:59 AM UTC

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

  4. resolved Nov 11, 2025, 02:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Artifactory Service outage affecting multiple customers across several AWS regions

Detected by Pingoru
Oct 20, 2025, 07:42 AM UTC
Resolved
Oct 20, 2025, 10:57 AM UTC
Duration
3h 15m
Affected: ArtifactoryArtifactoryArtifactoryArtifactory
Timeline · 4 updates
  1. investigating Oct 20, 2025, 07:42 AM UTC

    We are currently investigating this issue.

  2. investigating Oct 20, 2025, 08:01 AM 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 Oct 20, 2025, 09:45 AM 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: https://health.aws.amazon.com/health/status

  4. resolved Oct 20, 2025, 10:57 AM UTC

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

Read the full incident report →

Major October 10, 2025

JFrog Cloud Platform Service disruption affecting a subset of customers in Azure US East region

Detected by Pingoru
Oct 10, 2025, 05:26 PM UTC
Resolved
Oct 10, 2025, 06:19 PM UTC
Duration
53m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionWeb UI
Timeline · 3 updates
  1. investigating Oct 10, 2025, 05:26 PM UTC

    JFrog Engineers are actively investigating this event and will shortly update

  2. monitoring Oct 10, 2025, 05:50 PM 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 services.

  3. resolved Oct 10, 2025, 06:19 PM UTC

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

Read the full incident report →

Major September 7, 2025

Critical JFrog Cloud Platform Database Incident affecting Xray service on Azure USE

Detected by Pingoru
Sep 07, 2025, 12:42 PM UTC
Resolved
Sep 07, 2025, 01:39 PM UTC
Duration
56m
Affected: Security - Xray
Timeline · 5 updates
  1. identified Sep 07, 2025, 12:42 PM UTC

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

  2. identified Sep 07, 2025, 12:52 PM UTC

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

  3. identified Sep 07, 2025, 12:54 PM UTC

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

  4. monitoring Sep 07, 2025, 01:04 PM UTC

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

  5. resolved Sep 07, 2025, 01:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 6, 2025

JFrog Cloud Platform Service Disruption in GCP Central Region

Detected by Pingoru
Aug 06, 2025, 03:52 AM UTC
Resolved
Aug 06, 2025, 05:17 AM UTC
Duration
1h 25m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 3 updates
  1. investigating Aug 06, 2025, 03:52 AM UTC

    We are currently investigating this issue.

  2. monitoring Aug 06, 2025, 03:53 AM 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 Aug 06, 2025, 05:17 AM UTC

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

Read the full incident report →

Minor July 14, 2025

JFrog Cloud Platform degraded UI performance

Detected by Pingoru
Jul 14, 2025, 01:40 PM UTC
Resolved
Jul 14, 2025, 01:42 PM UTC
Duration
2m
Affected: ArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactorySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - XraySecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - JASSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CurationSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - CatalogSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeSecurity - RuntimeDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionDistributionPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesPipelinesWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookWebhookUS - MyJFrog - JFrog Customer PortalJFrog Connect
Timeline · 3 updates
  1. investigating Jul 14, 2025, 01:40 PM 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 Jul 14, 2025, 01:41 PM UTC

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

  3. resolved Jul 14, 2025, 01:42 PM UTC

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

Read the full incident report →

Minor July 7, 2025

Artifactory Service Degraded for JFrog customers using Terraform

Detected by Pingoru
Jul 07, 2025, 01:43 PM UTC
Resolved
Jul 07, 2025, 03:18 PM UTC
Duration
1h 35m
Affected: ArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactory
Timeline · 2 updates
  1. identified Jul 07, 2025, 01:43 PM 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 working on implementing a resolution. We will continue to monitor the situation closely and provide updates as they become available.

  2. resolved Jul 07, 2025, 03:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2025

JFrog Connect was Unavailable For Customers

Detected by Pingoru
Jun 25, 2025, 10:00 AM UTC
Resolved
Jun 25, 2025, 10:00 AM UTC
Duration
—
Affected: JFrog Connect
Timeline · 1 update
  1. resolved Jun 26, 2025, 09:08 AM UTC

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

Read the full incident report →

Notice June 12, 2025

JFrog Google Cloud Platform degraded performance

Detected by Pingoru
Jun 12, 2025, 06:42 PM UTC
Resolved
Jun 12, 2025, 08:39 PM UTC
Duration
1h 56m
Affected: ArtifactoryArtifactoryArtifactory
Timeline · 6 updates
  1. investigating Jun 12, 2025, 06:42 PM UTC

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

  2. identified Jun 12, 2025, 07:05 PM 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 Jun 12, 2025, 07:09 PM 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: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  4. monitoring Jun 12, 2025, 07:33 PM UTC

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

  5. monitoring Jun 12, 2025, 08:38 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 12, 2025, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 30, 2025

JFrog platform services brief outage affecting a subset of AWS US West2 region customers

Detected by Pingoru
May 30, 2025, 07:06 PM UTC
Resolved
May 30, 2025, 07:39 PM UTC
Duration
32m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionWeb UIWebhook
Timeline · 2 updates
  1. monitoring May 30, 2025, 08:28 PM 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 May 30, 2025, 08:30 PM UTC

    All Services are back online & fully operational

Read the full incident report →

Notice May 28, 2025

JFrog Azure Cloud Platform degraded performance

Detected by Pingoru
May 28, 2025, 08:51 AM UTC
Resolved
May 28, 2025, 03:54 PM UTC
Duration
7h 3m
Affected: ArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactoryArtifactory
Timeline · 5 updates
  1. investigating May 28, 2025, 08:51 AM 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 May 28, 2025, 10:20 AM UTC

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

  3. identified May 28, 2025, 10:24 AM UTC

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

  4. monitoring May 28, 2025, 03:51 PM UTC

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

  5. resolved May 28, 2025, 03:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 1, 2025

JFrog Cloud Platform users might experience broken Set Me Up flow affecting subset of JFrog customers

Detected by Pingoru
Apr 01, 2025, 01:50 PM UTC
Resolved
Apr 02, 2025, 02:47 PM UTC
Duration
1d
Affected: Web UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UIWeb UI
Timeline · 2 updates
  1. investigating Apr 01, 2025, 01:50 PM 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 Apr 02, 2025, 02:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 19, 2025

JFrog Cloud Connect Platform Login is Unavailable For Customers

Detected by Pingoru
Mar 19, 2025, 02:08 PM UTC
Resolved
Mar 20, 2025, 10:57 AM UTC
Duration
20h 48m
Timeline · 4 updates
  1. investigating Mar 19, 2025, 02:08 PM 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 Artifactory and access Connect through the link provided there.

  2. identified Mar 19, 2025, 02:08 PM UTC

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

  3. identified Mar 19, 2025, 02:12 PM UTC

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

  4. resolved Mar 20, 2025, 10:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 5, 2025

JFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues

Detected by Pingoru
Mar 05, 2025, 01:49 PM UTC
Resolved
Mar 05, 2025, 02:42 PM UTC
Duration
52m
Affected: Web UIWeb UIWeb UI
Timeline · 5 updates
  1. investigating Mar 05, 2025, 01:49 PM 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 Mar 05, 2025, 02:35 PM UTC

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

  3. investigating Mar 05, 2025, 02:35 PM UTC

    We are currently investigating this issue.

  4. monitoring Mar 05, 2025, 02:36 PM UTC

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

  5. resolved Mar 05, 2025, 02:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 13, 2025

JFrog services intermittent degradation affecting a subset of customers in AWS US West 2 region

Detected by Pingoru
Jan 13, 2025, 06:34 PM UTC
Resolved
Jan 13, 2025, 08:15 PM UTC
Duration
1h 40m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 3 updates
  1. investigating Jan 13, 2025, 07:32 PM UTC

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

  2. monitoring Jan 13, 2025, 07:45 PM UTC

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

  3. resolved Jan 13, 2025, 08:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 31, 2024

JFrog platform services outage affecting a subset of customers in Azure US East region due to infrastructure issues

Detected by Pingoru
Dec 31, 2024, 02:41 AM UTC
Resolved
Dec 31, 2024, 08:03 AM UTC
Duration
5h 22m
Affected: ArtifactorySecurity - XraySecurity - JASSecurity - CurationSecurity - CatalogSecurity - RuntimeDistributionPipelinesWeb UIWebhook
Timeline · 4 updates
  1. investigating Dec 31, 2024, 02:41 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 31, 2024, 06:44 AM UTC

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

  3. monitoring Dec 31, 2024, 07:50 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 31, 2024, 08:03 AM UTC

    This incident has been resolved.

Read the full incident report →