67 ms·
Likely because Route53 doesn’t have any degraded service at the moment. Would be more apt for a yellow status next to S3, given context in threads above.
by bowmessage 7y ago
Likely because Route53 doesn’t have any degraded service at the moment. Would be more apt for a yellow status next to S3, given context in threads above.
- deleted 7y ago[deleted]
- banana_giraffe 7y agoIt's not just S3. I'm seeing failures of DNS resolution of well known, and very much still working, non-AWS sites from within AWS now. It's really hit or miss, though. Most of the big stuff works.