From a github support email: """ Hi Mozilla, The custom domain for your GitHub Pages site mozilla/FirefoxAcademicCenter needs attention. You must take immediate corrective action to ensure that your site remains available this week and continues to remain available after December 1st, 2014. Please follow the instructions for setting up a custom domain with GitHub Pages to update your custom domain’s DNS settings to point to the proper GitHub IP addresses. As a reminder, this week we will be conducting a “brownout” of all misconfigured GitHub Pages sites, meaning, we will intermittently serve a warning page, in place of your site’s content. We will update our status site before we do so, and normal functionality will resume at the conclusion of the brownout. For more context around why we’re making this change, and how to verify that you’ve updated your DNS records, please see the original GitHub Pages Legacy IP Deprecation announcement. Questions? We’re here to help. Happy Publishing! — The GitHub Pages Team """ https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/
I have nothing to do with that site, but I am CCing people who seem to.
I believe that things are set up correctly.  If you find that you're still getting brownouts for this, please REOPEN this bug. $ dig firefoxacademiccenter.org +nostats +nocomments +nocmd ; <<>> DiG 9.8.5-P1 <<>> firefoxacademiccenter.org +nostats +nocomments +nocmd ;; global options: +cmd ;firefoxacademiccenter.org. IN A firefoxacademiccenter.org. 3600 IN A 126.96.36.199 firefoxacademiccenter.org. 3600 IN A 188.8.131.52  Based on directions at https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.