4 ms·
It's not directly related to the event, but related to a recent code push. We're putting status here: http://status.disqus.com http://status.disqus.com
by danielha 16y ago
It's not directly related to the event, but related to a recent code push.
We're putting status here: http://status.disqus.com http://status.disqus.com
- vyrotek 16y ago"Our service is almost back to normal. Some sites may experience slow loading or errors with your comment count. This however does not affect the posting of comments. The following is our post mortem report. At around 9:30am PDT, Disqus identified a big increase in response times for traffic hitting non-VIP and API servers. The problem was tied to a significant increase in volume of requests to disqus.com, which overwhelmed our load balancer capacity. The immediate problem has been resolved by doubling load balancer capacity, and we are looking at options to improve capacity and availability of the API and the rest of the Disqus platform based on the lessons learned from today's issues. We sincerely apologize for the interruptions this morning, -Giannii" So it was related to a spike in traffic volume. :)
- danielha 16y agoIt was a bad configuration which, sure, probably wouldn't have been a big deal if we had 0 traffic. :)