2018-07-18 18:15 UTC: At this time, we’re unable to process manual payments and cannot set up new payment sources for automatic monthly billing. We’re working to resolve the issue and will update this post when more info is available.
2018-07-18 19:15 UTC: We’ve track this issue down to our payment pre-processor. We are working with them to resolve this.
2018-07-19 15:56 UTC: The issues with our payment pre-processor have been resolved.
We are going to be upgrading the server-wide install of psycopg2, to begin on Monday, July 09, 2018 around 03:00 UTC. This will be a minor version upgrade that may affect running Python applications which interface with PostgreSQL databases, most notably Django, and issues are usually resolved by restarting the application. If you need any assistance, simply open a support ticket and we will be happy to help.
If you are running any Python+PostgreSQL applications, please be aware of this upgrade and inspect the behavior of your app following the roll-out. You can check the version of psycopg2 by printing psycopg2.__version__ from within a python environment.
Note that the latest version of psycopg2 is not compatible with python2 below 2.6, nor with python3 below 3.2. We will not be upgrading psycopg2 for legacy versions in order to avoid breaking operation of applications that still use them.
Our techs are looking at resolving this as soon as possible. Please stand by for updates.
Mon Jun 18 04:17:10 UTC 2018: Some servers are starting to become accessible. We’re still investigating the problem and will make another post as soon as we are sure services have been restored. We thank you all for your patience.
Mon Jun 18 04:58:07 UTC 2018: The issue has been mitigated. Services should be restored. We are still in talks with the datacenter in regards to the cause and ways to prevent future occurrences. You may need to manually start any apps that are not currently running. If you still encounter issues please feel free to open a ticket for us to investigate.
Mon Jun 18 21:12:50 UTC 2018: This issue has been marked as resolved.