Cloudsmith reported "STATUS PAGE MIGRATION NOTICE - ACTION REQUIRED" on its status page at 2025-03-25 13:05 UTC.

Cloudsmith did not name the affected components. The updates on this page have the details.

When did the maintenance start and end?

It started at 2025-03-25 13:05 UTC. This page shows the end time when Cloudsmith marks it resolved.

How do I get alerts for Cloudsmith?

Subscribe to the Cloudsmith live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cloudsmith. outages.live reads it every few minutes and keeps every update.

CloudsmithMaintenance · 2025-03-25 13:05 UTC

STATUS PAGE MIGRATION NOTICE - ACTION REQUIRED

MaintenanceOfficial update

We are migrating our status page from Atlassian to incident.io to improve. incident management and communication. ⚠️ IMPORTANT ACTION REQUIRED BY APRIL 24, 2025 ⚠️ To continue receiving notifications - any existing alerts, subscriptions, or automation tied to our current status page should be updated before April 24th, 2025. New Status Page: https://status.cloudsmith.com After April 24, 2025, https://status.cloudsmith.io will redirect to the new URL. ---------------------- WHAT THIS MEANS FOR YOU ---------------------- - If you are not currently receiving status notifications: Sign up to receive notifications. - If you currently receive status notifications: See below for set-up instructions. --------------------------------- MIGRATING YOUR SUBSCRIPTION CONFIG --------------------------------- Slack: - Action Required: Configuration Change - Instructions: Use the slash command: /feed subscribe https://status.cloudsmith.com/slack.rss RSS: - Action Required: Configuration Change - Instru

The latest update from Cloudsmith.

State

Scheduled

Started

586 d ago

2025-03-25 13:05 UTC

Ongoing for

586 days

Worst impact

Maintenance

Timeline

1 update

Mar 25Aug 18Jan 12Jun 7Nov 1

MaintenanceUpdate postedDates in UTC

Scheduled

586 days 100%

Updates

Times in UTC

As posted by Cloudsmith

Scheduled2026-10-31 21:45 UTC

Cloudsmith in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 28 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

17 h 31 min

median 1 h 28 min

90 days agoToday

Other Cloudsmith incidents

All incidents

Cloudsmith·Experiencing 502/504 errors for Maven uploads

This issue has now been resolved.

Resolvedresolved 6 d ago

Cloudsmith·Intermittent 500 errors on Package Downloads

All services are operating normally

Resolvedresolved 12 d ago

Cloudsmith·Issues with package downloads

We have deployed the fix and confirmed resolution

Resolvedresolved 19 d ago

Cloudsmith·Intermittent 503 Errors on Download Requests

This incident is now resolved. Between 14:40 UTC and 18:53 UTC on 12 October 2026, some users may have experienced intermittent HTTP 503 errors affecting package downloads. We have applied a fix, and after monitoring, we confirmed normal operation for download requests.

Resolvedresolved 20 d ago

Cloudsmith·Intermittent Issue pushing NuGet packages

This incident is now resolved. Between approximately 12:00 UTC on 3 October and 07:30 UTC on 5 October, customers in Europe (eu-west-1) experienced intermittent failures when pushing NuGet packages. We have applied changes to the affected services and confirmed that package pushes have returned to normal. Pulling and downloading packages was unaffected throughout, as were all other package formats.

Resolvedresolved 27 d ago

Follow Cloudsmith

Your coding agent knows when Cloudsmith is down, and tells you when a failure is theirs, not yours. You can also get Cloudsmith 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.cc/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 "cloudsmith" and tell me if Cloudsmith 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.cc/feed.xml?providers=cloudsmith

Slack

/feed subscribe https://outages.cc/feed.xml?providers=cloudsmith

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane