Hacker Newsnew | past | comments | ask | show | jobs | submit | gslin's commentslogin

Quote from the first paragraph:

> Today, we’re announcing Amazon Route 53 Accelerated recovery for managing public DNS records, a new Domain Name Service (DNS) business continuity feature that is designed to provide a 60-minute recovery time objective (RTO) during service disruptions in the US East (N. Virginia) AWS Region. This enhancement ensures that customers can continue making DNS changes and provisioning infrastructure even during regional outages, providing greater predictability and resilience for mission-critical applications.



I believe a report with timezone not using UTC is a crime.


An epoch fail?


I think it makes sense in this instance. Because this occurred in us-east-1, the vast majority of affected customers are US based. For most people, it's easier to do the timezone conversion from PT than UTC.


But us-east-1 is in Eastern Time, so if you aren't going to use UTC, why not use that?

I'm guessing PT was chosen because the people writing this report are in PT (where Amazon headquarters is).


us-east-1 is an exceptional Amazon region; it hosts many global services as well as services which are not yet available in other regions. Most AWS customers worldwide probably have an indirect dependency on us-east-1.


My guess is that PT was chosen to highlight the fact that this happened in the middle of the night for most of the responding ops folks.

(I don't know anything here, just spitballing why that choice would be made)


Their headquarters is in Seattle (Pacific Time.) But yeah, I hate time zones.


The password `TPL075526460603` is also mentioned in CVE-2022-37255[1].

[1]: https://nvd.nist.gov/vuln/detail/CVE-2022-37255




For English translation about incidents, Google Translate for entire website might be helpful: https://smc-peering-tw.translate.goog/?_x_tr_sl=auto&_x_tr_t...





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: