CHYP.ai · ORBIT // Cloudy_Day Security Suite

Outages · Payments

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

88

Light rain: official status: Maintenance

At a glance

18official incidents, 90 d
100%of our checks clean (10)
1.1 hmedian time to resolve
0visitor reports, 24 h
0reports, last 15 min
0status changes recorded

90-day timeline (1 day tracked)

2026-08-24: no data yet2026-08-25: no data yet2026-08-26: no data yet2026-08-27: no data yet2026-08-28: no data yet2026-08-29: no data yet2026-08-30: no data yet2026-08-31: no data yet2026-09-01: no data yet2026-09-02: no data yet2026-09-03: no data yet2026-09-04: no data yet2026-09-05: no data yet2026-09-06: no data yet2026-09-07: no data yet2026-09-08: no data yet2026-09-09: no data yet2026-09-10: no data yet2026-09-11: no data yet2026-09-12: no data yet2026-09-13: no data yet2026-09-14: no data yet2026-09-15: no data yet2026-09-16: no data yet2026-09-17: no data yet2026-09-18: no data yet2026-09-19: no data yet2026-09-20: no data yet2026-09-21: no data yet2026-09-22: no data yet2026-09-23: no data yet2026-09-24: no data yet2026-09-25: no data yet2026-09-26: no data yet2026-09-27: no data yet2026-09-28: no data yet2026-09-29: no data yet2026-09-30: no data yet2026-10-01: no data yet2026-10-02: no data yet2026-10-03: no data yet2026-10-04: no data yet2026-10-05: no data yet2026-10-06: no data yet2026-10-07: no data yet2026-10-08: no data yet2026-10-09: no data yet2026-10-10: no data yet2026-10-11: no data yet2026-10-12: no data yet2026-10-13: no data yet2026-10-14: no data yet2026-10-15: no data yet2026-10-16: no data yet2026-10-17: no data yet2026-10-18: no data yet2026-10-19: no data yet2026-10-20: no data yet2026-10-21: no data yet2026-10-22: no data yet2026-10-23: no data yet2026-10-24: no data yet2026-10-25: no data yet2026-10-26: no data yet2026-10-27: no data yet2026-10-28: no data yet2026-10-29: no data yet2026-10-30: no data yet2026-10-31: no data yet2026-11-01: no data yet2026-11-02: no data yet2026-11-03: no data yet2026-11-04: no data yet2026-11-05: no data yet2026-11-06: no data yet2026-11-07: no data yet2026-11-08: no data yet2026-11-09: no data yet2026-11-10: no data yet2026-11-11: no data yet2026-11-12: no data yet2026-11-13: no data yet2026-11-14: no data yet2026-11-15: no data yet2026-11-16: no data yet2026-11-17: no data yet2026-11-18: no data yet2026-11-19: no data yet2026-11-20: no data yet2026-11-21: 10 checks, 0 with an official incident (worst: maintenance)90 days agotoday

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

1 incident(s), week ending 2026-08-2915 incident(s), week ending 2026-09-0550 incident(s), week ending 2026-09-121 incident(s), week ending 2026-09-1910 incident(s), week ending 2026-09-262 incident(s), week ending 2026-10-0321 incident(s), week ending 2026-10-1011 incident(s), week ending 2026-10-1711 incident(s), week ending 2026-10-2411 incident(s), week ending 2026-10-3110 incident(s), week ending 2026-11-072 incident(s), week ending 2026-11-1423 incident(s), week ending 2026-11-21313 weeks agothis weekmax 5/week

Impact mix, 90 d

1 critical3 major12 minor2 none18
  • 2 none
  • 12 minor
  • 1 critical
  • 3 major

Visitor reports, last 24 h

24 h agonow · peak 1/15 min

Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.

Incident history

  1. · 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
  2. → resolved · lasted 2.5 hAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
  3. → resolved · lasted 1.4 hAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
  4. · 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
  5. → resolved · lasted 29.3 hMicrosoft 365 Service Degradationminor resolved · Microsoft 365 · official notice ↗ · replay & discuss
  6. → resolved · lasted 41 minAPI Service Degradation - EU Regionmajor resolved · API (EU) · official notice ↗ · replay & discuss
  7. → resolved · lasted 11.6 daysSecurity Notice: No Impact from PHPshell Zero-Day Vulnerabilitynone resolved · Product Security · official notice ↗ · replay & discuss
  8. → resolved · lasted 0 minAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
  9. → resolved · lasted 42.9 hAPI Service Degradation - EU Regionminor resolved · API (EU) · official notice ↗ · replay & discuss
  10. → resolved · lasted 0 minAPI Service Degradationminor resolved · API (EU) · official notice ↗ · replay & discuss
  11. → resolved · lasted 2 hAPI Service Degradationmajor resolved · API (US) · official notice ↗ · replay & discuss
  12. → resolved · lasted 0 minAPI Service Degradationminor resolved · API (EU) · official notice ↗ · replay & discuss
  13. → resolved · lasted 50 minSignup Degradationminor resolved · official notice ↗ · replay & discuss
  14. → resolved · lasted 1.1 hApplication Login Issuesminor resolved · Admin Console (US), Admin Console (EU), Admin Console (AU) · official notice ↗ · replay & discuss
  15. → resolved · lasted 22 minAPI Service Degradationminor resolved · API (US) · official notice ↗ · replay & discuss
  16. → resolved · lasted 8 minAPI Service Degradationmajor resolved · API (US) · official notice ↗ · replay & discuss
  17. → resolved · lasted 0 minQuickBooks Online Service Degradationminor resolved · QuickBooks · official notice ↗ · replay & discuss
  18. → resolved · lasted 1.8 hAvalara Service Degradationminor resolved · Avalara · official notice ↗ · replay & discuss

Related services

"Runs on" links are inferred from public information and may be outdated.

How we score status

  1. 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.
  2. 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.
  3. 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).
  4. 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.
  5. 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.

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.

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.

Where to next