We are currently experiencing an outage in our Chicago Datacenter. All sites hosted in this data center are currently unresponsive and not loading.

We are addressing this issue now and will have things back up and operational shortly.

UPDATE 5:30PM CST: We’re still experiencing issues with the network backbone at our Chicago DC. We’re working with our provider to determine what the cause is and how we can mitigate this traffic to restore services.

UPDATE 6:05PM CST: We’re still working with our provider to determine the cause of the increased traffic along our backbone. We apologize for the delay in getting things back up and operational.

UPDATE 6:30PM CST: We’re still working with our provider to determine mitigating steps we can take for our internal network. We’ll provide an update in 30 minutes.

UPDATE 7:00PM CST: We’re currently engaging more senior members of our providers team to help troubleshoot the issues. We’ll provide an update in 30 minutes.

UPDATE 7:35PM CST: We’re still working with our provider to diagnose the current issues. We’ll provide an update in 30 minutes.

UPDATE 8:30PM CST: Our team is still working to mitigate the effects of traffic on our backbone. We’ve started to push out configuration changes which we expect to help reduce the impact, but it will be a bit longer before we know the impact of these changes. We’ll provide an update in 30 minutes.

UPDATE 10:05PM CST: Our team is still working to restore services. We’ll provide an update in 30 minutes.

UPDATE 10:40PM CST: Our team is beginning some work to bring servers back online and then will continue to evaluate issues. We do not expect services to return to normal at this time and will provide another update in 30 minutes.

UPDATE Jan, 10th, 2015 @ 12:30AM CST: Our team is still working on bringing servers back online and undergoing internal troubleshooting processes. We will continue to update the status blog as often as possible.

UPDATE Jan 10th, 2015 @ 1:25AM CST: We’re currently experiencing delays in the restoration of services as Rackspace is having provider line issues. We’ll continue our efforts as best as possible while Rackspace works to improve their provider issue. (https://status.rackspace.com/)

UPDATE Jan 10th, 2015 @ 2:45AM CST: The team is still working to bring services back online following issues from yesterday. We will continue to update the status blog as we make progress.

UPDATE Jan 10th, 2015 @ 6:05AM CST: Our team is still working to bring services back online. Some sites may have begun responding over the past hour, however, capacity is still not back to 100%. We’ll provide more updates as we progress.

UPDATE Jan 10th, 2015 @ 7:30AM CST: The team is still bringing services back online from the outage. We will provide more updates as we have them.

UPDATE Jan 10th, 2015 @ 9:00AM CST: We’re still working on bringing services back online related to this outage. We’ll provide more information as progress is made.

UPDATE Jan 10th, 2015 @ 10:00AM CST: Our team is still working to resolve issues related to connectivity and site availability. We’ll provide an update when we have more information.

UPDATE Jan 10th, 2015 @ 11:45AM CST: The team is making some configuration changes while we work to bring additional capacity online. We’ll provide an update when there is more progress.

UPDATE Jan 10th, 2015 @ 1:20PM CST: The team is making progress and we hope to have all systems back up and running soon. Some sites may have begun responding over the past hour, however, capacity is still not back to 100%. We’ll provide more updates as we progress.

UPDATE Jan 10th, 2015 @ 3:30PM CST: The team has made updates to the system that will help get things running and stable. Capacity is still not back to 100%. We’ll provide more updates as we progress.

UPDATE Jan 10th, 2015 @ 6:20PM CST: Sites are beginning to be served now but you may encounter the intermittent 502 error while things continue to settle. We’ll provide more updates as we progress.

UPDATE Jan 10th, 2015 @ 9:20PM CST: Customers with sites on our “Thor” cluster should see their sites being served properly now. We’re finalizing some work on our “Bode” and “Galaxy01” clusters and expect those to be functional shortly. We’ll provide more updates as we progress.

UPDATE Jan 11th, 2015 @ 9:15AM CST: We wanted to get another note out to let everyone know that we’ve seen stability restored (as of last night) and are currently seeing all systems online. We sincerely regret the experience provided over the last several days, but do appreciate your continued patience. Tomorrow we’ll be providing a more detailed analysis of the issues and our steps to correct these issues moving forward.

We are currently experiencing a high number of bot traffic affecting customers on the cluster “galaxy01”. This will result in some sites not being able to display or function. We are working on getting this resolve and will continue to update the status of this issue here.

If you have any questions, please submit a ticket via your my.pressable.com control panel.

Update 12:58 P.M.- We are continuing to investigate the issue causing some sites on different clusters that are getting 502 errors. If you have any questions please submit a ticket in your my.pressable.com control panel.

UPDATE 3:05PM CST: At this time we’ve seen stability across the systems for the last 90 minutes. We’re still continuing our investigation into the cause of these issues, but wanted to let you know some normalcy has returned. Our apologies for the issues this week.

We’re currently experiencing an issue impacting our edge devices that’s causing sites and internal systems to be inaccessible. We’re investigating with our provider and will provide an update when we have more information.

UPDATE 10:20PM CST: Our provider is investigating the issue and believes it may be related to a DDOS attack against another customer of theirs which is saturating the internal networks at the datacenter. We’re continuing to work with our partners to restore services ASAP.

UPDATE 10:30PM CST: Our provider is informing us that the attack appears to have subsided for the time being. At this time our systems are beginning to return to normal and we’re continuing to monitor for any lingering issues.

UPDATE 10:50PM CST: At this time we’re seeing our systems operating at normal levels. We’ll continue to monitor for issues, but do not expect there to be any problems related to this incident.

We’re currently experiencing an issue with a cluster named “Galaxy01” that’s causing high load across the system which results in sites being down or displaying 502 error messages. We’re investigating the root cause of this issue and will provide an updates as we have them.

UPDATE 11:15AM CST: We’re continuing to investigate issues causing higher than normal load on the systems. We’re also working to bring new hardware online which we believe may help to alleviate some issues.

UPDATE 12:25PM CST: We’re currently in the process of bringing the new hardware online which is causing some downtime while it starts taking traffic. We apologize for the issue and expect the new hardware to be 100% functional shortly.

UPDATE 1:00PM CST: The new hardware is online and we’re starting to see usage return to normal. We’ll provide an update when things are more stable on the systems.

UPDATE 3:25PM CST: We’ve seen stability in the systems for the past hour and are continuing to monitor systems. If you notice any issues, please let us know.

Howdy,

Our servers are currently under attack and this has caused some of our databases to run behind and result in sites not displaying, updating, or functioning properly.

We have already begun banning IPs before they hit out load balancers and are working toward reducing the impact and footprint of this.

We will update the status blog again once this attack has subsided.

If you have questions or concerns, please contact our helpdesk via your panel at  https://my.pressable.com.

Thank you!

UPDATE – 01/05/2015 @ 11:56AM Central: 

We are seeing the slave database servers as caught up and sites should be functioning properly now. If you are still experiencing issues, please contact us via https://my.pressable.com

UPDATE – 01/05/2015 @ 12:25AM Central: 

The slave databases have fallen behind again and we are attempting to get them caught back up. Although they had originally caught back up, they are now behind once more and you may be experiencing some issues (logging in to your site, content updates not display, etc.). We will update once we have seen sustained stability and synchronization on these database servers.

Please let me know if you have any questions, thanks!

Howdy,

2014 has nearly run its course and the holiday season is upon us. The Pressable staff wants to thank everyone for supporting us through this year and helping us find new ways to improve our services.

In observance of the holiday on November 27th, 2014, we will have a reduced support staff on hand and will be operating with minimal support response on both November 27th and 28th. We will resume operating under normal support hours on November 29th, 2014.

Minimal Support Response means that we won’t be available to respond to non-emergency requests. There will be support staff standing by, but we use our best judgement to determine emergency issues that need our attention immediately.

We hope everyone enjoys their holiday and look forward to serving you through the rest of the year.

Thank you!

Due to a miscommunication between us and our service provider Rackspace, the majority of websites hosted at our Chicago datacenter are offline.  We are on the phone with Rackspace working to restore the servers that are needed to bring these websites online as quickly as possible. 

As of Saturday October 25th 8:31AM. All services are running properly.

We are aware of the recently announced vulnerability in SSL called POODLE. This vulnerability affects a very small percentage of traffic on our systems.

You can read more about this vulnerability at the following links:

https://isc.sans.edu/diary/OpenSSL%3A+SSLv3+POODLE+Vulnerability+Official+Release/18827

Click to access ssl-poodle.pdf

The “fix” for this issue is to disable SSLv3 on servers and/or clients that utilize it. Fortunately, it is in use in a very small percentage of traffic and is not likely to hinder traffic to sites we host in any significant capacity.

The recommended solution to this problem will make clients using Internet Explorer 6 running on Windows XP or older recieve an SSL error.

Currently, this fix will also break the Pingdom monitoring service SSL check. Pingdom is aware of this issue and is making the appropriate changes to their systems.

We are aware of the inconvenience this may cause, but we believe that this is the right thing to do.

You can see larger providers implement similar policies here.

https://chargify.com/blog/dropping-sslv3/
https://blog.cloudflare.com/sslv3-support-disabled-by-default-due-to-vulnerability/

If you have any questions or concerns, please contact our help desk by submitting a ticket from https://my.pressable.com.

Howdy,

We are currently experiencing an issues with our slave database servers that is causing some sites in our network to serve stale content. We are aware of these issues and are working toward resolving them now.

This is not currently causing sites to be unavailable, just serve old content in some cases.

If you have any questions or concerns, please contact our help desk by submitting a ticket via your https://my.pressable.com control panel.

IMPORTANT: Sucuri has released details on an exploit for the plugin Slider Revolution Responsive WordPress Plugin. Details of the exploit can be seen on Sucuri’s blog.

IF YOU ARE USING THIS PLUGIN, PLEASE UPDATE TO THE LATEST VERSION IMMEDIATELY.

Our team is working on a way to block these attacks, but we can NOT update this plugin on sites as it’s not freely available on the WordPress.org repository.