All Systems Operational
API   Operational
Hosted Pages   Operational
Merchant Console   Operational
Customer Portal   Operational
Notifications Operational
Email   Operational
Webhook   Operational
Payment Processors Operational
Amazon Payments   Operational
Authorize.Net   Operational
Braintree API   Operational
eWay   Operational
PayPal   Operational
Pin Payments   Operational
Spreedly   Operational
Stripe API   Operational
WorldPay   Operational
Third Party Integrations Operational
Avalara Tax Calculation Service   Operational
AWS S3   Operational
Google Analytics   Operational
MailChimp   Operational
Refersion   Operational
SalesForce   Operational
SendGrid   Operational
Xero   Operational
Slack   Operational
Zapier   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
As you may be aware, the PCI DSS requirements now mandate a secure version of TLS (TLS1.2 and above) for payment systems, i.e to disable SSL and early TLS by 2018. Chargebee has already disabled the use of SSL. We now plan to disable TLS1.0 and TLS1.1 by April 02, 2018.

API Connections: Please contact your web developer, as well as your web hosting company, to confirm that they can support TLS 1.2 for your API connections. There should not be a need to change the code. But you may need to upgrade your Operating System, Components, and Frameworks based on how you use it.

How to test API: Codes are available on the link below for testing. You can execute the code from your production environment to the endpoints (available in the code).

https://support.chargebee.com/support/solutions/articles/231353-tls-1-2-handshake-testing-code

If you need further assistance, email us at support@chargebee.com, and we'll gladly help you out!
Posted on Feb 2, 14:55 UTC
System Metrics Month Week Day
Response Time
Fetching
App Uptime Report
Fetching
Past Incidents
Feb 20, 2018

No incidents reported today.

Feb 19, 2018

No incidents reported.

Feb 18, 2018

No incidents reported.

Feb 17, 2018

No incidents reported.

Feb 16, 2018

No incidents reported.

Feb 15, 2018

No incidents reported.

Feb 14, 2018

No incidents reported.

Feb 13, 2018

No incidents reported.

Feb 12, 2018

No incidents reported.

Feb 11, 2018

No incidents reported.

Feb 10, 2018

No incidents reported.

Feb 9, 2018

No incidents reported.

Feb 8, 2018

No incidents reported.

Feb 7, 2018

No incidents reported.

Feb 6, 2018

No incidents reported.