Skip to content

Instantly share code, notes, and snippets.

@amane-katagiri

amane-katagiri/message.txt

Created July 19, 2022 01:15
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save amane-katagiri/a0d0c73cefe87ea71e4b327910be172b to your computer and use it in GitHub Desktop.
Save amane-katagiri/a0d0c73cefe87ea71e4b327910be172b to your computer and use it in GitHub Desktop.
Download ZIP
Last weekend’s Revue outage
Raw
message.txt
Between 1:30pm ET on Friday, June 8, and around 6:15pm ET on Saturday, June 9, the Revue website was inaccessible.
We are sorry for the inconvenience this caused, and would like to explain what happened.
First off, some things to know:
Scheduled newsletter issues that were sent during the outage will have impacted delivery, but this incident will not affect future delivery
Analytics and aggregated data regarding your newsletters continued normally
The problem was caused by a Domain Name System (“DNS”) issue, which affected Revue between the hours stated above. The team worked hard to resolve the issue as swiftly as possible.
Once the issue was resolved, Revue came back online for a lot of people — but DNS changes can take up to 24 hours to propagate globally, which led to some people experiencing the outage for longer than others.
We sincerely apologize and we have taken the feedback you have shared into account. Our @TwitterWrite team will ensure that transparent, clear communication continues to be prioritized in future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment