Answers.Body: <blockquote>
    <p>The hosting company says the only error they see is "image missing" and the DB connection is fine.</p>
  </blockquote>
  
  <p>That seems suspicious to me.  Assuming the 503 Service Unavailable status code is initiated in Craft, it will do that in two common occurrences for front-end requests.  One is when Craft is in the middle of being updated, and the other is when it is having problems connecting to the database.</p>
  
  <p>A look through the Craft logs as well as your web server access logs should help verify this.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-10T14:29:10.620Z
Answers.Text: Thanks for this. The 503 is not served up by Craft. All you see is a broken image on the front end and the service unavailable for that image in Chrome dev tools. I'm guessing that this is just the server dropping the ball and taking too long to respond with the image. But I'm not sure.
Answers.UserDisplayName: Wonko
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-04-04T14:51:44.313Z
Answers.Text: Mystery finally solved. An SEO company was running some tests against the site that day and basically hammered the server too hard. Why they were testing against a live site is beyond me.
Answers.UserDisplayName: Wonko
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-07T03:04:12.163Z
Answers.LastActivityDate: 2018-03-07T03:04:12.163Z
Answers.UserDisplayName: Brad Bell
Body: <p>Folks:</p>
  
  <p>When users visit the site only some of the images on the page show. Checking Chrome dev tools shows that the missing images are failing with "server unavailable" errors. The image is there if you go to it directly.</p>
  
  <p>This appears to be random. Images show sometimes but not others. I have erased the cache, rebuilt the search index and the asset list. No change.</p>
  
  <p>The client says that the site sometime fails completely but I have yet to witness this.</p>
  
  <p>I have VPNed from various locations and it seems to be the same no matter where I'm coming from.</p>
  
  <p>The hosting company says the only error they see is "image missing" and the DB connection is fine.</p>
  
  <p>Any help would be great.</p>
  
Tags: <image>
Title: Images missing, service unavailable
ThreadText: # Images missing, service unavailable
  
  (Asked by: username_0 on 2018-03-07)
  
  Folks:
  
  When users visit the site only some of the images on the page show. Checking Chrome dev tools shows that the missing images are failing with "server unavailable" errors. The image is there if you go to it directly.
  
  This appears to be random. Images show sometimes but not others. I have erased the cache, rebuilt the search index and the asset list. No change.
  
  The client says that the site sometime fails completely but I have yet to witness this.
  
  I have VPNed from various locations and it seems to be the same no matter where I'm coming from.
  
  The hosting company says the only error they see is "image missing" and the DB connection is fine.
  
  Any help would be great.
  
  **Tags:** image
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-03-07. Score: 1
  
  > The hosting company says the only error they see is "image missing" and the DB connection is fine.
  
  That seems suspicious to me. Assuming the 503 Service Unavailable status code is initiated in Craft, it will do that in two common occurrences for front-end requests. One is when Craft is in the middle of being updated, and the other is when it is having problems connecting to the database.
  
  A look through the Craft logs as well as your web server access logs should help verify this.
  
  > **Comments:**
  > **username_0**: Thanks for this. The 503 is not served up by Craft. All you see is a broken image on the front end and the service unavailable for that image in Chrome dev tools. I'm guessing that this is just the server dropping the ball and taking too long to respond with the image. But I'm not sure.  
  > **username_0**: Mystery finally solved. An SEO company was running some tests against the site that day and basically hammered the server too hard. Why they were testing against a live site is beyond me.  
  
  ---
  
  