Scheduled Maintenance - Oct 15, 2017

On Sunday, October 15, 2017, Chargify has scheduled a one hour maintenance window for our web application, API, and billing platform. The maintenance window is scheduled for one hour beginning at 9:00am UTC / 5:00am EDT / 2:00am PDT during a lower volume period for our customers in different time zones.

We anticipate the maintenance will result in approximately 15 minutes of actual downtime, but have reserved the entire hour to ensure there’s time to get it right. We’ll maintain continuous communication throughout the process on our status site at: http://status.chargify.io

How to prepare

  • During the maintenance window, Chargify’s web app and API will become unavailable.
  • If you have low activity/volume during this period, the maintenance may go unnoticed. If you have higher activity/volume, you may want to prepare a warning statement telling your users to try again after the maintenance window concludes.
  • New signups and transactions will not be accepted by our servers during any period of downtime.
  • Chargify will pause all system-generated renewals, emails, and webhooks during this period. As soon as the maintenance is complete, all pending renewals will be processed and we’ll send all emails and webhooks in queue.
  • If you have background syncs or internal API calls, we recommend pausing them during this window. Alternately, you should verify that your integration code will correctly retry the API calls after the window is over.

Technical Information

During this window, the Chargify app will respond to requests in the following ways:

  • Web users visiting the Chargify app viewing Public Signup Pages: Will see a placeholder page indicating Chargify is unavailable, with the time window and latest info from our status site.
  • API clients requesting or sending a JSON resource: Will receive a 503 Service Unavailable response along with the following JSON body: {"errors": ["Chargify is unavailable for scheduled maintenance"]}
  • API clients requesting or sending an XML resource: Will receive a 503 Service Unavailable response along with the following body:
<?xml version="1.0" encoding="UTF-8"?>
<errors>
 	 <error>Chargify is unavailable for scheduled maintenance.</error>
</errors>

Why is this necessary?

Normally our database maintenance is done through the use of a cluster that allows us to perform changes without downtime or business impact. In this instance, the cluster itself will be upgraded and the version change is significant enough to warrant extra caution.

When the new database comes online, we’ll double check everything before we begin allowing writes to the database to ensure there is no loss of critical transaction data. During this period downtime will occur for anyone interacting with the application.

If you have any questions, please let us know at support@chargify.com.

Thank you for your patience and understanding, and thanks for being a Chargify customer.