rewindex

CompaniesChargebeeIncidents

Chargebee: API Latency Issue

MinorStatus: resolvedStarted Resolved (25 min)1 updatestatus.chargebee.com (opens in new tab)

Timeline of updates

  1. resolved

    We noticed marginal performance degradation in Chargebee API service, during 12:38 to 14:23, 23/07/2020. This event occurred due to query performance issues in a recent change, which in-turn induced load in few of the db shards. Post the identification, the change was reverted to normalise the load. Set of customers were affected during this event, we have communicated and updated the affected customers via Support.

From Chargebee’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.chargebee.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Chargebee, started 2020-07-23 14:27 UTC, resolved after 25 min, 1 update(s).

Title
API Latency Issue
Vendor
Chargebee
Date
URL
https://rewindex.com/company/chargebee/incidents/v6v0zclwcqbk

Chargebee profileRecent Chargebee incidentsAll outages on July 23, 2020Chargebee in July 2020MarkdownJSON