注册降解
Issues轻微事件
- investigating
我们正在调查一个阻止新用户报名的问题。 一旦掌握更多信息,我们将提供最新情况.
- identified
这一问题已经确定,一个解决办法正在实施之中.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
63 Chargebee incidents · 2025年2月 — official updates, affected components, duration and resolution details.
我们正在调查一个阻止新用户报名的问题。 一旦掌握更多信息,我们将提供最新情况.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们在使用电子邮件和密码访问Chargebee Admin门户网站(https://app.chargebee.com)时,正在调查登录问题;单一签名没有问题。 我们会随时通知你.
这个问题已经解决,我们正在监测我们的系统,以确保持续稳定。 我们为这可能造成的破坏道歉.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们经历了短暂的服务中断,导致少数API请求失败. 所有服务已完全恢复,我们正在监测我们的系统,以确保持续稳定。 我们为这可能造成的破坏道歉.
我们注意到协调世界时11:49至协调世界时12:01之间的API故障. 虽然整个事件窗口持续了12分钟,但实际中断时间仅限于4分钟. 我们的系统仍然完全稳定,我们正在解决这一事件.
自动翻译自官方事件更新。
在协调世界时12:54至协调世界时12:57之间,一些用户可能曾经历过美国地区间歇性API故障. 这些服务已经恢复,我们正在监测局势,以促进稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
由于QuickBooks Online的外部服务中断,我们经历了间歇性登录和功能问题. "快书"证实"根由已经固定",所有系统全部恢复. 我们对此造成的任何不便表示歉意。 事件参考 - https://quickbooks.statuspage.io/incidents/vkntw55njz2z 互联网档案馆的存檔,存档日期2014-12-21
自动翻译自官方事件更新。
在协调世界时14:54至协调世界时15:32之间,我们与我们的税收计算提供者阿瓦拉拉发生断断续续的错误,这暂时影响了几个API请求. 错误已经停止,我们正在继续监测各种服务,以确保稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
Some users may have experienced intermittent issues managing subscriptions, invoices, or payment methods in the Self-Serve Portal. Service has been fully restored. We apologize for any inconvenience caused.
在协调世界时05:59至协调世界时06:01之间,一些用户可能在所有3个地区都经历了间歇性API故障. 这些服务已经恢复,我们正在监测局势,以促进稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在同我们的税务计算提供者阿瓦拉拉调查一个技术问题,它影响到一些续订和开具发票的程序。 我们正在跟踪阿瓦拉拉,并将随着我们的进展不断更新这一事件.
错误从协调世界时08:25停止,我们正在监测受影响的系统,以确保稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
协调世界时12:38至协调世界时12:43之间,我们在美国地区经历了间歇性API请求超时的情况. 这个问题后来得到解决,服务正常运行.
自动翻译自官方事件更新。
从协调世界时的7月19日09:49到协调世界时的7月19日12:12,在窗口期间,我们经历了为TEST网站提供网页的延迟,这些服务正在如预期的那样运作. 我们为这给您的测试工作流程造成的任何干扰道歉.
自动翻译自官方事件更新。
我们在欧盟地区经历了间歇性的API请求超时,从协调世界时15-7-2026 21:56:00到协调世界时16-07-2026 01:23:55. 这个问题后来得到解决,服务正常运行.
自动翻译自官方事件更新。
我们意识到一个导致服务器错误的问题出现在Growth应用程序中的Chargebee Copilot面板中. 用户可能无法加载或与"副驾驶"接口交互. 所有核心计费功能均完全不受影响并正常运行.
我们确认,这些警报是虚假的,没有实际出现服务退化。 我们为这可能造成的混乱道歉.
自动翻译自官方事件更新。
We are investigating an issue with our email provider that is causing delays in system notifications. Our team is working with the email provider to restore normal functionality. We will keep you posted as we progress.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented. We are coordinating with our email provider to activate these changes and fully restore notification services.
Our team is following up with the email provider to expedite the restoration of notification services. We will keep you posted as we progress.
We are working with our email provider to expedite the resolution. We will provide another update as soon as notifications begin processing again.
Email service has been restored, and new notifications are now being delivered as expected. We will reprocess all queued emails to ensure that any messages delayed during this period are successfully delivered.
This incident has been resolved.
We experienced 2 minutes of intermittent API request timeouts in the US region during the window from 05-06-2026 22:16 UTC to 22:22 UTC. The issue has since been resolved, and services are operating normally.
We are investigating an issue with our email provider that is causing delays in system notifications for test sites. Live sites are not impacted and remain fully operational. We are working with the provider to restore normal email functionality for our test environments. We will keep you posted as we progress.
We have restored outbound email functionality for test environments. This incident has been resolved. -- Live sites were not impacted during this service window.
We experienced intermittent API request timeouts in the EU region between 15:02 UTC and 15:16 UTC. The issue has since been resolved, and services are operating normally.
We experienced an issue causing intermittent 5xx errors across all regions, which was traced back to an internal change. We have reverted it to restore full stability. We apologize for any inconvenience this may have caused. Update: Impact Window: 10:06 UTC to 10:17 UTC
We are experiencing login issues with the RevRec portal. We will share an update as we progress.
We have identified the root cause and implemented a fix. Our team is continuing to monitor the services to ensure ongoing stability.
This incident has been resolved.
Between May 7, 23:35 UTC and May 8, 00:55 UTC, we experienced intermittent API request timeouts in the US region due to an AWS platform issue. We are monitoring the systems to ensure continued stability.
Our team is working with AWS to assess the impact. We will share an update as we progress.
We are continuing to monitor the services. The incident remains open as we verify full system recovery. We will share an update as we progress.
We have verified that the intermittent API latency has been fully resolved. Our monitoring confirms all systems have fully recovered.
### **Intermittent API Errors and Background Processing Delays** **Incident Overview** On May 7, 2026, an infrastructure event in [AWS US-EAST-1](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_FFA94_A4DC515D30F) \(availability zone use1-az4\) caused degraded performance in Amazon DynamoDB, a component of Chargebee’s infrastructure. Rather than a sustained outage, this manifested as two brief windows of elevated API errors — approximately 3:00–3:15 AM UTC and 4:15–4:50 AM UTC on May 8, 2026, while the rest of the period remained largely stable. Approximately 1.5% of active sites experienced intermittent API failures or background job delays during these windows, with actual impact limited to approximately 15 minutes across the event. All affected background jobs were successfully rescheduled and completed. **What Happened** AWS experienced a thermal event in a single availability zone \(use1-az4\) in US-EAST-1, which impaired a subset of DynamoDB storage partitions. While the AWS-side infrastructure recovery took several hours, the customer-visible impact on Chargebee was limited to intermittent error spikes rather than continuous degradation, reflecting our platform’s ability to absorb partial infrastructure failures. **What We Are Doing** All API errors during this incident were traced to DynamoDB latency caused by the AWS internal AZ-level impairment. Given DynamoDB’s role in our business-critical workflows, we are evaluating highly available alternatives and fallback architectures to reduce the impact of similar infrastructure events. --- We recognise that even intermittent disruption has real consequences for your operations. The errors that spiked during this incident were brief, and our systems absorbed the majority of the AWS recovery window. We remain committed to further reducing Chargebee’s exposure to external infrastructure events