3

There is a news announcement banner at the top of Stack Overflow, but clicking this link (https://insights.stackoverflow.com/survey/2018/) displays:

Error.

An error occurred while processing your request.

Developer tools reports a 500 error:

Failed to load resource: the server responded with a status of 500 ()
insights.stackoverflow.com/
  • 1
    It's not broken for me. What browser are you using? – Margarine Mar 14 '18 at 21:51
  • Chrome on Windows 7 – Exit Mar 14 '18 at 21:53
  • That link works fine for me on IE11. – PolyGeo Mar 14 '18 at 21:56
  • I'm actually getting an error now using Android Dolphin. It worked fine this morning though. – Carcigenicate Mar 14 '18 at 22:00
  • I'm getting the same error with Chrome on Mac. – Laurel Mar 14 '18 at 22:01
  • I checked with Chrome on Windows 10, Chrome on Android, and it worked. – Exit Mar 14 '18 at 22:03
  • Alright, if others are confirming the error, how about not downvoting my question? – Exit Mar 14 '18 at 22:04
  • 1
    This should have been posted on Stack Overflow :P – Laurel Mar 14 '18 at 22:04
  • I thought meta was for posting about issues with the stackoverflow family of sites? – Exit Mar 14 '18 at 22:07
  • 2
    There is meta.SE for all meta sites and meta.SO specific to StackOverflow. Duplicate question from there: meta.stackoverflow.com/questions/364629/… – BDL Mar 14 '18 at 22:17
  • Sigh, it's all quite confusing, all these domains and subdomains. I have a hard time discerning what the purpose is of some of these sites, and I'm not alone, judging from the number of times questions get pushed to other sites. – Exit Mar 14 '18 at 22:24
  • @Exit despite popular believe you can post bugs on any meta. Only when it comes to site specific policies, moderation, behavior etc the site specific meta is the preferred place to post. So for this specific post you shouldn't be pushed around at all. Sorry for that. – rene Mar 15 '18 at 8:29
  • This is server side error, browser isn't relevant. There was a short, temporary, glitch, on that domain, it happens. We should not report one time errors, only when it last for long time (e.g. 15 minutes) without any other notice. – Shadow Wizard Mar 15 '18 at 11:08
  • I disagree, I believe it was constructive to point it out, especially after it was discovered that the problem was not limited to me. As for it being a server side error, that does't mean it is not browser related - you only need to add a condition to check for user agent and if the code within that condition is messed up, like trying to call a non-existent function, then it would create such an error for specific browsers. The other post that @BDL mentioned illustrated that specifc browsers indeed were being affected. – Exit Mar 16 '18 at 2:29
  • it works for me too i am using chrome 64 bit – Muhammad Omer Aslam Mar 18 '18 at 13:20

You must log in to answer this question.

Browse other questions tagged .