63 Chargebee incidents · februar 2025 — official updates, affected components, duration and resolution details.
Vi undersøger et spørgsmål, der forhindrer nye brugere i at tilmelde sig. Vi vil give en opdatering, så snart vi har flere oplysninger.
Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.
Et fix er blevet gennemført, og vi overvåger resultaterne.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undersøger login spørgsmål, når adgang til Chargebee Admin Portal (https: / / app.recebee.com) ved hjælp af e-mail og adgangskode; der er ingen problemer med Single Sign-On. Vi holder jer underrettet, når vi gør fremskridt.
Spørgsmålet er blevet løst, og vi overvåger vores systemer for at sikre fortsat stabilitet. Vi undskylder for eventuelle forstyrrelser.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplevede en kort service afbrydelse, der resulterede i et lille antal mislykkedes API anmodninger. Alle tjenester er kommet sig, og vi overvåger vores systemer for at sikre fortsat stabilitet. Vi undskylder for eventuelle forstyrrelser.
Vi bemærkede API fejl mellem 11: 49 UTC og 12: 01 UTC. Mens den samlede hændelse vindue varede i 12 minutter, de faktiske forstyrrelser var begrænset til 4 minutter. Vores systemer er helt stabile, og vi løser denne hændelse.
Automatisk oversat fra den officielle hændelsesopdatering.
Mellem 12: 54 UTC og 12: 57 UTC kan nogle brugere have oplevet intermitterende API svigt i den amerikanske region. Tjenesterne er kommet sig, og vi overvåger situationen for stabilitet.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplevede intermitterende login og funktionalitetsproblemer på grund af en ekstern service afbrydelse på QuickBooks Online. QuickBooks har bekræftet, at roden årsag er blevet rettet og alle systemer er fuldt restaureret. Vi undskylder for ulejligheden. Incident Reference - https: / / quickbooks.statuspageio / hændelser / vkntw55njz2z
Automatisk oversat fra den officielle hændelsesopdatering.
Mellem 14: 54 UTC og 15: 32 UTC oplevede vi periodiske fejl med vores skatteberegningsudbyder, Avalara, som midlertidigt påvirkede et par API-anmodninger. Fejlene er holdt op, og vi overvåger fortsat tjenesterne for at sikre stabilitet.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
Mellem 05: 59 UTC og 06: 01 UTC kan nogle brugere have oplevet intermitterende API svigt i alle 3 regioner. Tjenesterne er kommet sig, og vi overvåger situationen for stabilitet.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undersøger et teknisk problem med vores skatteberegningsudbyder, Avalara, som påvirker nogle abonnementsfornyelser og faktureringsprocesser. Vi følger op med Avalara på dette og vil holde denne hændelse opdateret, når vi skrider frem.
Fejlene stoppede fra 08: 25 UTC, og vi overvåger de berørte systemer for stabilitet.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplevede intermitterende API anmodning timeouts i den amerikanske region mellem 12: 38 UTC og 12: 43 UTC. Spørgsmålet er siden blevet løst, og tjenesterne fungerer normalt.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplevede en forsinkelse i webhook levering til TEST sites under vinduet fra 19. juli 09: 49 UTC til 19. juli 12: 12 UTC, og tjenesterne fungerer som forventet. Vi undskylder for eventuelle forstyrrelser dette forårsaget af dine test arbejdsgange.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplevede intermitterende API request timeouts i EU-regionen under vinduet fra 15- 7- 2026 21: 56: 00 UTC til 16- 07- 2026 01: 23: 55 UTC. Spørgsmålet er siden blevet løst, og tjenesterne fungerer normalt.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er klar over et problem, der forårsager server fejl, der skal vises i Chargebee Copilot panel i vækst ansøgning. Brugere kan være ude af stand til at indlæse eller interagere med Copilot interface. Alle centrale faktureringsfunktioner er fuldstændig upåvirkede og fungerer normalt.
Vi har bekræftet, at disse indberetninger var falske positive, og at der ikke skete nogen reel forringelse af tjenesten. Vi undskylder for enhver forvirring, det måtte have forårsaget.
Automatisk oversat fra den officielle hændelsesopdatering.
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