I would have them first reboot the image server then the web server. As I watched the debugger before, I saw that index or a current page starts to load three images try loading then it just fails. So it is not DNS, but I am sure we will be told that. Listen, most of the code here were imports from other libraries, for example the ad at the bottom is different from the top ads because most of the time, when the bottom one does not load, it tries another one but that fails to because somehow the software is getting into a state where code is being generated to ask for and ad source for the image from https//:softserve.softserve.10ktimes which is an invalid url. All you need is one person with an open tab, bothering the image server for that ad, and the whole system tanks because it ties up the web serve doing a ping pong affect, eating systems resources, until both crash along with everyone else. I have told them this about 100 times. Most devs do not touch external libraries that are imported into the code base and may not even have access to it if it is munged properly or n a binary file. You can tell it is the image server when images break, load slowly, or open in a new tab. Please tell Jim to Reboot image and web server please.