Störungsverlauf von Jfrog

1. 5. August 2026 um 13:14 UTCinvestigating

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

2. 5. August 2026 um 13:21 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. 4. August 2026 um 13:55 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. 23. Juli 2026 um 15:04 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 23. Juli 2026 um 15:55 UTCidentified

   Mehrere Backend-Dienste in Azure melden Ausfälle, wir arbeiten mit ihnen zusammen, um sie wiederherzustellen.

3. 23. Juli 2026 um 18:44 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 23. Juli 2026 um 20:32 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juli 2026 um 10:45 UTCinvestigating

   Wir untersuchen eine mögliche Serviceunterbrechung, die JFrog Xray in allen Regionen betrifft. Eine Teilmenge von Kunden kann beim Zugriff auf Xray und bei der Durchführung von Xray-bezogenen Vorgängen Authentifizierungsfehler oder -fehler aufweisen. Unsere Ingenieurteams arbeiten aktiv daran, den normalen Service wiederherzustellen. Wir werden innerhalb der nächsten Stunde ein weiteres Update bereitstellen.

2. 12. Juli 2026 um 11:03 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juni 2026 um 05:32 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. 10. Juni 2026 um 05:43 UTCidentified

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

3. 10. Juni 2026 um 06:20 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. 21. Mai 2026 um 06:04 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. 21. Mai 2026 um 06:35 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. 20. Mai 2026 um 10:35 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. 20. Mai 2026 um 11:01 UTCmonitoring

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

3. 21. Mai 2026 um 06:01 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 01:21 UTCidentified

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

2. 8. Mai 2026 um 05:07 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. 11. Mai 2026 um 04:16 UTCresolved

   This incident was resolved at May 8 5.30am UTC

1. 24. April 2026 um 15:39 UTCidentified

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

2. 24. April 2026 um 16:45 UTCmonitoring

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

3. 24. April 2026 um 18:05 UTCresolved

   This incident has been resolved.

1. 22. April 2026 um 17:03 UTCinvestigating

   We are currently investigating this issue.

2. 22. April 2026 um 17:25 UTCidentified

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

3. 22. April 2026 um 17:30 UTCmonitoring

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

4. 22. April 2026 um 17:59 UTCresolved

   This incident has been resolved.

1. 2. März 2026 um 08:29 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. 18. März 2026 um 11:40 UTCresolved

   This incident has been resolved.

1. 7. Februar 2026 um 08:33 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. 7. Februar 2026 um 08:56 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. 7. Februar 2026 um 10:52 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. 7. Februar 2026 um 15:26 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. 22. Dezember 2025 um 08:51 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. 24. Dezember 2025 um 08:44 UTCresolved

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

1. 11. Dezember 2025 um 17:34 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. 11. Dezember 2025 um 19:24 UTCresolved

   This incident has been resolved.

1. 11. November 2025 um 00:29 UTCidentified

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

2. 11. November 2025 um 00:55 UTCinvestigating

   We are currently investigating this issue.

3. 11. November 2025 um 01:59 UTCmonitoring

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

4. 11. November 2025 um 02:31 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 07:42 UTCinvestigating

   We are currently investigating this issue.

2. 20. Oktober 2025 um 08:01 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. 20. Oktober 2025 um 09:45 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. 20. Oktober 2025 um 10:57 UTCresolved

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

1. 10. Oktober 2025 um 17:26 UTCinvestigating

   JFrog Engineers are actively investigating this event and will shortly update

2. 10. Oktober 2025 um 17:50 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. 10. Oktober 2025 um 18:19 UTCresolved

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

1. 7. September 2025 um 12:42 UTCidentified

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

2. 7. September 2025 um 12:52 UTCidentified

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

3. 7. September 2025 um 12:54 UTCidentified

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

4. 7. September 2025 um 13:04 UTCmonitoring

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

5. 7. September 2025 um 13:39 UTCresolved

   This incident has been resolved.

1. 6. August 2025 um 03:52 UTCinvestigating

   We are currently investigating this issue.

2. 6. August 2025 um 03:53 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. 6. August 2025 um 05:17 UTCresolved

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

1. 14. Juli 2025 um 13:40 UTCinvestigating

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

2. 14. Juli 2025 um 13:41 UTCidentified

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

3. 14. Juli 2025 um 13:42 UTCresolved

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