News for hackers. Stuff that matters.
Re:AWS S3 Outage by nmjohn on Monday August 10, 2015 @03:42AM (#10033187)
I'm seeing it as well - majority of connections are being dropped for us atm

  The Amazon S3 team recently completed some maintenance   
  changes to Amazon S3’s DNS configuration for the US STANDARD region on 
  July 30th, 2015.
    
  You are receiving this email because we noticed that your bucket
  is still receiving requests on the IP addresses which were removed 
  from DNS rotation. These IP addresses will be disabled on August 
  10th at  11:00 am PDT, at which time any requests still using
  those addresses will receive an HTTP 503 response status code.
  
  Applications should use the published Amazon S3 DNS names for 
  US STANDARD: either s3.amazonaws.com or s3-external-2.amazonaws.com
  with their associated time to live (TTL) values. Please refer to 
  our documentation at: 
  http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 
  for more information on Amazon S3 DNS names.
Something to do with that perhaps? AWS sent us that last thursday
Re:AWS S3 Outage by bbrazil on Monday August 10, 2015 @04:59AM (#10033428)
Java by default can cache DNS forever, which may be why many people are seeing problems. Set networkaddress.cache.ttl to adjust this.

http://javaeesupportpatterns.blogspot.ie/2011/03/java-dns-ca... has more detail.

Re:AWS S3 Outage by ork on Monday August 10, 2015 @05:58AM (#10033608)
Reading this article, it seems that starting at 1.6 the default TTL became 30s.
Re:AWS S3 Outage by Xorlev on Monday August 10, 2015 @06:58AM (#10033773)
It's not true as far as I can tell. You need this flag set or it keeps DNS entries forever, at least on the JVM we run (Oracle, 1.8u51).
Re:AWS S3 Outage by cperciva on Monday August 10, 2015 @03:47AM (#10033210)
If it is related, someone screwed up badly. I didn't receive such an email; and I'm seeing the same error rate with IPs I resolved 5 minutes ago.