What happened? I came back to the site, and TeX is no longer being rendered. Is anybody else having this problem? I didn't make any updates to my browser or other changes that might explain the problem at my end.


As of 14:20 UTC, MathJax.org is down, hence all MathJax requests fail.

Edit From Pierre-Yves' comment: there was an issue with DNS propagation (IP address for the server changed but the DNS didn't update fast enough). The hole is gradually healing itself. As of 16:15 UTC people have reported being about to connect to the mathjax.org domain (though it is still not connecting where I am physically).

  • 8
    $\begingroup$ Thanks. Good to know. May be I am old-fashioned, but I feel like saying something about reliance to third party SW. On second thought, I'd better not :-) $\endgroup$ Mar 13 '12 at 14:33
  • $\begingroup$ So we can't use mathJax except when a certain site other than this one is working? $\endgroup$ Mar 13 '12 at 15:31
  • $\begingroup$ Devs have added a means of altering the source for this now, to allow for some sort of fallback when the CDN fails. $\endgroup$
    – Shog9
    Mar 13 '12 at 15:53
  • 1
    $\begingroup$ @Michael: it is a bit more complicated then that. Most sites nowadays with high traffic volume uses a Content Delivery Network. This is supposed to improve redundancy, increase available bandwidth, and decrease latency (in other words, much better browsing experience for the user). MathJax uses Amazon CloudFront for this, and has generally functioned quite well. For something using a CDN to fall completely off the grid is quite unlikely. You usually need a very large number of servers to die... $\endgroup$ Mar 13 '12 at 16:00
  • 1
    $\begingroup$ ...at the same time for hardware problems to be the culprit. So it is not as simple as "certain other site" is not working. Try reading the MathJax documentation and have fun guessing what is causing this CDN problem. $\endgroup$ Mar 13 '12 at 16:06
  • 1
    $\begingroup$ Is the thing your calling "quite unlikely" the same thing that quite likely happened today? $\endgroup$ Mar 13 '12 at 16:12
  • 1
    $\begingroup$ @Michael: yes. In fact, as the discussion at the mailing list that Pierre-Yves linked to showed, the issue is not with the CDN, but with an DNS update. It is possible that best practices were not followed, but not knowing more details I can only speculate. $\endgroup$ Mar 13 '12 at 16:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .