管理中未加载的付款表
Issues轻微事件
受影响的组件
Manage
- identified
我们发现一个问题 阻止付款表装入管理器 没有保存卡片的客户目前无法添加付款方法或升级计划. 现有的订阅和节省的支付方法不受影响。 已查明原因,正在部署一个固定装置。 现场直播后再发布最新消息.
- monitoring
固定装置已经部署,付款表已经恢复。 我们正在核实受影响的流量 并监测任何进一步的问题.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
62 Sanity incidents · 2025年6月 — official updates, affected components, duration and resolution details.
我们发现一个问题 阻止付款表装入管理器 没有保存卡片的客户目前无法添加付款方法或升级计划. 现有的订阅和节省的支付方法不受影响。 已查明原因,正在部署一个固定装置。 现场直播后再发布最新消息.
固定装置已经部署,付款表已经恢复。 我们正在核实受影响的流量 并监测任何进一步的问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
从 UTC 的 6: 33 起, 我们看到向 Embeddings Index 服务请求时错误率( HTTP 5xx) 升高。 这个问题在协调世界时约7:16被确定并解决.
自动翻译自官方事件更新。
从UTC19:51的近似时间开始,我们看到向Embeddings索引,Agent Actions和AI Assistance服务请求时,错误率(HTTP 5xx)上升. 这个问题在协调世界时约20:32被确定并解决.
自动翻译自官方事件更新。
从协调世界时13:05-13:45左右开始,我们看到由于API请求间歇性超时,一小部分客户的API出错率提高. 这个问题已经确定和解决.
自动翻译自官方事件更新。
一些顾客在协调世界时8月17日大约从07:25到07:45之间经历了间歇性的工作室连通问题. 这个问题已经解决,各种服务已经恢复正常运作.
自动翻译自官方事件更新。
Starting at approximately 14:30 UTC, we have seen elevated API and API CDN error rates. We are currently investigating the issue.
A fix was implemented and service rates returned to normal at 14:40 UTC. The period of elevated error rates was identified to have started at 14:34 UTC. We are continuing to monitor.
This incident has been resolved.
Between approximately 09:25 and 09:45 UTC on August 6, some requests to api.sanity.io and apicdn.sanity.io returned errors or timed out for a small subset of customers. The issue has been resolved and API services have returned to normal operation.
在协调世界时7月24日约23:16至协调世界时7月25日00:10之间,一些图像和资产请求从cdn.sanity送达. io返回错误或缓慢地为北美和欧洲的用户加载. 此后,图像和资产交付已恢复正常运作。 Contents APIs(api.sanity.io, apicdn.sanity.io)和 Studio编辑没有受到影响.
自动翻译自官方事件更新。
在协调世界时18:00至21:00之间,一些地区的Live Content API出现了部分停用. 事件现已解决.
自动翻译自官方事件更新。
我们正在调查关于连通性问题的报告 影响Sanity Studio。 一些用户可能会经历工作室被卡在"尝试连接"上或无法加载. 我们的工程组正在积极调查这一问题,一旦获得更多信息,我们将提供最新情况.
我们确认,在早期缓解之后,一些用户再次出现这一问题。 我国工程组正在积极调查剩余的连通性问题并努力恢复全面服务. 我们将继续在获得更多信息后提供最新情况.
我们发现了影响额外服务的问题再次发生。 我们的工程队正在积极实施进一步缓解并调查所余影响。 我们将继续提供最新资料.
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查Webhooks网页未能装入Webhook数据的问题. 这不影响网络浏览的交付。 在您的项目上配置的 Webhooks 将继续按预期开火 .
一项固定措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
A small subset of customers experienced increased query latency and intermittent timeouts during this incident. Our engineering team identified the issue, implemented mitigations, and restored normal query performance. The incident has been resolved.
We are currently investigating an issue causing slower-than-expected query performance for some customers. A subset of users may experience increased latency when querying content. Our team is actively investigating the issue and working to mitigate the impact. We will provide further updates as more information becomes available.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of an issue with the Content Agent in Dashboard where a small number of responses in longer-running threads may not be delivered to the user. We are investigating and will provide an update shortly.
The issue has been identified and we are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has now been resolved.
Our MCP server (mcp.sanity.io) is currently inoperative, returning 500 errors and impacting access via tools like Claude and Cursor. We are working to restore functionality.
We are implementing a fix that should resolve the issue.
We’ve identified the issue affecting the MCP server (mcp.sanity.io) and are actively working on a fix. We’ll share another update as soon as we have more information.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 06:01 and 06:35 UTC today, some users encountered errors when attempting to create organizations, create projects, or make plan changes. This was caused by an internal service configuration issue that has since been rolled back.
Between approximately 06:35 and 06:52 UTC today, some users may have experienced issues loading Sanity Studio. This was caused by a temporary service disruption in our infrastructure. The issue is resolved and a fix has been deployed to prevent recurrence.
Between 14:14 UTC and 14:20 UTC, we observed elevated error rates on our API for some customers. The issue has since been resolved and all systems are operating normally.
We’re currently investigating an issue affecting Sanity Studio where some users may see documents and document lists fail to load.
We’ve taken steps to address an issue affecting Sanity Studio where some users experienced documents and document lists failing to load, and are continuing to monitor the situation closely.
This incident has been resolved.
Starting 12:47 UTC, we are experiencing a sustained error rate on the Asset CDN. Some customers will be seeing elevated rates of 5xx errors when requesting images during this time.
The issue has been identified and we are working on a fix.
A fix has been implemented and we are monitoring results.
This incident has been resolved.