Compare the status, incidents stats and history between Chargebee and ChartMogul
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
We have identified an issue where the Merchant UI Console is returning a “404 Not Found” error when any special characters are included in customer, subscriptions, and invoice handles. Our engineer...
Chargebee has detected an issue that impacted some customers, potentially resulting in elevated errors in the API calls. The errors are stopped and we are currently monitoring it.
Chargebee has detected an issue that impacted multiple customers, potentially resulting in elevated errors in the API requests. While we are providing an early notification in an effort to alert as...
We have identified an issue in recent deployment and we are reverting it, the app will be back in a couple of minutes.
We have identified an issue in recent deployment and reverting it, the app will be back in a couple of minutes.
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. We are investigating the cause right now.
Try it out! How much time you'll save your team, by having the outages information close to them?