I also get the same error.
All I can say is that your site is probably affected by the current issue: