>>162246 Part 2

Yes, I am 100% correct and here is why. I am posting this from another browser tab and when I go to inspect for failed images, I get none, zero; and the bottom image ad is loaded of a frog on a unicorn with an image name of 11b83ef4c4ff4a50a0d37f041693bd0c.jpeg. So, something is happening in the code that loads those ads at the bottom with:

https://softserve.softserve.softserve.softserve.softserve.softserve.softserve.softserve.softserve.softserve.softserve….

Which causes a response of

This site can’t be reached to 8Kun and 8Kun then tries to cycle with another ad image, which is also bad, then goes into an endless loop of two bad image ads, eating up the image server resources, which eventually locks up the 8kun server waiting for a proper response of a resource, and then NGINX sees all this busyness and reports back that the service is unavailable with a 503. That add server at the bottom for some reason is generating a bad source for the image as https://softserve.softserve….

This should end all these outages when fixed, because they are not outside denial of services but a bad URL in the source of the images being loaded into the ad server.

Any questions?