Siteleaf Status - Incident Historyhttp://status.siteleaf.com
StatuspageTue, 13 Mar 2018 10:35:25 +0000Publish/preview/sync issues
<p><small>Dec 13, 19:41 UTC</small><br><strong>Resolved</strong> - Previews and publishes should be working as expected. Please reach out to support@siteleaf.com if we can help further!</p><p><small>Dec 13, 16:53 UTC</small><br><strong>Identified</strong> - We've identified the issue and are working on a fix now.</p><p><small>Dec 13, 16:18 UTC</small><br><strong>Investigating</strong> - We're seeing elevated error rates with publishing, previewing, and syncing.</p> Wed, 13 Dec 2017 19:41:41 +0000https://status.siteleaf.com/incidents/1b3xqgvbc1tt
https://status.siteleaf.com/incidents/1b3xqgvbc1ttDelayed sync and publish
<p><small>Jul 9, 21:44 UTC</small><br><strong>Resolved</strong> - Job queues are now caught up and running as expected. Thanks for your patience!</p><p><small>Jul 9, 18:41 UTC</small><br><strong>Update</strong> - We're adding a couple extra servers to help work through the queued jobs quicker.</p><p><small>Jul 9, 18:15 UTC</small><br><strong>Monitoring</strong> - We have identified a delay with sync and publishes, leading to a backlog of queued jobs. Jobs are currently running and should be caught up soon. We will continue to monitor this issue.</p> Sun, 09 Jul 2017 21:44:27 +0000https://status.siteleaf.com/incidents/bkgw6brj5012
https://status.siteleaf.com/incidents/bkgw6brj5012Bug with GitHub sync
<p><small>May 1, 16:22 UTC</small><br><strong>Resolved</strong> - We identified a bug in GitHub sync, which may inadvertently remove files on commit for sites with a large amount of files. The bug has been resolved, but you may need to revert your Git history to undo this commit and restore your files. You can follow these instructions to revert: https://github.com/blog/2019-how-to-undo-almost-anything-with-git
<br />
<br />Please get in touch with support@siteleaf.com if you have any questions. Sorry for the inconvenience!</p> Mon, 01 May 2017 16:22:22 +0000https://status.siteleaf.com/incidents/zt7tjfqn4f2v
https://status.siteleaf.com/incidents/zt7tjfqn4f2vIssues at AWS
<p><small>Mar 1, 00:26 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb 28, 18:17 UTC</small><br><strong>Monitoring</strong> - AWS is reporting increased error rates in the US-EAST-1 region, which may affect uploads, publishes, and v2 preview sites. For more information see: https://status.aws.amazon.com</p> Wed, 01 Mar 2017 00:26:33 +0000https://status.siteleaf.com/incidents/wm51xmlvws0h
https://status.siteleaf.com/incidents/wm51xmlvws0hIntermittent v1 publishing issues
<p><small>Feb 10, 22:17 UTC</small><br><strong>Resolved</strong> - Connectivity has been restored between our v1 servers and our database provider. Thank you everyone for your patience!</p><p><small>Feb 10, 20:48 UTC</small><br><strong>Identified</strong> - We have been seeing intermittent publishing errors on v1 due to connectivity issues with our database provider.</p> Fri, 10 Feb 2017 22:17:00 +0000https://status.siteleaf.com/incidents/4hq29ngsv56f
https://status.siteleaf.com/incidents/4hq29ngsv56fScheduled Maintenance
<p><small>Jan 30, 09:56 UTC</small><br><strong>Completed</strong> - v1 took a little longer to update, but all services are now back online and running smoothly. Thanks for your patience!</p><p><small>Jan 30, 05:01 UTC</small><br><strong>Update</strong> - The management interface for Siteleaf v2 is now back online (manage.siteleaf.com). v1 will follow shortly.</p><p><small>Jan 30, 04:00 UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan 27, 16:57 UTC</small><br><strong>Scheduled</strong> - Siteleaf will be temporarily offline for maintenance beginning Sunday January 29 at 11pm EST (Jan 30 04:00 UTC). We expect this downtime to last up to one hour. During this window, the Management Interface (manage.siteleaf.com) and API (api.siteleaf.com) will not be accessible for both Siteleaf v1 and v2 sites, however your published websites will remain online and unaffected (even Siteleaf hosted sites).</p> Mon, 30 Jan 2017 09:56:12 +0000https://status.siteleaf.com/incidents/6svtkj4z4hg5
https://status.siteleaf.com/incidents/6svtkj4z4hg5Ongoing DDoS attack against Dyn DNS
<p><small>Oct 22, 00:00 UTC</small><br><strong>Resolved</strong> - Siteleaf services remain stable and we are considering this issue resolved. To avoid an outage like this in the future, <a href="http://app.go.mongodb.com/e/es?s=413370795&e=765217&elqTrackId=71ee2d8782a8479193a95cbc0f2f39b7&elq=29f11fdf72154d53b946535be8d1c9a5&elqaid=3431&elqat=1">MongoDB Cloud now splits their DNS traffic between multiple providers</a> to ensure a similar attack on a single provider does have the same impact going forward. Dyn, the target of the global DDoS attack, has published a <a href="https://www.dynstatus.com/incidents/5r9mppc1kb77">Preliminary Findings Report</a>. Thanks everyone for their patience!</p><p><small>Oct 21, 19:47 UTC</small><br><strong>Update</strong> - Siteleaf services have stabilized, but we'll continue to monitor.</p><p><small>Oct 21, 16:31 UTC</small><br><strong>Monitoring</strong> - As of 15:52 UTC, Dyn is <a href="https://www.dynstatus.com/incidents/nlr4yrr162t8">reporting another DDoS attack</a> against our their DNS infrastructure. While Siteleaf does not use this service directly, it is affecting our database provider MongoDB Cloud. As a result both Siteleaf v1 and v2 are suffering intermittent outages. We'll continue to monitor and update this page.</p> Sat, 22 Oct 2016 00:00:48 +0000https://status.siteleaf.com/incidents/n650ys77dlx7
https://status.siteleaf.com/incidents/n650ys77dlx7Upstream DNS outage
<p><small>Oct 21, 13:35 UTC</small><br><strong>Resolved</strong> - This incident has been <a href="https://www.dynstatus.com/incidents/nlr4yrr162t8">confirmed resolved</a> by MongoDB's DNS provider, though we will continue to monitor.</p><p><small>Oct 21, 13:21 UTC</small><br><strong>Monitoring</strong> - We're able to connect to our database provider again and Siteleaf is back online. We'll continue to monitor the situation and keep you updated if anything changes.</p><p><small>Oct 21, 13:03 UTC</small><br><strong>Update</strong> - We've confirmed the DNS provider used by our database (MongoDB Cloud) is currently undergoing a DDoS attack. More information here: https://www.dynstatus.com/incidents/nlr4yrr162t8</p><p><small>Oct 21, 12:23 UTC</small><br><strong>Update</strong> - The outage appears to be coming from an upstream DNS issue affecting our database provider MongoDB Cloud. Many other services we rely on including GitHub and CircleCI are also affected.</p><p><small>Oct 21, 12:00 UTC</small><br><strong>Investigating</strong> - We are currently investigating a server outage that is affecting both v1 and v2. Stay tuned for updates.</p> Fri, 21 Oct 2016 13:35:00 +0000https://status.siteleaf.com/incidents/8gfcn26gvjll
https://status.siteleaf.com/incidents/8gfcn26gvjllAdmin downtime
<p><small>Oct 3, 16:31 UTC</small><br><strong>Resolved</strong> - Everything should be running smoothly again! Get in touch with support if you notice any troubles with your site.</p><p><small>Oct 3, 15:30 UTC</small><br><strong>Identified</strong> - We ran into an issue deploying a new version of the Siteleaf admin and should have things up and running soon.</p> Mon, 03 Oct 2016 16:31:23 +0000https://status.siteleaf.com/incidents/y5yvqv4xr54k
https://status.siteleaf.com/incidents/y5yvqv4xr54kv1 downtime
<p><small>Jun 5, 11:21 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun 5, 06:00 UTC</small><br><strong>Monitoring</strong> - We determined the issue was caused by a bad IP assigned to one of our load balancers by AWS, our hosting provider. It has since been resolved and we will continue to monitor it.</p><p><small>Jun 5, 04:39 UTC</small><br><strong>Investigating</strong> - We are currently investigating unusual traffic on Siteleaf v1 which resulted in intermittent downtime late Saturday night.</p> Sun, 05 Jun 2016 11:21:47 +0000https://status.siteleaf.com/incidents/wrlg9zq33dsd
https://status.siteleaf.com/incidents/wrlg9zq33dsdv2 Upgrade
<p><small>Jan 8, 04:54 UTC</small><br><strong>Resolved</strong> - v2 is back!</p><p><small>Jan 8, 03:36 UTC</small><br><strong>Identified</strong> - We are currently upgrading the v2 beta servers, during this time the v2 admin will be inaccessible. Sorry for the interruption. Note: this only affects v2 beta users, v1 and published sites are not affected.</p> Fri, 08 Jan 2016 04:54:50 +0000https://status.siteleaf.com/incidents/kkhkkfblcgcc
https://status.siteleaf.com/incidents/kkhkkfblcgccv1 Outage
<p><small>Dec 31, 22:59 UTC</small><br><strong>Resolved</strong> - Maintenance is now complete. The root issue was a <a href="https://twitter.com/rubygems_status/status/682684988278607872">CDN outage at Rubygems</a>, which caused issues with our autoscaling environment. We'll continue to monitor, but everything should be back to normal now!</p><p><small>Dec 31, 22:15 UTC</small><br><strong>Identified</strong> - We are currently performing maintenance to resolve an unexpected outage on Siteleaf v1, sorry for the interruption (v2 is not affected).</p> Thu, 31 Dec 2015 22:59:00 +0000https://status.siteleaf.com/incidents/hndmhdmmgngm
https://status.siteleaf.com/incidents/hndmhdmmgngmIntermittent database errors
<p><small>Nov 3, 13:13 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov 3, 04:55 UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov 3, 04:00 UTC</small><br><strong>Identified</strong> - Some users may be seeing an intermittent error when saving pages, which reads "Could not connect to a primary node for replica set". We have identified the issue and are working to resolve it.</p> Tue, 03 Nov 2015 13:13:50 +0000https://status.siteleaf.com/incidents/1jjyd6xb2p9c
https://status.siteleaf.com/incidents/1jjyd6xb2p9cService Outage
<p><small>Sep 28, 15:01 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep 28, 13:46 UTC</small><br><strong>Monitoring</strong> - New servers are up. Monitoring performance.</p><p><small>Sep 28, 13:24 UTC</small><br><strong>Identified</strong> - We’re investigating an outage with our servers at AWS. Sorry for the interruption!</p> Mon, 28 Sep 2015 15:01:06 +0000https://status.siteleaf.com/incidents/rlbyqpsbzs1n
https://status.siteleaf.com/incidents/rlbyqpsbzs1nIntermittent errors
<p><small>Sep 17, 15:08 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep 17, 13:31 UTC</small><br><strong>Monitoring</strong> - We have been seeing intermittent errors due to a server degradation at AWS. A new server has been brought into our cluster and we will continue to monitor the issue. Published sites are not affected.</p> Thu, 17 Sep 2015 15:08:14 +0000https://status.siteleaf.com/incidents/pcf5yr65xzy4
https://status.siteleaf.com/incidents/pcf5yr65xzy4Response Times
<p><small>May 19, 23:22 UTC</small><br><strong>Resolved</strong> - This issue has been resolved.</p><p><small>May 19, 22:56 UTC</small><br><strong>Identified</strong> - We have identified an issue with our servers and are working on a fix.</p> Tue, 19 May 2015 23:22:17 +0000https://status.siteleaf.com/incidents/gt2wwhvsc9j2
https://status.siteleaf.com/incidents/gt2wwhvsc9j2Response time
<p><small>May 8, 16:02 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May 8, 15:07 UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>May 8, 14:56 UTC</small><br><strong>Investigating</strong> - We are investigating slower than normal response times and 504 timeouts, sorry for the interruption.</p> Fri, 08 May 2015 16:02:34 +0000https://status.siteleaf.com/incidents/h8qw6b5c2mqh
https://status.siteleaf.com/incidents/h8qw6b5c2mqhScheduled Maintenance
<p><small>Apr 26, 04:54 UTC</small><br><strong>Completed</strong> - Sorry for the delay, we're back and faster than ever!</p><p><small>Apr 26, 04:07 UTC</small><br><strong>Update</strong> - We are still working on the maintenance, expecting to wrap up within the next half hour. Will continue to update progress.</p><p><small>Apr 26, 03:00 UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Apr 23, 20:15 UTC</small><br><strong>Scheduled</strong> - Siteleaf will be temporarily offline for maintenance beginning Saturday April 25 at 11pm EDT (Apr 26 03:00 UTC). We expect this downtime to last up to one hour. During this window, the Management Interface (manage.siteleaf.com) and API (api.siteleaf.com) will not be accessible, however your published websites will remain online and unaffected (even Siteleaf hosted sites). After the brief downtime we'll be back and faster than ever!</p> Sun, 26 Apr 2015 04:54:50 +0000https://status.siteleaf.com/incidents/c8d8413ky0cj
https://status.siteleaf.com/incidents/c8d8413ky0cjDNS outage
<p><small>Dec 2, 06:32 UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec 2, 00:43 UTC</small><br><strong>Monitoring</strong> - Services on siteleaf.com have been restored. Sites hosted on siteleaf.net domains may still be experiencing DNS issues, but are coming back online. We'll continue to monitor this.</p><p><small>Dec 1, 20:20 UTC</small><br><strong>Update</strong> - Our DNS provider is currently working to mitigate the issue, details at http://dnsimplestatus.com</p><p><small>Dec 1, 19:55 UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Dec 1, 19:45 UTC</small><br><strong>Investigating</strong> - Currently experiencing an interruption due to an outage at our DNS provider (https://twitter.com/dnsimple/status/539499331670511616), this affects siteleaf.com as well as sites hosted with siteleaf.net domains.</p> Tue, 02 Dec 2014 06:32:37 +0000https://status.siteleaf.com/incidents/zxdnxm93qqj7
https://status.siteleaf.com/incidents/zxdnxm93qqj7Server reboot
<p><small>Sep 29, 03:19 UTC</small><br><strong>Resolved</strong> - Our service provider performed a server reboot as part of their infrastructure maintenance, causing a few minutes of downtime (https://status.rackspace.com)</p> Mon, 29 Sep 2014 03:19:04 +0000https://status.siteleaf.com/incidents/v1rqgyw4z51w
https://status.siteleaf.com/incidents/v1rqgyw4z51w