All Systems Operational
api.sanity.io Operational
90 days ago
99.51 % uptime
Today
apicdn.sanity.io Operational
90 days ago
100.0 % uptime
Today
cdn.sanity.io Operational
90 days ago
100.0 % uptime
Today
Asset Pipeline Operational
90 days ago
100.0 % uptime
Today
Authentication Operational
90 days ago
99.99 % uptime
Today
Datasets Operational
90 days ago
100.0 % uptime
Today
Studio ? Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
99.53 % uptime
Today
www.sanity.io ? Operational
90 days ago
99.99 % uptime
Today
Manage ? Operational
90 days ago
99.99 % uptime
Today
GraphQL ? Operational
90 days ago
100.0 % uptime
Today
Integrations ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Sep 12, 2024

No incidents reported today.

Sep 11, 2024

No incidents reported.

Sep 10, 2024

No incidents reported.

Sep 9, 2024

No incidents reported.

Sep 8, 2024

No incidents reported.

Sep 7, 2024

No incidents reported.

Sep 6, 2024
Resolved - The issue has now been fully resolved, and the role mapping modals are rendered as expected. We are actively monitoring the system to ensure continued performance and reliability.
Sep 6, 12:35 UTC
Identified - We are currently experiencing an issue affecting enterprise customers using SAML SSO. The role mapping modal is not rendering correctly, which may prevent users from managing role assignments effectively.

Our team has identified the underlying issue and reviewing the fix for release. We are committed to resolving this as quickly as possible and will provide updates as they become available.

We apologize for any inconvenience this may cause and appreciate your patience. If you have any urgent concerns, please reach out to our support team for assistance.

Sep 6, 11:54 UTC
Resolved - We experienced a delay in API CDN invalidations between 08:30 and 09:30 UTC.
During this period, users may have noticed that changes to cached content were not reflected immediately due to the delay in invalidating the content on our CDN.

The issue has now been fully resolved, and invalidations are processing as expected. We are actively monitoring the system to ensure continued performance and reliability.

We apologize for any inconvenience caused and appreciate your understanding. If you continue to experience any issues, please contact our support team.

Sep 6, 08:30 UTC
Sep 5, 2024

No incidents reported.

Sep 4, 2024

No incidents reported.

Sep 3, 2024

No incidents reported.

Sep 2, 2024

No incidents reported.

Sep 1, 2024
Resolved - This incident has been resolved.
Sep 1, 22:27 UTC
Monitoring - This incident has now been resolved. The fix will temporarily affect the ability to access document history for the subset of customers that were impacted. No data was lost and all history will be restored shortly.
Aug 31, 22:20 UTC
Update - We are continuing to implement a fix for this issue.
Aug 31, 15:58 UTC
Update - We are continuing to implement a fix for this issue.
Aug 31, 14:28 UTC
Update - We are continuing to implement a fix for this issue. Until roll-out is complete, impacted customers will still see mutations failing and webhooks will be unavailable on their affected datasets. All queries to the API and API CDN remain unaffected by this incident.
Aug 31, 12:55 UTC
Identified - We are experiencing an issue with mutations failing for a small subset of customers. The main impact of this issue is on Studio connectivity. We have identified the cause and a fix is being implemented.
Aug 31, 11:52 UTC
Aug 31, 2024
Aug 30, 2024

No incidents reported.

Aug 29, 2024
Resolved - This incident has been resolved.
Aug 29, 16:40 UTC
Monitoring - The pending webhook delivery queue has dropped to zero. We are continuing to monitor.
Aug 29, 15:16 UTC
Identified - The issue has been identified and the webhook delivery queue is shrinking.
Aug 29, 14:25 UTC
Investigating - There is a backlog of webhooks that is causing delayed delivery for some customers. We are currently investigating and are working on clearing that queue.
Aug 29, 14:22 UTC