Live

Unexpected rate limits for some customers

0

Sanity reported unexpected rate limits for some customers on api.sanity.io and apicdn.sanity.io. Sanity resolved the incident and says the impact lasted about 65 minutes.

State

Resolved

Started

Lasted

1 h 5 min

Worst impact

Degraded

Timeline

3 updates
16:3116:4717:0417:2017:36
DegradedUpdate postedTimes in UTC

Investigating

20 min 31%

Monitoring

45 min 69%

Updates

Times in UTC

As posted by Sanity

Resolved

This incident has been resolved.

Monitoring

As of 16:30 UTC, all unexpected rate-limited requests for affected customers have been resolved. We are continuing to monitor.

Investigating

Some customers are currently encountering unexpected rate limits, which will appear as failed API and API CDN requests (the latter when revalidating the cache).

Affected components

2
api.sanity.ioapicdn.sanity.io

Sanity in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

13

Days with an incident

14

Median duration

1 h 36 min

This incident

32% shorter than the median

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

22 h 6 min
median 1 h 36 min
90 days agoToday

Other Sanity incidents

All incidents

Follow Sanity

Your coding agent knows when Sanity is down, and tells you when a failure is theirs, not yours. You can also get Sanity 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 "sanity" and tell me if Sanity 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=sanity
Slack
/feed subscribe https://outages.live/feed.xml?providers=sanity

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane