outages.live
Live
Chargebee logoChargebeeMaintenance ·

Receivables Service Degradation

MaintenanceOfficial update

Due to ongoing emergency maintenance, merchants will temporarily be unable to access Receivables. We will keep you posted with updates as we progress.

The latest update from Chargebee.

State

Identified

Started

Ongoing for

1 h 44 min

Worst impact

Maintenance

Timeline

1 update
21:0721:3321:5922:2522:51
MaintenanceUpdate postedTimes in UTC

Identified

1 h 44 min 100%

Updates

Times in UTC

As posted by Chargebee

Identified

Due to ongoing emergency maintenance, merchants will temporarily be unable to access Receivables. We will keep you posted with updates as we progress.

Affected components

4
Receivables UIReceivables APIChargebee Receivables - Receivables UIChargebee Receivables - Receivables API

Chargebee in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

24

Median duration

41 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 days
median 41 min
90 days agoToday

Other Chargebee incidents

All incidents
Chargebee logo

Chargebee·Microsoft 365 Service Degradation

Chargebee reports degraded Microsoft 365 and Email & SMTP Services for Microsoft 365. Merchants using custom SMTP with Microsoft 365 can get delayed or failed email notifications. Chargebee monitors the situation and retries pending notifications when the service is restored.

Degraded
Chargebee logo

Chargebee·Partially Degraded Service

Chargebee reports that the Slack Apps/Integrations/APIs component did not work correctly. Chargebee reports that this problem is resolved. The problem lasted 3 minutes.

Resolved
Chargebee logo

Chargebee·Partially Degraded Service

Chargebee reported partially degraded service on Slack Apps/Integrations/APIs. Chargebee reports that the incident is resolved. The incident lasted 213 minutes.

Resolved
Chargebee logo

Chargebee·API Service Degradation - EU Region

This incident has been resolved.

Resolved
Chargebee logo

Chargebee·Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability

Chargebee reports no impact to its services or customer integrations from the PHPshell zero-day vulnerability. This affects Product Security. Chargebee marked the incident resolved on 3 November 2026, about 11 days after it started.

Resolved

Follow Chargebee

Your coding agent knows when Chargebee is down, and tells you when a failure is theirs, not yours. You can also get Chargebee incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "chargebee" and tell me if Chargebee has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=chargebee
Slack
/feed subscribe https://outages.live/feed.xml?providers=chargebee

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane