Live

JFrog

JFrog is reporting maintenance

Checked 54 s ago Maintenance

Service Under Maintenance

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

8

Median duration

2 h

Longest incident

6 h 6 min

Components

402

US - East1 (N. Virginia) - AWS

Artifactory Operational
90 days ago2 days with an incidentToday
Security - Xray Operational
90 days ago1 day with an incidentToday
Security - JAS Operational
90 days ago1 day with an incidentToday
Security - Curation Operational
90 days ago1 day with an incidentToday
Security - Catalog Operational
90 days ago1 day with an incidentToday
Security - Runtime Operational
90 days ago1 day with an incidentToday
Distribution Operational
90 days ago1 day with an incidentToday
Pipelines Operational
90 days ago1 day with an incidentToday
Web UI Operational
90 days ago1 day with an incidentToday
Webhook Operational
90 days ago1 day with an incidentToday

US - West1 (California) - AWS

Artifactory Operational
90 days ago1 day with an incidentToday
Security - Xray Operational
90 days agoNo incidentsToday
Security - JAS Operational
90 days agoNo incidentsToday
Security - Curation Operational
90 days agoNo incidentsToday
Security - Catalog Operational
90 days agoNo incidentsToday
Security - Runtime Operational
90 days agoNo incidentsToday
Distribution Operational
90 days agoNo incidentsToday
Pipelines Operational
90 days agoNo incidentsToday
Web UI Operational
90 days agoNo incidentsToday
Webhook Operational
90 days agoNo incidentsToday

Europe - West1 (Ireland) - AWS

Artifactory Operational
90 days ago1 day with an incidentToday
Security - Xray Operational
90 days agoNo incidentsToday
Security - JAS Operational
90 days agoNo incidentsToday
Security - Curation Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Maintenance

Affected components

5
  • ArtifactoryUS - East1 (S. Carolina) - GCPMaintenance
  • ArtifactoryUS - Central1 (Iowa) - GCPMaintenance
  • ArtifactoryUS - East1 (S. Carolina) - OSS - GCPMaintenance
  • ArtifactoryUS - West1 (Oregon) - GCPMaintenance
  • ArtifactoryEurope - West2 (London) - GCPMaintenance

Follow JFrog

Your coding agent knows when JFrog is down, and tells you when a failure is theirs, not yours. You can also get JFrog incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "jfrog" and tell me if JFrog has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=jfrog
Slack
/feed subscribe https://outages.live/feed.xml?providers=jfrog

Go from tracking outages to fixing production issues with Polylane.

Try Polylane