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.
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.
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.