Just now when trying to upload an image with the image uploader I'm greeted intermittently with the following error:

Failed to upload image; imgur is rejecting the request

That error comes from the POST on https://meta.stackexchange.com/upload/image?https=true

I initially was on an non-encrypted HTTP connection. Switching to HTTPS seemed to resolve the issue.

In this same time-frame I also notice that images that are hosted on i.stack.imgur.com are not served or only after refreshing a couple of times.

I have verified in chat that it is not only me and I rule out caching.

Can this be looked at and if possible fixed?

  • I assume imgur DNS has issues, I think that's how Gravatar started to fall apart. Really hope they won't ignore it like Gravatar do. Feb 27, 2017 at 20:24
  • i.stack.imgur.com/mah7s.png Just took 4 reloads to access.
    – Tim
    Feb 27, 2017 at 23:04
  • 1
    Now I get “Imgur is over capacity”.
    – egreg
    Feb 28, 2017 at 17:48
  • +1 I've had the same issue for the last 24 hours. Feb 28, 2017 at 17:52
  • Same problem here.... Feb 28, 2017 at 18:01
  • The image wasn't showing up when I tried to upload stuff, but it uploaded - if I went to the URL it gave me, I could see it.
    – Mithical
    Feb 28, 2017 at 18:03
  • Same is happening for me when I try to upload a 1.7Mb gif on bio.SE Feb 28, 2017 at 18:43
  • I'm having the same problem Feb 28, 2017 at 20:21
  • It happens even with very small (~ 10 KB) images
    – vsz
    Feb 28, 2017 at 21:01
  • If the servers at Amazon S3 don't accept the network-packets the size doesn't really matter.
    – rene
    Feb 28, 2017 at 21:15

1 Answer 1


It appears that S3 has fallen over in AWS for the US-EAST1. Ironically I can't include a screenshot of the dashboard in this post, but I promise I have one.

You can see the AWS status dashboard here: https://status.aws.amazon.com/

Imgur uploads should return successfully once that issue has settled. Apologies for the trouble, but we're not in a position to do much about it for the moment. We're working on some long-term backup bits but they're far from being in place.

We're also fighting a botnet (no idea if this is related, it's unlikely), so busy on a few fronts at the moment.

  • 6
    Maybe the webcam botnet also DDoSing imgur by uploading millions of images per second? Feb 28, 2017 at 18:38
  • 9
    "fighting a botnet" ... I just imagined all the Team avatars in knight's armor awaiting an oncoming horde of robotic insects. (I'm thinking giant ants because they are a pain to get rid of.) This image is so much more epic than the reality of fighting a botnet, so I will continue to assume it is done this way to make you all more epic.
    – Kendra
    Feb 28, 2017 at 20:08
  • 1
    Shucks, hang in there fellas. Rooting for you.
    – jxramos
    Feb 28, 2017 at 21:22
  • 4
    @Kendra Funny, Stargate's Replicators came to mind when I read that.
    – Mr.Wizard
    Feb 28, 2017 at 21:39
  • 3
    accepting this answer now, as the S3 issues have been resolved. Thanks Nick for your hard work and dedication.
    – rene
    Feb 28, 2017 at 23:11
  • 2
    Though the issue has been resolved, I might add the official imgur's tweet regarding this issue, and its support page for reference. Mar 1, 2017 at 6:40
  • 1
    @qwer it's not resolved, I still get broken images ~80% of the times and have to reload a lot to see images. Mar 1, 2017 at 7:36
  • 2
    @Kendra "To dream... the impossible dream..."
    – TylerH
    Mar 1, 2017 at 14:39
  • Hmm. Yeah, something's still jacked up. I'll ping folks internally (or hey, here. HI NICK) to see if we can reach out to our contacts at Imgur and figure out what's what.
    – Adam Lear StaffMod
    Mar 2, 2017 at 6:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .