At approximately 7:24 PM Central on 4/11 (00:24 UTC on 4/12), we experienced a brief outage for some sites on our network. We isolated the issue and site availability was restored to normal at approximately 7:30 PM Central (00:30 UTC).
We will continue to monitor the situation but do not expect further issues. If you have any questions or concerns, please contact our help desk by submitting a ticket from your https://my.pressable.com control panel.
UPDATE: 19:16 UTC everything back to normal
UPDATE: 19:06 UTC services appear to be restored, we are in the process of creating “mystagingwebsite.com” sub-domain entries that failed to create during the outage.
We are aware of a delay that is impacting the creation of sub-domains on the “mystagingwebsite.com” domain for newly created sites. This issue is due to an API outage at our upstream DNS provider. More details will be posted here as they become available.
On Friday, June 10th, at 17:37 UTC (12:37PM Central) we accidentally deployed a platform-wide change that caused the
DB_CHARSET value to be set incorrectly on most Pressable-hosted websites.
DB_CHARSET is very important, as it tells the web server which character set to use when talking to the database server. It’s important that the values on both the web and database servers match and our change caused a mismatch.
We identified the problem and rolled back our changes at 19:52 UTC (2:52PM Central), but during the 2 hours and 15 minutes the problem existed, if you edited any content on your site, there is a chance it’s now corrupt. This corruption can appear in a few different ways, but one obvious way is that quotes might now appear as “gibberish”. Unfortunately, the problem is not limited to pages and posts, but can also affect widgets, settings, etc.
One of the benefits of our new 2.0 platform is a high level of automation and consistency across severs and websites. This should result in a more consistent, predictable, and improved user experience. Unfortunately, in this case, our newfound automation caused a major problem and for that we apologize. We are adding additional tests, checks, and monitoring to ensure a similar problem doesn’t happen in the future.
If your site has been behaving strangely since Friday, please get in touch and we’ll help you restore things to normal.
UPDATE (4:36PM CDT): We’ve corrected this issue, and SFTP access is fully functional across all sites once again. If you are still having trouble, please submit a ticket to our helpdesk in http://my.pressable.com/
We are currently experiencing an issue that is causing SFTP to be unavailable for many customers. We are working diligently toward getting this resolved as soon as possible and will provide updates as they become available.
One of the machines behind our provisioning system has experienced a hardware failure, we are working on replacing the underlying hardware, and expect the machine to be back online in very soon.
In the mean time, functionality like adding, editing, removing a site, or collaborators of a site is not going to work. We apologize for any inconvenience.
Please note: This only affects our control panel, not your actual website.
We just finished dealing with an issue in our Chicago datacenter that was causing several other clusters to experience instability. Our “Ursa” cluster was taking on an extreme amount of traffic that looks to be, in large part, a bot attack.
This happened as a result of the “Ursa” cluster having a set of tools not running appropriately that detects and mitigates issues like this.
We’ve cleared this up and all sites are now back up and running appropriately.
If you have any questions or concerns, please contact our help desk via your https://my.pressable.com control panel.