https://github.com/posthog/post-mortems

When something goes wrong, we talk about it here. Unless it's confidential.
https://github.com/posthog/post-mortems

Last synced: 5 months ago
JSON representation

When something goes wrong, we talk about it here. Unless it's confidential.

• Host: GitHub
• URL: https://github.com/posthog/post-mortems
• Owner: PostHog
• License: mit
• Created: 2024-03-01T09:45:02.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2026-01-20T19:28:20.000Z (5 months ago)
• Last Synced: 2026-01-21T04:39:26.504Z (5 months ago)
• Size: 71.3 KB
• Stars: 3
• Watchers: 9
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# PostHog Post-mortems (Public)

When something goes wrong, we talk about it here and come up with a plan. Unless it's confidential or involves explicitly talking about customer data - in which case it should go in [our internal repo](https://github.com/PostHog/incidents-analysis).

Post-mortems usually happen after an incident or outage. It's the responsibility of the incident lead to make sure a post-mortem happens. If we don't have an incident lead, it's the responsibility of whoever opened the incident. 

You can stay updated about incidents via [our status page](https://status.posthog.com/).

Curious about how we handle incidents? [Check the handbook](https://posthog.com/handbook/engineering/incidents).