Skip to content
Back to ChargebeeIncident Postmortem
Chargebee logo

Chargebee

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Chargebee: vendor-reported major incident on September 29 (tracked 3h 0m)

Sep 29, 01:35 PM → Sep 29, 04:35 PM · 3h 0m · high

Chargebee reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3h 0m, from Tue, 29 Sep 2026 13:35:55 GMT to Tue, 29 Sep 2026 16:35:56 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3h 0m
tracked by PulseWatch

Impact

During the 3-hour high-severity disruption, Chargebee's services were affected. This incident was identified through automated monitoring and the vendor's status page. No user reports were collected for this incident, and therefore no specific user-reported features, regions, or issue types can be detailed.

Incident timeline

  1. Sep 29, 01:35 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 29, 01:35 PM

    Status updated: possible issue

  3. Sep 29, 04:35 PM

    PulseWatch closed the incident

Official updates

  1. Sep 29, 01:35 PM

    Chargebee reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash