[Fixed] Web550 inaccessible
Web550 is currently inaccessible. We are looking into the issue and will resolve it as quickly as possible.
2018-07-02 23:09 UTC: Web550 is back online.
Web550 is currently inaccessible. We are looking into the issue and will resolve it as quickly as possible.
2018-07-02 23:09 UTC: Web550 is back online.
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.
The server is currently not accessible. We are looking into the issue and will resolve as quickly as possible.
2018-06-30 22:34 UTC: Mailbox17 is back online.
Web620 is currently inaccessible. We are looking into the issue and will resolve it as quickly as possible.
2018-06-29 04:40 UTC: Web620 is back online.
Web554 is currently inaccessible. We are looking into the issue and will resolve it as quickly as possible.
2018-06-20 07:01 UTC: Web554 is back online.
Mon Jun 18 00:02:08 UTC 2018: Some servers in our Singapore datacenters are not accessible. We’re working with them to resolve the situation as soon as possible. Please stand by.
Mon Jun 18 00:27:18 UTC 2018: There is an issue with a router that serves some servers in Singapore:
Web321, Web322, Web323, Web339, Web360, Web375, Web379, Web409, Web424, Web429, Web442, Web463, Web474, Web486, Web505, Web508, Web517
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.
In order to meet the latest PCI Data Security Standards (PCI DSS) we will be dropping support for TLS 1.0 and the TLS_RSA_WITH_3DES_EDE_CBC_SHA ciphers on all servers in our infrastructure.
The deadline set from the PCI Security Standards Council is the 30th of June, 2018. You can read more about it here.
After this update, customers using legacy browsers and user agents will be unable to access any SSL secured website hosted in our platform.
These user agents include but not limited to:
If your browser and operating system is up to date, then you should probably be OK.
If you are unsure whether this change will affect you or not you can visit this test page.
If you have any questions regarding this security change, please raise a ticket and our support team will gladly answer your questions.
2018-06-01 14:35 UTC: The shared MySQL database service on Web536 is currently down. We’re working to restore service at this time. We’ll update this post when more information is available.
2018-06-01 17:59 UTC: All databases have been restored.
Web560 is currently inaccessible. This appears to be due to routing problems and we are looking into it.
Wed May 30 04:23:50 UTC 2018: The server is back online.
The frontend web server (nginx) on Web505, Web517 and Web630 is currently down. Our system administrators are working to resolve this issue as soon as possible.
2018-05-28 8:22 UTC: The issue has been resolved and nginx on all 3 servers is now back online.