Well folks, sorry about the brief downtime today there on this here community site!
At around 2pm CST, @Teke , @zachary , @Dave and I all simultaneously turned around and said, “Is the community site being a slow for you?”. To which the answer was, “Yes, we should fix this ASAP”, unfortunately “ASAP” meant a bit of downtime. It also means that the community site should be able to keep up with you now: double the CPU, quadruple the RAM, double the network speed, and configured to be upgradable in the future with less interruption.
When we turned the box off so we could change the EC2 instance size, we did not realize that DNS was pointing at a non-elastic IP address, and thus when we brought the box back up, it had a new IP address yet DNS was pointing at the old IP. While I added an elastic IP and repointed our DNS records, @zachary wrote up this status.spark.io update. Unfortunately the time to live (TTL) on the DNS records was one hour, so for some people, the site was not available for an hour.