In case you or your team had trouble using Zingtree today, the cause was due to our caching provider (Cloudflare). We use Cloudflare to ensure better performance and reliability on zingtree.com (as do a lot of other popular sites), but in this case it made things worse.
Here’s Cloudflare’s summary of the problem:
Identified – Starting at 00:00 UTC on January 1, 2017, CNAME resolutions on some machines stopped working due to a bug triggered by the universal addition of one leap second, which affected both some authoritative DNS and origin DNS lookups, causing 5xx errors. Authoritative DNS was less affected since resolvers were served SERVFAIL and possibly retried until they hit a healthy instance. We deployed a fix at 01:30 UTC and it is rolling out to most affected sites. We will update this once the deployment is finished.