Maintenance Chargebee outage dossier
chargebee.com · Official status page (Statuspage-compatible JSON)
Active official incident: Security Notice: No Impact to Chargebee Services from Recent NGINX & Java4shell CVEs
Known long-running issue (limited scope, not counted in the headline): Receivables Service Degradation · why
Official status now
Maintenance Maintenance
2 of 86 components 1 known long-running issue checked 0 min ago How we score status
Service Under Maintenance
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Light rain: official status: Maintenance
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 2 none
- 12 minor
- 1 critical
- 3 major
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- · ongoingSecurity Notice: No Impact to Chargebee Services from Recent NGINX & Java4shell CVEsnone investigating · Product Security · official notice ↗ · replay & discuss1 of 86 componentsstarted 2026-11-20active · open 15 hupdated 15 h ago
- → resolved · lasted 2.5 hAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
- → resolved · lasted 1.4 hAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
- · ongoingReceivables Service Degradationcritical identified · Receivables UI, Receivables API · official notice ↗ · replay & discuss2 of 86 componentsstarted 2026-11-13stale / unchanged · open 7 daysupdated 4 days agoknown long-running issue
- → resolved · lasted 29.3 hMicrosoft 365 Service Degradationminor resolved · Microsoft 365 · official notice ↗ · replay & discuss
- → resolved · lasted 41 minAPI Service Degradation - EU Regionmajor resolved · API (EU) · official notice ↗ · replay & discuss
- → resolved · lasted 11.6 daysSecurity Notice: No Impact from PHPshell Zero-Day Vulnerabilitynone resolved · Product Security · official notice ↗ · replay & discuss
- → resolved · lasted 0 minAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
- → resolved · lasted 42.9 hAPI Service Degradation - EU Regionminor resolved · API (EU) · official notice ↗ · replay & discuss
- → resolved · lasted 0 minAPI Service Degradationminor resolved · API (EU) · official notice ↗ · replay & discuss
- → resolved · lasted 2 hAPI Service Degradationmajor resolved · API (US) · official notice ↗ · replay & discuss
- → resolved · lasted 0 minAPI Service Degradationminor resolved · API (EU) · official notice ↗ · replay & discuss
- → resolved · lasted 50 minSignup Degradationminor resolved · official notice ↗ · replay & discuss
- → resolved · lasted 1.1 hApplication Login Issuesminor resolved · Admin Console (US), Admin Console (EU), Admin Console (AU) · official notice ↗ · replay & discuss
- → resolved · lasted 22 minAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
- → resolved · lasted 8 minAPI Service Degradationmajor resolved · API (US) · official notice ↗ · replay & discuss
- → resolved · lasted 0 minQuickBooks Online Service Degradationminor resolved · QuickBooks · official notice ↗ · replay & discuss
- → resolved · lasted 1.8 hAvalara Service Degradationminor resolved · Avalara · official notice ↗ · replay & discuss
Related services
- no official feedStripeno official feed→
- no official feedPayPalno official feed→
- OperationalSquareOperational→
- no official feedAdyenno official feed→
- no official feedBraintreeno official feed→
- no official feedCheckout.comno official feed→
- OperationalPlaidOperational→
- Degraded / minor incidentWiseDegraded / minor incident→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.