Email Service Degradation
Resolved
This incident has been resolved.
Jun 11, 11:15 PMResolved Jun 12, 2:12 AMCriticalEmail Notifications (AU)Email Notifications (EU)
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Subscription billing and revenue management for SaaS businesses.
Source
auto
Category
Payments
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 1h ago
96
Components
0
Active incidents
0
Maintenance
7.69%
90d uptime
Email Service Degradation
Jun 11, 11:15 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 25 of 96 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
API Endpoints https://apidocs.chargebee.com/docs/api/ | Operational | Group | Not recorded |
Checkout A collective term for Chargebee checkout and portal. | Operational | Group | Not recorded |
Webhooks Webhooks (or HTTP callbacks) can be used to notify your systems about events as they occur in your Chargebee instance. | Operational | Group | Not recorded |
Email Notifications | Operational | Group | Not recorded |
Payment Gateway Processing The virtual equivalent of a credit card machine, a payment gateway is your portal to accepting online payments | Operational | Group | 6/17/2026 |
Chargebee UI https://app.chargebee.com | Operational | Group | Not recorded |
Self-Serve Portal | Operational | Group | Not recorded |
Mobile Subscriptions Apple iOS and Google Android in Chargebee | Operational | Group | Not recorded |
Identity and Access Management SSO allows team members to sign on using their associated credentials. Chargebee supports authentication via SAML or Google. | Operational | Group | Not recorded |
Reports And Analytics Revenue Story gives you a 360° business visibility on subscription analytics | Operational | Group | Not recorded |
Third Party Integrations Third-party providers and services | Operational | Group | Not recorded |
Email Services | Operational | Group | Not recorded |
Chargebee RevRec Revenue recognition is an accounting methodology which helps determining the revenue to be recognized over the period of time the service is consumed. | Operational | Group | Not recorded |
Chargebee Receivables Accounts Receivable (AR) management and collection automation platform that helps to view, track, and collect unpaid invoices. | Operational | Group | Not recorded |
Chargebee Retention | Operational | Group | Not recorded |
API (US) | Operational | Component | Not recorded |
Accounting Services Revenue recognition features | Operational | Component | Not recorded |
Admin Console (US) | Operational | Component | Not recorded |
Apple Store | Operational | Component | Not recorded |
Chargebee Payments (US) | Operational | Component | Not recorded |
Checkout (US) | Operational | Component | Not recorded |
Customer Portal app.brightback.com | Operational | Component | Not recorded |
Dashboard (US) | Operational | Component | Not recorded |
Email Notifications (US) | Operational | Component | Not recorded |
IAM (US) | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Chargebee is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
7.69%
Known uptime
13 known history days
96
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Payment Gateway Processing
Operational
Spreedly Core Transactional API
Operational
API (AU)
Operational
API (EU)
Operational
API (US)
Operational
1
operational days
1
degraded days
8
outage days
3
maintenance days
77
unknown days
Latest outages and degradations detected from the official status page.
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 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
This incident has been resolved.
### **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
Between 14:15 UTC and 14:22 UTC, a brief degradation in the hCaptcha service caused intermittent API errors for some users. The upstream issue has been resolved, and our services are operating normally. -- For more details - https://www.hcaptchastatus.com/incidents/ztn3pw8tg2cv
We have concluded our monitoring period and observed no further issues. All systems are operating normally. Thank you for your continued patience.
We observed minor service degradation in API responses from 11:19 UTC to 11:23 UTC due to an internal server issue, which resulted in an unexpected increase in API failures in the US region. We apologize for any inconvenience caused.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Chargebee status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.chargebee.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
