Historial de interrupciones de Jfrog

1. August 5, 2026 at 1:14 PM UTCinvestigating

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

2. August 5, 2026 at 1:21 PM UTCresolved

   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 confirms continued stability.

1. August 4, 2026 at 1:55 PM UTCresolved

   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 environment to ensure normal operation.

1. July 23, 2026 at 3:04 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 23, 2026 at 3:55 PM UTCidentified

   Varios servicios de backend en Azure están reportando interrupciones, estamos trabajando con ellos para recuperarse.

3. July 23, 2026 at 6:44 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 23, 2026 at 8:32 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 12, 2026 at 10:45 AM UTCinvestigating

   Estamos investigando una posible perturbación del servicio que afecta a JFrog Xray en todas las regiones. Un subconjunto de clientes puede experimentar errores de autenticación o fallos al acceder a rayos X y realizar operaciones relacionadas con rayos X. Nuestros equipos de ingeniería están trabajando activamente para restaurar el servicio normal. Proporcionaremos otra actualización dentro de la hora siguiente.

2. July 12, 2026 at 11:03 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 10, 2026 at 5:32 AM UTCidentified

   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 resolution.

2. June 10, 2026 at 5:43 AM UTCidentified

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

3. June 10, 2026 at 6:20 AM UTCresolved

   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.

1. May 21, 2026 at 6:04 AM UTCinvestigating

   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. May 21, 2026 at 6:35 AM UTCresolved

   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.

1. May 20, 2026 at 10:35 AM UTCidentified

   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. May 20, 2026 at 11:01 AM UTCmonitoring

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

3. May 21, 2026 at 6:01 AM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 1:21 AM UTCidentified

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

2. May 8, 2026 at 5:07 AM UTCmonitoring

   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. May 11, 2026 at 4:16 AM UTCresolved

   This incident was resolved at May 8 5.30am UTC

1. April 24, 2026 at 3:39 PM UTCidentified

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

2. April 24, 2026 at 4:45 PM UTCmonitoring

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

3. April 24, 2026 at 6:05 PM UTCresolved

   This incident has been resolved.

1. April 22, 2026 at 5:03 PM UTCinvestigating

   We are currently investigating this issue.

2. April 22, 2026 at 5:25 PM UTCidentified

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

3. April 22, 2026 at 5:30 PM UTCmonitoring

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

4. April 22, 2026 at 5:59 PM UTCresolved

   This incident has been resolved.

1. March 2, 2026 at 8:29 AM UTCmonitoring

   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. March 18, 2026 at 11:40 AM UTCresolved

   This incident has been resolved.

1. February 7, 2026 at 8:33 AM UTCidentified

   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 recover services.

2. February 7, 2026 at 8:56 AM UTCidentified

   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: https://app.azure.com/h/JLPW-7W8/86af1b

3. February 7, 2026 at 10:52 AM UTCidentified

   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. February 7, 2026 at 3:26 PM UTCresolved

   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 returned to expected performance levels. Recovery & Ongoing Validation While primary connectivity and service layers have been restored, the JFrog engineering team remains in an active monitoring phase. We are currently performing comprehensive validations across all Azure services including storage and compute components. This process ensures that all dependent systems have achieved full synchronization and are performing at optimal capacity. Incident Timeline (UTC) 12:30 UTC: The infrastructure provider confirmed the restoration of facility power and physical network connectivity. Subsequent Window: Azure Cloud services were recovered, enabling the sequential restoration and stabilization of the JFrog service layers. For further technical details regarding the root cause of the underlying infrastructure failure, please refer to the official Azure Status Page - https://azure.status.microsoft/en-us/status

1. December 22, 2025 at 8:51 AM UTCinvestigating

   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. December 24, 2025 at 8:44 AM UTCresolved

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

1. December 11, 2025 at 5:34 PM UTCidentified

   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. December 11, 2025 at 7:24 PM UTCresolved

   This incident has been resolved.

1. November 11, 2025 at 12:29 AM UTCidentified

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

2. November 11, 2025 at 12:55 AM UTCinvestigating

   We are currently investigating this issue.

3. November 11, 2025 at 1:59 AM UTCmonitoring

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

4. November 11, 2025 at 2:31 AM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 7:42 AM UTCinvestigating

   We are currently investigating this issue.

2. October 20, 2025 at 8:01 AM UTCinvestigating

   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. October 20, 2025 at 9:45 AM UTCmonitoring

   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. October 20, 2025 at 10:57 AM UTCresolved

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

1. October 10, 2025 at 5:26 PM UTCinvestigating

   JFrog Engineers are actively investigating this event and will shortly update

2. October 10, 2025 at 5:50 PM UTCmonitoring

   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. October 10, 2025 at 6:19 PM UTCresolved

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

1. September 7, 2025 at 12:42 PM UTCidentified

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

2. September 7, 2025 at 12:52 PM UTCidentified

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

3. September 7, 2025 at 12:54 PM UTCidentified

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

4. September 7, 2025 at 1:04 PM UTCmonitoring

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

5. September 7, 2025 at 1:39 PM UTCresolved

   This incident has been resolved.

1. August 6, 2025 at 3:52 AM UTCinvestigating

   We are currently investigating this issue.

2. August 6, 2025 at 3:53 AM UTCmonitoring

   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. August 6, 2025 at 5:17 AM UTCresolved

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

1. July 14, 2025 at 1:40 PM UTCinvestigating

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

2. July 14, 2025 at 1:41 PM UTCidentified

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

3. July 14, 2025 at 1:42 PM UTCresolved

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