Honest Status Page

@honest_update

These are the things we probably ought to say when updating incident status. Snark and compassion. Now, about your data… by and friends.

The Incident Review Meeting
Joined February 2015

Tweets

You blocked @honest_update

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @honest_update

  1. Jan 7

    We regret that we did not listen to the AWS engineer that begged us to THROW OUT THIS INSTANCE TYPE.

    Undo
  2. Dec 31

    ┏━━┓┏━━┓┏━━┓┏━━┓ ┗━┓┃┃┏┓┃┗━┓┃┃┏┓┃ ┏━┛┃┃┃┃┃┏━┛┃┃┃┃┃ disks still fill up ┃┏━┛┃┃┃┃┃┏━┛┃┃┃┃ ┃┗━┓┃┗┛┃┃┗━┓┃┗┛┃ ┗━━┛┗━━┛┗━━┛┗━━┛

    Undo
  3. Oops. This is gonna take longer than expected because we forgot to move our 2FA to our new phones.

    Undo
  4. Sorry for the long duration of that service interruption. Everyone knew how to fix it, but not how to fix it in kubernetes.

    Undo
  5. The root cause is you not clicking our damned ads.

    Undo
  6. Ughhh what are we supposed to do if we can’t browse while waiting for tests to run? (Hugs to !)

    Undo
  7. It's only an incident if it's from the paying region of the customer list. Otherwise it's a sparkling bugfix.

    Undo
  8. Undo
  9. Wait, adopting DevOps wasn’t enough Chaos?

    Undo
  10. Good news! Our deployment tooling now tells you who is on call before you start your deploy…

    Undo
  11. Your data is important to us but… speaking of black holes: We’re sorry that all work you did since midnight is lost. Please redo your work.

    Undo
  12. We learned today that moving files out of Terraform doesn’t cause it to ignore the assets.

    Undo
  13. Retweeted
    9 Apr 2019

    The CASE Method: A framework for improving monitoring ergonomics, mental models, and attention.

    Show this thread
    Undo
  14. I’ve been hiring for over twenty years and I still swear by this one simple rule: it’s the MTU

    Undo
  15. Friendly reminder to check in with your teammates if they’ve had a bad on call stint. Maybe you can help! (Extra ❤️ for managers helping with this!)

    Undo
  16. Turns out everyone was afraid to touch that bit of infra for a damned good reason.

    Undo
  17. [soundcloud postmortem] engineer: wow this blew up here’s my soundclo… right

    Undo
  18. The incident wasn’t that bad, we just had a reorg to deal with right in the middle. Lesson learned.

    Undo
  19. Thankfully we overheard the solution to this problem in a coffee shop during our 1:1 walk.

    Undo
  20. We’re going to just leave it like this for a minute and take a nap.

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·