>>/162270/


This is what I mean by, we have a ton of work to do still. This is an easy fix but all that was done was the servers were rebooted earlier. Let me make it clear: if the src property of an image is bad, the image server won't know until it tries the url and when it does it tells the 8kun server that that image didn't load so the 8 kun server tries another ad and image with a bad url and the image server does the same thing. It cycles between two bad requests, and that eats up all system's resources, bandwidth, and being that it is single threaded, the interrupts and both cannot break out of the bad cycle. I analyzed the URLS earlier and they were each looking for a graphic with a URL like this:

https://softserve.softserve.softserve.100timesmore. 
Which is an invalid address for a resource. It should be something like this:
https://softserve/some32randomcharactersendingin.jpg