Live

Increase in latency for OIDC requests

We have now release a fix to resolve this issue. Our OIDC service is operating normally

The latest update from Cloudsmith.

State

Resolved

Started

39 d ago

2026-09-23 08:18 UTC

Lasted

3 h 21 min

until 2026-09-23 11:40 UTC

Worst impact

Degraded

Timeline

4 updates
08:1809:0909:5910:5011:40
DegradedUpdate postedTimes in UTC

Investigating

2 h 15 min 67%

Monitoring

1 h 7 min 33%

Updates

Times in UTC

As posted by Cloudsmith

Resolved2026-09-23 11:40 UTC

We have now release a fix to resolve this issue. Our OIDC service is operating normally

Monitoring2026-09-23 10:33 UTC

We have identified the issue, and a fix has been deployed. We are monitoring the issue.

Investigating2026-09-23 08:50 UTC

The engineering team is investigating increased latency for requests to our OIDC service; we've determined a potential cause and are working on a fix

Investigating2026-09-23 08:18 UTC

The engineering team is investigating increased latency for requests to our OIDC service; no impact is currently observed.

Cloudsmith in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

18

Days with an incident

18

Median duration

1 h 28 min

This incident

2.3× the median

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

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