All Systems Operational

About This Site

Get the latest info about how Chargify is running. We'll keep you updated if there are any issues.

Main Application Operational
90 days ago
100.0 % uptime
Today
Billing Portal Operational
API Operational
Chargify Direct Operational
Scheduled Payment Processing Operational
Email sending Operational
Documentation Site ? Operational
Integrations to 3rd Party Services ? Operational
Webhooks ? Operational
90 days ago
99.99 % uptime
Today
Chargify Hosted Pages ? Operational
90 days ago
100.0 % uptime
Today
Data Exports Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Jun 6, 2020

No incidents reported today.

Jun 5, 2020
Completed - This maintenance window is completed.
Jun 5, 15:26 CDT
Update - All customer-facing certificates have been replaced. Please reach out if you have any further connectivity issues.
Jun 5, 15:24 CDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 11:47 CDT
Scheduled - Over the weekend, we have taken steps to remove the offending expired AddTrust External CA Root from our certificate bundles. This has resolved SSL issues with our API for most of our merchants. We are still working to reissue our certificates in a manner that these much older clients can trust.

Some merchants may still experience issues accessing the Chargify API via a client that does not have updated trusted root certificates.

In the meantime, Chargify merchants can fix this for themselves by adding more recent root certificates to their trust stores. Add either one of these to the certificate store used by your client:
https://crt.sh/?id=1199354
https://crt.sh/?id=1720081

Note the “Download Certificate: PEM” link on the above webpages to obtain the certificate.

For example, if you are using curl as your client, you can specify a certificate authority file to use:
curl --cacert /etc/ssl/1199354.crt -u API_KEY:X https://subdomain.chargify.com/subscriptions.json

The above is an example. How to install or use the updated certificate is dependent on your client.
You can learn more here: https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA03l00000117LT
Jun 1, 11:44 CDT
Jun 4, 2020

No incidents reported.

Jun 3, 2020

No incidents reported.

Jun 2, 2020

No incidents reported.

Jun 1, 2020
May 31, 2020

No incidents reported.

May 30, 2020
Resolved - This incident has been resolved.

Update:
We found some additional webhooks that were not a part of our re-send on 5/30 ~4:30pm ET that were subsequently sent on 5/31 at ~11:30pm ET because they were deemed safe to resend. These webhooks were for subscriptions that had not generated additional webhooks after 5/30, so they contain the most up-to-date information.

We found a much smaller group of webhooks that were not re-sent that were deemed not safe to resend. A customer support representative will be reaching out to the affected merchants.
May 30, 15:35 CDT
Update - All webhooks have been successfully resent and this incident has been resolved. Please contact support if you have any questions or issues.
May 30, 15:34 CDT
Update - There have been some merchant-defined webhooks that have failed due to the expired certificate being returned in the CA bundle from those merchant-controlled servers. We have updated our client code to ignore that expired certificate and will be re-sending the webhooks.

There have also been some internal webhooks related to our Salesforce v1, QBO, and Xero integrations that have failed due to the certificate issues. We will be re-sending those as well, so any delays you currently see in your sync to those third party apps will be resolved shortly.
May 30, 14:43 CDT
Monitoring - A fix has been implemented to the CA bundle on the server-side, and we are monitoring the results.
May 30, 13:34 CDT
Update - You may experience problems accessing the Chargify API via a client that does not have updated trusted root certificates.

Chargify is in the process of attempting to replace an intermediate certificate which may, for some clients, force them to use a more recent (and unexpired) root that they already trust.

In the meantime, Chargify merchants can fix this for themselves by adding more recent root certificates to their trust stores. Add either one of these to the certificate store used by your client:

https://crt.sh/?id=1199354
https://crt.sh/?id=1720081

Note the "Download Certificate: PEM" link on the above webpages to obtain the certificate.

For example, if you are using curl as your client, you can specify a certificate authority file to use:

```
curl --cacert /etc/ssl/1199354.crt -u API_KEY:X https://subdomain.chargify.com/subscriptions.json
```

The above is an example. How to install or use the updated certificate is dependent on your client.
You can learn more here: https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA03l00000117LT
May 30, 11:02 CDT
Identified - An upstream SSL Signing Certificate has expired and we are actively working to redeploy our SSL Certificates to exclude this signing certificate from our bundle. The issue shouldn't affect browsers but will affect curl and openssl clients. Merchants can update their clients to resolve the issue while we work to redeploy our certificates.
May 30, 10:18 CDT
Investigating - We are currently investigating reports of a potential service interruption with the Chargify API. We apologize for any inconvenience and will post another update as soon as we learn more.
May 30, 09:57 CDT
May 29, 2020

No incidents reported.

May 28, 2020
Resolved - Square has since resolved the performance issues as of 17:54 PDT.
May 28, 21:10 CDT
Monitoring - Square is currently monitoring a performance issue on their end. If you utilize the Chargify+Square solution, you may experience delays in transactions being reflected or other errors. Their latest update is as follows:

*****
Monitoring:
May 28, 12:06 PDT
We’re beginning to see services recover, and we’ll continue to monitor as our Engineers work to ensure the fix will completely resolve the issues.

We want to assure you that throughout this outage, physical card payments have not been affected and have processed as normal, despite a delay in being reflected within transactions.

Thank you for being patient with us, and we’ll return with another update here shortly.
*****

We will continue to monitor their status page, and more information is available at https://www.issquareup.com/
May 28, 14:45 CDT
May 27, 2020

No incidents reported.

May 26, 2020

No incidents reported.

May 25, 2020

No incidents reported.

May 24, 2020

No incidents reported.

May 23, 2020

No incidents reported.