18:01 UTC – The issue has been resolved. The issue affected a limited number of sites for approximately three minutes. If you experience any connection timeout issues, please contact the Help Desk: email@example.com
17:44 UTC – Our systems team is currently investigating reports of connection timeouts. As soon as we have more information, we will update this post.
11:47 UTC – The issue is now resolved. It was caused by a problem with a file server. We apologize for the inconvenience. If you have questions or concerns, please contact the Help Desk: firstname.lastname@example.org
11:27 UTC – The systems team is investigating 502 Bad Gateway Errors, which are affecting several sites on our platform. As soon as we have more information, we will update this post.
1:16 UTC – This issue has been resolved. If you have any questions, please reach out to email@example.com.
12:57 UTC – Pressable’s systems team is investigating an issue that is causing some sites on our platform not to load due to connection timeouts. We will update this post with more information as it becomes available.
22:40 UTC – Maintenance has ended. Thank you!
19:50 UTC – Our systems team is conducting maintenance that may cause SFTP access to become intermittent at times. We will update this post with more information once the maintenance is finished. If you need assistance, please contact the Help Desk: firstname.lastname@example.org
4:50 UTC February 28 – The CDN for all sites in Production Mode has been re-enabled over the past 4 hours. We appreciate your patience on this issue. If you have any questions, please contact the Help Desk: email@example.com.
23:21 UTC February 27 – Our CDN provider reports that they have resolved the issue. The Pressable systems team will begin reactivating the CDN later this evening for those who had them deactivated earlier.
20:21 UTC / February 27 – Our CDN provider reports that they have isolated this issue to a single router. They have assured us that resolving the issue remains a high priority. In the meantime, we have begun disabling the CDN on a limited number of sites as a short term solution. So far, CDN deactivation has had a minimal impact on server performance, and our systems team has decided to continue with the deactivation of the CDN on additional server pools. We must stress that this is a temporary measure and that we are actively evaluating other options – both medium and long term – to solve for this issue. As always, we thank you again for your continued patience and understanding.
18:24 UTC / February 27 – This issue continues to impact several sites on our platform intermittently. While we remain in contact with our CDN provider to resolve this issue, we have begun exploring alternative measures. As soon as we have more information, we will update here. In the meantime, we greatly appreciate your patience and understanding.
14:29 UTC / February 26 – We continue to work with our CDN provider to address this issue. We have reiterated the urgency of having this issue resolved as soon as possible to our provider. If you detect assets from our CDN URLs (
https://*-zippykid.netdna-ssl.com ) taking significant amounts of time to load or not loading at all, we recommend turning off Production Mode for the time being. We thank you for your continued patience.
1:17 UTC / February 26 – We are still working with our CDN provider to determine what is causing some of our sites to experience longer response and load times. We will continue to update this page as new information is available.
16:24 UTC / February 25 – Our systems team has begun investigating an intermittent issue we are seeing with our CDN provider. In some cases, we are noticing sites take longer to respond and load due to a delay in retrieving images from our CDN provider. We will update this status page as new information is available.
At 6:46 AM UTC, our systems team began investigating 502 Bad Gateway errors affecting several sites on our platform. The issue coincided with scheduled maintenance at our network provider that was to begin approximately at 6:00 AM UTC. Consequently, at 7:20 AM UTC we contacted our network provider to address the issue. By 8:30 AM UTC, the issue was resolved.
If you have any questions or need assistance, please contact the Help Desk: firstname.lastname@example.org
4:15 UTC – Our systems team has located the issue and is working to address it fully. However, all affected sites should be functioning normally at this time. If you have any questions, please contact the Help Desk: email@example.com
3:49 UTC – We have detected an issue on our platform causing 502 Bad Gateway Errors on some sites. We are investigating and will post more information as it becomes available.