Home
/
Status
/
Service
Software supply chain platform for DevOps and security.
Source
auto
Category
Security
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 28m ago
442
Components
0
Active incidents
0
Maintenance
0%
90d uptime
JFrog Cloud Platform outage affecting subset of customers in GCP US region
Jun 10, 5:32 AM
Normalized official status-page data for incidents, maintenance, components, and history.
0%
Known uptime
27 known history days
442
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
60
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Artifactory
Operational
Artifactory
Operational
Artifactory
Operational
Distribution
Operational
Europe - West (Netherlands) - Azure
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
0
operational days
0
degraded days
6
outage days
21
maintenance days
63
unknown days
Latest outages and degradations detected from the official status page.
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.
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.
This incident has been resolved.
This incident was resolved at May 8 5.30am UTC
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
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
JFrog engineers have applied the fix and all devices are verified to be reporting status accurately.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Jfrog status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
http://status.artifactoryonline.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 442 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
US - East1 (N. Virginia) - AWS p-aws-prod-use1 | Operational | Group | 6/15/2026 |
US - EAST2 (Ohio) - AWS p-aws-prod-use2 | Operational | Group | 6/17/2026 |
US - West1 (California) - AWS p-aws-prod-usw1 | Operational | Group | Not recorded |
US - West2 (Oregon) - AWS p-aws-prod-usw2 | Operational | Group | 6/21/2026 |
US - East (Virginia) - Azure p-azure-prod-use | Operational | Group | Not recorded |
US - West (California) - Azure p-azure-prod-usw | Operational | Group | Not recorded |
US - West3 (Arizona) - Azure p-azure-prod-usw3 | Operational | Group | Not recorded |
US - East1 (S. Carolina) - GCP p-gcp-prod-use1 | Operational | Group | Not recorded |
US - East1 (S. Carolina) - OSS - GCP p-gcp-prod-oss-use1 | Operational | Group | Not recorded |
US - Central1 (Iowa) - GCP p-gcp-prod-usc1 | Operational | Group | 6/21/2026 |
US - West1 (Oregon) - GCP p-gcp-prod-usw1 | Operational | Group | Not recorded |
US - West2(Los Angeles) - GCP p-gcp-prod-usw2 | Operational | Group | 6/21/2026 |
US - East4 (N. Virginia) - GCP p-gcp-prod-use4 | Operational | Group | 6/21/2026 |
US - South Central (Texas) - Azure p-azure-prod-ussc | Operational | Group | Not recorded |
US - Central (lowa) - Azure p-azure-prod-usc | Operational | Group | Not recorded |
US - North Central US (Illinois) - Azure p-azure-prod-usnc | Operational | Group | Not recorded |
CANADA - Central - AWS p-aws-prod-cac1 | Operational | Group | Not recorded |
CANADA - Central (Toronto) - Azure p-azure-prod-cac | Operational | Group | Not recorded |
South America - Brazil (São Paulo) - AWS p-aws-prod-sae1 | Operational | Group | 6/14/2026 |
South America - Brazil South (São Paulo) - Azure p-azure-prod-brs | Operational | Group | Not recorded |
Europe - Central1 (Frankfurt) - AWS p-aws-prod-euc1 | Operational | Group | Not recorded |
Europe - West1 (Ireland) - AWS p-aws-prod-euw1 | Operational | Group | 6/21/2026 |
Europe - West2 (London) - AWS p-aws-prod-euw2 | Operational | Group | Not recorded |
Europe - West (Netherlands) - Azure p-azure-prod-euw | Operational | Group | 6/21/2026 |
Europe - West2 (London) - GCP p-gcp-prod-euw2 | Operational | Group | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Jfrog is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
