- Level
- confirmed
- Worst impact
- Maintenance
- Components
- Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook
- Regions
- us
Summary
JFrog says Azure is performing region-wide maintenance on Azure Database for PostgreSQL instances in West US, and it is now in progress. Customers in the impacted regions may experience a service interruption of less than 5 minutes.
Written by anthropic/claude-haiku-5.5 from JFrog's own updates.
What to do
Check whether you use JFrog Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Check that everything you run on JFrog came back after the window closed 2026-11-08 08:05 UTC.
Subscribe to JFrog's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=jfrog works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from JFrog 3
- scheduled
MSFT Azure will be performing a region wide maintenance of Azure Database for PostgreSQL instance(s). During the maintenance timeframe customers in the impacted regions may experience a short service interruption (less than 5 mins).
provider
- scheduled
Maintenance will begin as scheduled in 60 minutes.
provider
- in_progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f8845517c6
Is this JFrog maintenance still going on?
No, it ended 2026-11-08 08:05 UTC.
How long did it last?
1h 6m, from 2026-11-08 07:00 UTC to 2026-11-08 08:05 UTC, by the times JFrog posted.
What was affected?
JFrog named Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more in us.
What caused it?
JFrog hasn't published a root cause. If it does, it shows here.
Where does this come from?
JFrog's official status page, https://status.jfrog.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.