Service Interruption (Resolved)

Jul 7 2020, 08:04 PM

At 5:51pm CST we became aware of a service disruption related to the network.

This investigation is ongoing at this time, we're in contact with the datacenter to find the root cause of the network problem.

We will continue to provide updates, and apologize for the inconvenience. Measures have been taken to reroute traffic at this time, but they are temporary and you may experience degraded performance. They will also not be immediately effective for everyone at this time.

As of 9:39pm CST service is mainly operating on emergency procedures normally.

note: if you have a domain name and you have an 'A' record instead of a cname, please change the IP temporarily to -- or access the board via the url.

Latest updates are provided at the end of this topic


  1. John Says:

    Please note this also affects email service, -- PM notifications of emails will not go out.

    The datacenter is working to get things back online as soon as they can.

  2. John Says:

    Update: a temporary solution for email has been implemented, though it is not perfect.

    Important information regarding domains as well above.

  3. John Says:

    Service is mainly restored at this point to and subdomains, the backup measures to reroute traffic are in effect. We will likely announce a maintenance window for the primary network system once we know more.

    Update: We're told that a major switch had a power failure and they are working on replacing it. This will not affect any of you while we are under the backup routing measures and the transition back should be seamless.

  4. John Says:

    Update: we are rolling back to our normal system as the datacenter confirmed that the network switch has been replaced. A maintenance window wasn't needed to restore service for the time being -- we'll be monitoring it closely as well over the day, as they want to keep an eye on it after this. Work continues to be done by the crew as well.

  5. John Says:

    Normal operation has resumed since yesterday and there are no service interruptions related to this incident expected at this time, so this is being marked as resolved.

    Additionally, our uptime status page has been fixed by uptimerobot, is working.