Yousign 中断历史

1. 2026年9月4日 UTC 12:30investigating

   发送到微软托管地址(Outlook、Hotmail、Live和Microsoft 365)的一些电子邮件来得太晚或根本没有到来。 顾客在11:30CEST通知我们,中午后受影响的信息数量再次上升. 我们的发送追踪显示 每封邮件 仍然被发送商接受 所以问题似乎发生在交接之后 我们正在和他们一起调查 以确认原因 给所有其他提供者的电子邮件不受影响。 您一方无需采取任何行动。 一旦我们知道更多情况,我们将公布新的最新情况,我们对此造成的干扰感到遗憾.

2. 2026年9月4日 UTC 12:43identified

   更新 : 这个事件是微软方面,不是我们方面. 我们的供应商已确认在入境邮件上发生了一起全球性的微软事件,而微软并没有在自己的状态页面上发布. 我们的电子邮件离开我们的系统, 并被我们的发送提供者接受 像往常一样, 然后停下来微软。 从今天上午起,我们的电子邮件通知都没有到达由微软托管的商业邮箱(微软365和Exchange Online). 展望.com,hotmail.com和活地.com等个人地址不受影响,其他供应商也不受影响. 我们方面无法改变的东西将传送这些电子邮件,因此,我们无法解决这一事件或承诺解决时间。 我们正在追踪我们的供应商,他们与微软直接接触。 我们将告诉你,自今天上午以来所保存的电子邮件是用于恢复还是需要再次发送。 下一次更新在小时内.

3. 2026年9月4日 UTC 15:14monitoring

   微软解决了事件. 给微软企业邮箱的电子邮件再次被接受,所以新的通知通常都会通过. 我们的提供商仍在发邮件, 在清理积压之前,接收者仍可能延迟收到通知。 什么都没有丢失,你不需要再发送任何东西。 积压排水量的多快取决于我们的供应商 取决于微软接受的速率 而不是我们所控制的 一旦积压工作全部完成,下一次更新.

4. 2026年9月4日 UTC 21:06resolved

   决出. 积压的邮件全部交付:事件期间被扣留的每封邮件现在都已发送,自微软结束事件后,交付给微软企业的邮箱已经恢复正常. 发生的事情:从11:30左右的CEST,一个全球微软在入境邮件上的事件阻止了我们的通知到达由微软365和Exchange Online托管的商业邮箱. 展望.com,hotmail.com和活地.com等个人地址从未受到影响,也没有其他电子邮件提供者参与. 我们的系统一直正常发送 消息被我们的提供者排队而不是丢失。 微软恢复服务后,排队时间在接下来的几小时被冲走,这就是为什么有些通知在今天下午和晚上很晚才到来的原因. 原因和修补都站在了微软一边. 我们能改进的是,我们如何迅速发现一个单一供应商的阻塞,并告诉你,我们正在研究这个问题。 谢谢你的耐心 也为今天的混乱而难过.

自动翻译自官方事件更新。

1. 2026年9月2日 UTC 14:28investigating

   目前,合格电子签字服务正在退化。 自15:40(CEST)起,一些QES签名尝试间歇性地(在流量的识别部分)失败. 失败是随机的:当出错时,刷新页面并重试通常可以使签名完成. 今天早些时候也观察到类似的退化,从14:50到15:05. 已经拥有钱包的签名者不会受到影响:他们的签名正常工作. 只有通过身份验证流程获取新钱包的签名者才会遇到这些错误. 我们正在与我们的身份提供者联系,以解决这一问题并稳定服务。 一旦我们掌握了更多信息并更清楚地了解影响,我们将分享新的最新情况。 我们为这种不便表示诚挚的歉意并感谢你的耐心和理解.

2. 2026年9月2日 UTC 14:40monitoring

   快速更新今天早些时候报告的QES退化. 自16:27(CEST)起,我们没有观察到任何进一步的错误,QES签名正在正常完成. 目前,我们正与身份提供者确认,根本原因已经最终解决。 我们将不断密切监测这项服务,并在确认后发出最后更新。 谢谢你的耐心和理解.

3. 2026年9月2日 UTC 15:19resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月31日 UTC 09:42identified

   亲爱的用户, 我国的一个身份核查机构目前面临技术困难。 因此,我们产品中的下列流动受到影响: 高级电子签名:APP v3签名人可能遇到长时间的识别处理时间,一小部分签名人试图进行识别时也可能遇到错误. 核查身份核查:所有API身份核查请求都正确记录并待我们一方处理,一旦供应商返回网上,将予以处理 我们正在积极配合所提供的服务,以迅速恢复我们的服务,并将随时向你们通报这一进程的最新情况。 我们对此可能造成的不便表示歉意,并赞赏你在我们努力加强服务时的理解。 任何问题或援助,请联系@youtrust.com.

2. 2026年8月31日 UTC 10:03monitoring

   我们的提供者已经恢复了服务,我们正在密切注视我们处理积压的待核查工作的情况: 高级电子签名:在供应商出厂期间试图进行身份验证的签名者,其签名流程可能仍然会出错. 我们正积极努力使他们的处境正常化。 其他开始流动的签名者 不会再遇到任何错误 核实身份:所有请求现在应按照标准处理时间(每请求几秒钟)顺利处理 我们正在监测,并将随时向你们通报最新情况.

3. 2026年8月31日 UTC 10:55monitoring

   我们确认,身份查验服务现已完全恢复上网,由于核查工作积压,有些时间很长。 这种延迟正在逐步改善,我们正在继续监测。 在供应商停业窗口期间试图识别的高级电子签名签名人现在应成功重新测试其识别过程。 在停用期间所作的未成功识别尝试将不计入计费/消费数据.

4. 2026年8月31日 UTC 13:28monitoring

   由于我们的供应商正在扩大业务规模以吸收积压的核查工作,核查身份核查服务仍然受到重大延迟的影响。 我们正在同提供者密切合作,以确保顺利恢复服务。 高级电子签字没有受到影响.

5. 2026年8月31日 UTC 18:30monitoring

   我们继续观察到身份核查服务存在拖延。 我国身份核查机构已充分调动其小组,以吸收在日终和夜间的积压核查工作。 随着收到的请求数量逐渐减少,我们期望它们的系统在一夜之间恢复标准处理时间。 数据不会丢失:在此期间提交的所有身份核查请求都安全地记录在我们一方,并将予以处理,不需要你采取任何行动,也不需要重新提交。 高级电子 签署目前没有受到影响。 我们正在不断监测局势,如果有任何变化,我们将提供进一步的最新情况。 下一次更新预计明天早上,或者在局势发生变化时更早。 我们为不方便而道歉。 任何问题请联系我们@yosign.com.

6. 2026年9月1日 UTC 06:00monitoring

   我们的提供方已经查明了它们系统不稳定的根源,与它们的管弦乐器层相连,用于核查服务。 他们的系统在夜间已完全稳定,这意味着身份核查的处理时间现已恢复到几秒钟的标准时间。 我们现在正在逐步处理积压的待核查工作,并期望在上午处理所有核查工作。 我们正在继续监测局势.

7. 2026年9月1日 UTC 08:44monitoring

   在消耗了相当一部分有待核查后,我国的提供者再次面临不稳定。 因此,高级电子签名和身份核查服务处于待决状态: AES 签名者面临识别减速或出错 身份核查申请有待处理,一旦供应商再次出现,将予以处理 我们正在监测局势,并将随时向你通报最新情况.

8. 2026年9月1日 UTC 12:37monitoring

   我们与我们的提供方进行了深入的交流,使我们能够找到其规模问题的确切根源,找到解决问题的途径。 先进电子签名全面启动. 查明核查工作现在也正在运作,同时我们仍然在今后几个小时处理积压的待核查工作.

9. 2026年9月1日 UTC 18:08resolved

   所有身份核查服务现已全面运作,我们已根据对供应商基础设施的洞察力采取了其他措施来增强服务稳定性。 我们现在结束这一事件,并对所造成的任何不便表示诚挚的歉意.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 15:22investigating

   Since 17:11 (CEST), we have been observing a degradation of our services, which may result in slowness or intermittent errors when using Product v2 and v3. Our technical teams are engaged and are currently assessing the precise scope and extent of the impact. An update will be published as soon as more information is available. Thank you for your patience.

2. 2026年8月13日 UTC 15:28investigating

   Since 17:11 (CEST), we have been observing a degradation of our services affecting Advanced (AES) and Qualified (QES) electronic signatures. Current impact: Advanced electronic signature (AES): signers can complete the signing flow, but signature finalisation is delayed. Documents will be finalised once the service is restored. Qualified electronic signature (QES): the signing flow is currently unavailable, and signers are unable to complete their signature. All other operations on the platform, including Simple electronic signature (SES), are operating normally. Our technical teams are actively working on a resolution. An update will be published as soon as more information is available. Thank you for your patience.

3. 2026年8月13日 UTC 15:57investigating

   As of 17:53 (CEST), the situation is stabilised. Both Advanced (AES) and Qualified (QES) signature flows are functional again, and signers are able to complete their signatures normally. We are currently processing the remaining signatures that were pending during the incident. This backlog should be fully cleared within the next few minutes. All other operations on the platform remain unaffected. We will continue to monitor the situation closely and will confirm full resolution shortly. Thank you for your patience.

4. 2026年8月13日 UTC 16:05resolved

   As of 18:05 (CEST), this incident is resolved. All pending Advanced (AES) signatures have been processed, and the signature delay has been fully cleared. Both Advanced (AES) and Qualified (QES) signature flows are operating normally, along with all other operations on the platform. We apologise for the inconvenience caused and thank you for your patience.

1. 2026年7月24日 UTC 11:29monitoring

   目前我们正面临在合格eSignature(QES)上的延迟. 这些拖延来自我们的身份核查提供者之一,它目前正在经历更高的反应时间。 因此,身份核查和QES签名完成的时间可能比通常要长. 所有其他级别的签名(SES, AES)不受影响. 我们为这种不便表示诚挚的歉意。 我们的队伍已充分动员起来,监测局势,尽快恢复正常服务。 我们将尽快提供最新情况.

2. 2026年7月24日 UTC 12:03monitoring

   我们正在继续监测任何其他问题.

3. 2026年7月25日 UTC 10:53resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月17日 UTC 08:46investigating

   目前我们在处理一些QES电子签名请求时遇到延误. 签署工作仍在妥善进行。 钱包创建和签名流是功能,但签名的文档尚未取出. 所有其他级别的签字都不受影响。 我们为这种不便表示诚挚的歉意。 我们的小组已充分动员起来,以查明根源,并尽快执行解决办法.

2. 2026年7月17日 UTC 09:12identified

   我们的一家供应商正面临停工。 我们为不便道歉,并将尽快提供最新情况.

3. 2026年7月17日 UTC 09:26monitoring

   我们正在继续监测任何其他问题.

4. 2026年7月17日 UTC 09:32identified

   这一问题已经确定,一个解决办法正在实施之中.

5. 2026年7月17日 UTC 09:44identified

   我们正在继续努力解决这个问题。

6. 2026年7月17日 UTC 09:55monitoring

   一项措施已经执行,我们正在监测结果.

7. 2026年7月17日 UTC 14:03resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月15日 UTC 19:25investigating

   有些顾客可能会遇到我们的服务问题 我们的工程师正在努力尽快查明和解决此事。 我们很快会再次向你通报最新情况。 如果您有紧急问题, 请通过发送电子邮件联系我们的支援团队@yousign.com .

2. 2026年7月15日 UTC 19:34identified

   这些问题已经确定。 我们的团队正在研究.

3. 2026年7月15日 UTC 19:45resolved

   我们的基础设施供应商介绍了我们低水平基础设施的最新情况,这些基础设施本应没有受到影响。 更新现已完成,所有服务恢复正常. 对在此期间可能发生的服务退化感到抱歉.

自动翻译自官方事件更新。

1. 2026年7月5日 UTC 02:54investigating

   Since 04:24 (CEST), our customers may experience HTTP 500 errors on the Public API and intermittent instabilities on the Yousign application. Our engineering teams are currently investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.

2. 2026年7月5日 UTC 02:55investigating

   Since 04:26 (CEST), our customers may experience HTTP 500 errors on the Public API and intermittent instabilities on the Yousign application. Our engineering teams are currently investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.

3. 2026年7月5日 UTC 03:20investigating

   We are continuing to investigate this issue.

4. 2026年7月5日 UTC 03:22monitoring

   The incident has been resolved since 04:56 (CEST). The root cause has been identified and the situation is now back to normal. The Public API and Yousign application are operating as expected.

5. 2026年7月5日 UTC 03:43resolved

   This incident has been resolved.

1. 2026年6月30日 UTC 11:51investigating

   Since 13:32 (CET), some signature and eSeal requests are experiencing increased processing times. Requests are not lost and continue to complete, though they may take longer than usual to finalize. All other services are operating normally. Our engineering teams have identified the issue and are actively working to reduce these delays. We will provide an update as soon as the situation improves. We apologize for any inconvenience.

2. 2026年6月30日 UTC 12:06identified

   Update: Since 14:00 (CET), processing times for signature and eSeal requests have started to recover. Delays are gradually decreasing and requests continue to complete normally. All other services remain unaffected. Our teams continue to monitor the situation closely. We will confirm once processing times have fully returned to normal. Thank you for your patience.

3. 2026年6月30日 UTC 12:08resolved

   Resolved: As of 14:07 (CET), processing times for signature and eSeal requests have fully returned to normal. All requests are completing as expected. This incident only affected Simple (SES) and Advanced (AES) levels. Qualified Electronic Signature (QES) and Qualified Electronic Seal (QES/qSeal) were not affected. This incident is now resolved. All services are operating normally. Thank you for your patience throughout this incident.

1. 2026年6月29日 UTC 09:10investigating

   Since 11:00 AM (CET), we are observing slowdowns as well as intermittent 500 errors affecting the web application and the API on version 3. Our engineering teams are engaged and currently investigating the root cause in order to restore normal operation as quickly as possible. Impact: some requests may fail or return degraded response times. Retrying the request is generally sufficient to succeed.

2. 2026年6月29日 UTC 09:15monitoring

   Since 11:07 AM (CET), the situation has stabilized: the slowdowns and intermittent 500 errors observed earlier are no longer occurring. The web application and the API are operating normally again. Our teams are maintaining active monitoring to confirm the return to normal operation and to prevent any recurrence.

3. 2026年6月29日 UTC 09:54identified

   [Investigating] New degradation on the App and API (v3) Since 11:46 AM (CET), we are observing a new degradation, with a return of slowdowns and intermittent 500 errors on the web application and the API on version 3. Our engineering teams are engaged again and actively investigating in order to identify the cause and restore normal operation as quickly as possible. Impact: some requests may fail or return degraded response times. Retrying the request may allow it to succeed. We apologize for any inconvenience caused.

4. 2026年6月29日 UTC 10:15monitoring

   Since 12:08 PM (CET), the situation is stable again: the slowdowns and intermittent 500 errors are no longer occurring. The web application and the API are operating normally. Our teams are continuing the investigation to identify the root cause and prevent any further recurrence. Active monitoring remains in place.

5. 2026年6月29日 UTC 13:07resolved

   [Resolved] Service back to normal on the App and API (v3) The incident that caused slowdowns and intermittent 500 errors on the web application and the API (v3) this morning is now resolved. Our teams performed an action on one of our infrastructure clusters, which was relocated. Since this intervention, the situation has been fully stable: everything has been operating normally since 12:08 PM (CET). We are continuing the analysis with our infrastructure provider to identify the cause of the transient saturation of this cluster and to put in place the measures needed to prevent any recurrence. We thank you for your patience and apologize for any inconvenience caused. At no point was the integrity of your signatures or your data affected.

1. 2026年6月22日 UTC 10:34investigating

   Since 12:06 PM (CET), we have identified an issue affecting the real-time update of element statuses within the application. All underlying processes are operating normally. Signatures, approvals, and document workflows are being processed and completed correctly. However, the application is not receiving the events that refresh the status of items on screen. As a result, an action that has actually completed - for example, a signature that has been successfully signed - may still appear with its previous status in the interface. To note: This is a display-only issue. No data is lost and no action is blocked. The actual state of your documents and signatures is correct on our side. API is not affected. Workaround: To see the up-to-date status, please force a refresh of your browser using CTRL+F5 (or the refresh button in your browser). Our teams are actively working on a resolution. We will provide an update as soon as more information is available.

2. 2026年6月22日 UTC 10:40resolved

   As of 12:35 PM (CET), the issue has been resolved. The application is once again receiving events normally, and element statuses are updating in real time as expected. To recap: between 12:06 PM and 12:35 PM (CET), the application was not receiving the events used to refresh the status of items on screen. All underlying processes continued to operate normally throughout this period - signatures, approvals, and document workflows were processed and completed correctly. The issue affected the display of statuses only; no data was lost and no action was blocked. You should no longer need to manually refresh your browser to see the current status of your documents and signatures. We are now investigating the root cause of this degradation to prevent it from recurring. Thank you for your patience.

1. 2026年6月10日 UTC 07:51investigating

   Since 9:31 AM (CEST), we are experiencing degraded performance affecting both the Yousign application and the API v3. The main impact is increased latency in the execution of our processes. Our team is actively investigating to assess the full scope of the impact and identify the root cause. We will provide a further update as soon as we have more information. We apologize for any inconvenience this may cause.

2. 2026年6月10日 UTC 08:04resolved

   As of 10:00 AM (CEST), the latency affecting the Yousign application and the API v3 has been resolved, and process execution times are back to normal. During the incident window (9:31 AM - 10:00 AM CEST), in addition to the delay in process execution, notifications to signers including email, SMS, and voice were also affected by delays. All notifications have now been delivered and the service is operating normally. We apologize for any inconvenience this may have caused and thank you for your patience.

1. 2026年6月3日 UTC 15:36investigating

   Since 4:24pm CET, we're currently experiencing degraded performance on Advanced eSignature identification and image Identity Verification for Verify due to an ongoing incident with one of our third-party providers. Some users may notice slower response times or intermittent errors. Our team is actively monitoring the situation and working with the provider to restore full functionality. We'll share updates as more information becomes available.

2. 2026年6月3日 UTC 15:45investigating

   We are continuing to investigate this issue.

3. 2026年6月3日 UTC 15:57monitoring

   Advanced eSignature identification and image Identity Verification are back to normal since 5:44pm CET. The incident impacted the service from 4:28pm to 5:44pm CET. We are monitoring the situation closely and awaiting confirmation from our third-party provider before resolving this incident.

4. 2026年6月3日 UTC 16:10resolved

   This incident is now resolved. Advanced eSignature identification and image Identity Verification for Verify have been fully operational since 5:44pm CEST. We will continue to investigate with our provider to identify the root cause and prevent any recurrence. We apologize for any inconvenience caused.

1. 2026年5月25日 UTC 08:17resolved

   Between 09:56 and 10:06 CET, customers may have experienced increased latency and intermittent slowness on API v2 and v3 endpoints. The issue has been identified and resolved. All services are now operating normally. We apologize for the inconvenience and thank you for your patience.

1. 2026年5月21日 UTC 08:19investigating

   Since 10:00 AM CET, we are observing increased processing times on electronic signature operations. Signatures are still being processed successfully, but with higher latency than usual. Our engineering teams are actively investigating the root cause. We will provide an update as soon as we have more information. Thank you for your patience.

2. 2026年5月21日 UTC 08:44investigating

   Since 10:00 AM CET, we are observing increased processing times on the following operations: - Simple Electronic Signature (SES) - Advanced Electronic Signature (AES) - Simple and Advanced eSeal Qualified Electronic Signature (QES) is not impacted and continues to operate normally. Operations are still being processed successfully, but with higher latency than usual. Our engineering teams are actively investigating the root cause and we will provide an update as soon as we have more information. Thank you for your patience.

3. 2026年5月21日 UTC 08:58resolved

   Processing times on Simple/Advanced Electronic Signature and Simple/Advanced eSeal started to recover at 10:51 AM CET and returned to normal at 10:57 AM CET. All operations are now processed with usual latency. Qualified Electronic Signature (QES) was not impacted at any point during the event. A post-event analysis is being conducted by our engineering teams to identify the root cause and prevent recurrence. Thank you for your patience.

1. 2026年5月18日 UTC 08:00identified

   Since 9:35 AM, we are experiencing an issue affecting the v3 application. The API and the application are working normally, and your actions are being processed correctly on our side. However, the browser is not receiving real-time status updates. For example, a signature request that has just been signed will not automatically appear as signed in the application. Workaround: Refresh the page manually to see the latest status. Next update: We are currently rolling back a recent configuration change to restore normal behavior. We will share an update as soon as the situation evolves. We apologize for the inconvenience and thank you for your patience.

2. 2026年5月18日 UTC 08:11resolved

   The application has been working normally since 9:57 AM. Notifications are now being delivered to users' browsers as expected. Important action is required for already-connected users: **If you were connected to the application between 9:35 AM and 9:57 AM, please force a refresh of your browser page to restore real-time updates.** You can do this by: Clicking the refresh button in your browser, or Pressing Ctrl + R (Windows / Linux) or Cmd + R (Mac). Users who connect (or reconnect) after 9:57 AM are not affected and do not need to take any action. We sincerely apologize for the inconvenience caused during this incident. We are now marking this incident as resolved and thank you for your patience and understanding.

1. 2026年5月12日 UTC 15:20investigating

   Since 17:03 (CET), our customers may experience HTTP 500 errors on the Public API and intermittent instabilities on the Yousign application. Our engineering teams are currently investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.

2. 2026年5月12日 UTC 15:32monitoring

   The incident has been resolved since 17:19 (CET). The root cause has been identified and the situation is now back to normal. The Public API and Yousign application are operating as expected.

3. 2026年5月12日 UTC 16:04resolved

   This incident has been resolved.

1. 2026年4月30日 UTC 07:31investigating

   We are currently experiencing delays in signature processing affecting both our v2 and v3 Products. Users may experience longer than usual processing times when signing documents.Status: We identified the issue at 09:19 AM CEST and our engineering team is actively working on restoring normal service. We are implementing a failover to resolve the situation. We will provide an update within the next 30 minutes. We apologize for the inconvenience.

2. 2026年4月30日 UTC 07:37identified

   Our teams have identified the issue, and we are actively working to resolve it. SES signatures have been processed since 9:33 a.m.; we are working to reduce the processing time for AES and QES.

3. 2026年4月30日 UTC 07:43monitoring

   Our teams have resolved the issue with the signature processing delay: * Processing of SES-level signatures has been back to normal since 9:33 a.m. * Processing of AES- and QES-level signatures has been back to normal since 9:38 a.m. Everything has been back to normal since 9:40 a.m. We apologize for the inconvenience.

4. 2026年4月30日 UTC 08:04resolved

   The incident is fully resolved. The root cause was a network outage on one of the datacenters hosting our electronic signature operations. The recovery time corresponds to the failover process to our secondary datacenter and the automatic patching of the affected components. SES signatures were restored first (9:33 AM), followed by AES and QES signatures (9:38 AM), with full service recovery at 9:40 AM. Our teams are currently investigating the root cause of the network outage. We thank you for your patience.

1. 2026年4月8日 UTC 07:07investigating

   Since 8:50 a.m., our webhooks/notifications are running slowly on API; The app and API remain functional and accessible. we are investigating the cause

2. 2026年4月8日 UTC 07:39identified

   A fix has just been deployed, and notifications regarding the status of the signatures are currently being sent out. Please note that the signatures were properly signed and accessible; only the API webhooks had not been sent since 8:50 a.m.

3. 2026年4月8日 UTC 07:53identified

   FYI - We have reassessed the initial impact. The response time is normal for both the app and the API. Only the webhooks (notifications) for the v3 API were down from 8:50 AM to 9:43 AM. Since 9:43 AM, notifications/webhooks have been sent (though there is still some delay).

4. 2026年4月8日 UTC 07:59monitoring

   All notifications/webhooks have been sent, and the service is back to normal.

5. 2026年4月8日 UTC 08:27resolved

   This incident has been resolved.

1. 2026年4月7日 UTC 08:23investigating

   We are experiencing performance slowdowns on our v3 Application and API since 9:47 AM UTC+2. Application: Slower navigation and page load times API: Increased response times on API requests and delays in webhook delivery Signing delays are not affected by this issue. Our team is actively investigating the root cause. We have increased system capacity to help reduce the impact while we work on a resolution. We will provide updates as we learn more.

2. 2026年4月7日 UTC 08:28identified

   As of 10:22 a.m., the situation has returned to normal. We have increased our system's processing capacity while we identify the cause of the slowdown.

3. 2026年4月7日 UTC 08:35monitoring

   The incident is now under monitoring; the situation has been stable since 10:22 a.m.

4. 2026年4月7日 UTC 09:19resolved

   The issue has been resolved since 10:22 a.m; our teams are investigating the root cause.