incident.io Profile Banner
incident.io Profile
incident.io

@incident_io

Followers
3,140
Following
29
Media
364
Statuses
1,322

On-call, incident response and status pages all under one roof. So good, you'll break things on purpose 🔥 Loved by @netflix , @hashicorp , @linear + 1000s more

Run better incidents with ➡️
Joined December 2020
Don't wanna be here? Send us removal request.
Explore trending content on Musk Viewer
Pinned Tweet
@incident_io
incident.io
5 days
14 expert speakers, 9 awesome sessions, 1 week until it all. 🔥 SEV0 is just 7 days away—who are you most excited to hear from? 👀 We have just a few spaces left! RSVP here: #SEV0
Tweet media one
0
0
4
@incident_io
incident.io
1 year
We're ecstatic to introduce Status Pages. With an elegant, easy-to-use interface and integration into our product, businesses can regain confidence in their customer communications during incidents. Read our announcement post here:
5
34
382
@incident_io
incident.io
2 years
Today is an exciting day. We’ve raised $34M, and opened our US office 🔥🇺🇸 Thank you to our team, our investors, and most of all, our customers — we couldn’t do it without you ❤️ Read more:
Tweet media one
20
25
290
@incident_io
incident.io
2 years
You've built the spreadsheets, poured over the data: you know drawing conclusions from incident data is hard. That's why we've released a load of new dashboards to help you get real insight from your org. Let's take a look, using data from our real account 🔍
Tweet media one
6
14
165
@incident_io
incident.io
2 years
Have you heard of Digital Operational Resilience Act? If not, pay attention, as it’s likely it’ll be coming your way in the near future 👇
1
24
145
@incident_io
incident.io
3 years
it was DNS
6
16
156
@incident_io
incident.io
3 years
Pull Requests with personality 😉 Credit to @type__error
Tweet media one
2
9
109
@incident_io
incident.io
2 years
We couldn’t be more excited to share our Practical Guide to Incident Management! 🎉 Every company needs a plan for when things go wrong. Here it is – our years of collective knowledge & experience distilled into a practical guide. What's your favourite chapter? Comment below👇
7
17
81
@incident_io
incident.io
7 months
Today’s the day— On-call is finally here! 🎉 We’re on a mission to be the single place you turn when things go wrong. And now the wait is over. Feature-rich, rock-solid, and downright delightful to use. We can’t wait to hear what you think! 🔥
2
6
57
@incident_io
incident.io
2 years
There's a whole lot of lovely places to hang out at HQ. If you're in London and want to swing by, there's always a coffee on offer ☕
Tweet media one
Tweet media two
Tweet media three
5
3
50
@incident_io
incident.io
2 years
Rolling into the office on a Monday like…
Tweet media one
2
1
48
@incident_io
incident.io
3 years
We always knew we’d see our name in lights someday ⚡️
Tweet media one
0
0
44
@incident_io
incident.io
2 years
We've gotten a LOT of DM's about our merch lately!❤️ Here's the deal 🤝 we'll trade a T-shirt and a pair of socks for a Tweet of our merch 🔥 and we'll throw in some stickers if you promise to get a dog on the pic🐶 Just slide into the DMs with your request and we'll ship it 🚢
Tweet media one
7
10
44
@incident_io
incident.io
3 years
It's been a busy month. We've stepped away from the bustle of London to the Wye Valley to give ourselves the headspace to think, plan and build!
1
1
42
@incident_io
incident.io
3 years
this is fine. let us know if you want merch!
Tweet media one
9
0
38
@incident_io
incident.io
3 years
Thought it was time for a new team photo - all 10 of us ✨
Tweet media one
Tweet media two
0
1
37
@incident_io
incident.io
3 years
Happy Halloween from ! 👻
Tweet media one
1
2
37
@incident_io
incident.io
3 years
Running a hugely successful company like @monzo is no mean feat, and it's even harder when things go wrong 🔥 @t_blom shares insight into a gnarly incident from the early days, and how the company turned incredible incident handling into a superpower 💪
1
3
34
@incident_io
incident.io
3 years
Every company needs a strong brand identity, so we're thinking of names for our signature orange colour 🔥 We think our ideas are flawless, obviously. incident.iorange (Everything's On) Fire Orange Orange You Glad You Use Jason Orange Fruit Cause Analysis
15
0
34
@incident_io
incident.io
1 year
🥳 We're super excited to be a part of the Notion Projects ecosystem! If you're an user, you can easily export post-mortems to your Notion workspaces, with intuitive formatting to match ✨ Thank you @NotionHQ !
Tweet media one
@NotionHQ
Notion
1 year
The future of project management is connected. Your favorite apps love to work with Notion just as much as you do 🫱🏼‍🫲🏾 Meet our partners that supercharge Notion Projects:
Tweet media one
40
134
1K
1
5
33
@incident_io
incident.io
3 years
A good data stack is key for fast-paced companies. The last two weeks we've gone from zero to a production data stack we're really happy with, and already getting value from. Here's a write-up from @lawrjones on the what, why and how:
2
5
32
@incident_io
incident.io
4 years
Delighted to share that @evnsio is joining the team! The best way to respond to and learn from incidents just got a little better 🚀
Tweet media one
1
0
29
@incident_io
incident.io
2 years
❗Big day for us today❗We are live on @ProductHunt ! We’re really excited about what we’re building here, so it's great to reach this milestone moment after 18 months of hard work. Check out our page and let us know your feedback 🙏
1
15
28
@incident_io
incident.io
1 year
🔥Introducing Catalog—connecting everything that exists in your organization to level up your incident response. 🔥 With Catalog, you now have a clear map of services, customers, teams, and more in your organization. ✅
Tweet media one
1
9
29
@incident_io
incident.io
3 years
Private incidents coming soon 🤫🔒🔜
Tweet media one
0
0
27
@incident_io
incident.io
3 years
Very (very 😉) occasionally our software goes wrong and someone needs to step in to fix it. Out of hours that's the responsibility of our on-call rotation – something that everyone participates in by default. Interested in how we do it? Read on! 👇
0
2
28
@incident_io
incident.io
3 years
We've always put security at the forefront of everything we do. From today you no longer have to take our word for it, as we're now officially SOC 2 compliant🔒🎉
0
1
28
@incident_io
incident.io
4 years
😱 Seeing things go wrong in Slack, and want to create an incident off the back of it? 😌 Easy peasy. Quickly create incidents directly from messages using our shortcut, and we'll handle the rest.
0
2
26
@incident_io
incident.io
3 years
You asked, so we built it. We're really excited to announce the launch of a hotly anticipated new feature - Workflows! Automate your essential incident processes quickly and easily ⚡️
1
4
26
@incident_io
incident.io
2 years
Our API is live! You can now automatically: ✅ create incidents from monitoring and ticketing tools ✅ export incident data for analysis to data warehouses and BI tools ✅ configure custom fields (ie services affected) from external data sources See how it works👇
0
0
26
@incident_io
incident.io
3 years
We're in San Francisco this week at #SREcon 🙌 We'd love to avoid bringing these t-shirts back to London with us, so if you want one and to say hi, let us know!
Tweet media one
Tweet media two
1
1
25
@incident_io
incident.io
3 years
Introducing our newest engineering hire, Sophie Koonin ( @type__error )! She finally took a break from adding <marquee> and <blink> tags on our web UI long enough to say hello on our blog:
0
0
24
@incident_io
incident.io
1 year
And that's a wrap for @KubeCon_ ! A massive thank you to everyone who stopped by our booth. We're genuinely humbled by the outpouring of support and interest in what we're building. We had an absolute blast and can't wait to do it again. See you next year! ✌🏼
Tweet media one
1
0
23
@incident_io
incident.io
3 years
Exciting news! 🎉 We’re looking for engineers to come and help us build the best way for organisations to respond to incidents. Interested, but want to hear more? Read on…
2
7
23
@incident_io
incident.io
3 years
There's a lot of guidance for larger companies on how to manage incidents, but startups are left to figure it out for themselves. If you're small, short on time, and looking for a pragmatic and low effort way to get started, we've got you covered 👇
0
6
23
@incident_io
incident.io
4 years
Busy week last week! We shipped: - Exporting incident actions to JIRA after a postmortem, to make it way easier to follow-up - Billing: you can now pay us money! - Actions in your postmortem document - Resiliency improvements Dive in for more:
0
2
23
@incident_io
incident.io
2 years
We’ve just released our new Notion Integration to enhance your post-incident process 🎉 Here’s some highlights 🎥
1
2
22
@incident_io
incident.io
3 years
"You should build the systems that differentiate you from your competition, and buy the ones that don't." Engineer @type_error shows how we're using @LaunchDarkly to feature-flag our work in progress and make sure we're shipping quickly and safely.
1
5
23
@incident_io
incident.io
4 years
Incidents can be chaotic. When they are, it's hard to know who's doing what. 🤷‍♀️ We get it. Split up the work with actions, assign tasks to individuals, and request help from others. If you're interested, sign up for early access at 👀
0
5
23
@incident_io
incident.io
1 year
2
1
22
@incident_io
incident.io
2 years
don't even bother applying for an SRE position unless your incident activity looks like this 🔥
Tweet media one
@AlexRoseGames
Alex Rose
2 years
don't even bother applying for a senior dev position unless your github looks like this
57
982
5K
2
1
22
@incident_io
incident.io
3 years
Ever been asked to reduce the number of incidents you're having, or avoid them altogether? We've been there – so we thought we'd share some better approaches.
0
4
22
@incident_io
incident.io
2 years
Things go wrong — that's fine! Learn, iterate, improve. It’s true of incidents…and certainly of product demos👇 Ours took a few messed up tries, but we made it eventually. Check out the final version on our website 👉 ('See how it works' button)
2
1
21
@incident_io
incident.io
3 years
We've been featured by the @SlackHQ App Store! Thanks for featuring us as one of the must-have apps to install folks. Feels comfy being alongside our friends @loom as well! Check it out:
Tweet media one
0
3
21
@incident_io
incident.io
3 years
We recently spoke to @GergelyOrosz about the things that take place when the dust has settled on an incident. We've elaborated on a few of our points here, and linked to the full post from Gergely too 👇
2
2
21
@incident_io
incident.io
3 years
As a small start-up, we wanted a super simple observability setup. We found one that doesn't just help us debug production issues, but has become an essential tool for devs when working locally. See how we did it:
1
3
19
@incident_io
incident.io
3 years
Achievement unlocked! Completed our first team escape room, and we're all still on speaking terms.
Tweet media one
1
0
20
@incident_io
incident.io
7 months
Ever found yourself fighting your paging solution? With our new On-call product, we’re fixing that 🎉 We’ve put tons of focus into making the experience of being on call as delightful as possible. Here are a few highlights! 👇 Automatic incident creation ⚡️ No need to manually
Tweet media one
Tweet media two
Tweet media three
Tweet media four
1
1
20
@incident_io
incident.io
1 year
And the (self proclaimed) award for most beautiful booth goes to… Come say hi if you’re at @KubeCon_ !
Tweet media one
1
0
20
@incident_io
incident.io
4 years
Ever joined an incident, and found yourself scrolling back through pages of Slack messages, trying to figure out what's going on? 🤔 We have. That's why we'll send you a short update of everything you need to know, as soon as you join an incident. Get up to speed, at speed. 🚀
1
4
20
@incident_io
incident.io
1 year
📢 Big milestone alert: Over 5️⃣0️⃣ customers now use our public status pages to manage exception comms with their customers 🔥 And it looks like team light mode are winning 👀
Tweet media one
2
3
19
@incident_io
incident.io
2 years
Team incident is growing fast 🚀 we couldn't be more excited to say hello to our 5 newest joiners 👋👇
1
2
19
@incident_io
incident.io
2 years
Our team is growing 🎉 We're super excited to welcome onboard team , our newest product engineer, Martha!
Tweet media one
1
0
18
@incident_io
incident.io
3 years
We're extremely excited to be working with @umanagineer , @anuraggoel and co at @render ! For the simplest way to start building something customers love, head on over and sign up.
Tweet media one
0
0
19
@incident_io
incident.io
2 years
If you’ve ever built something and later realised that it really should have just been bought, then you’re not alone 🛍 Here's a story about the time we built an in-house expense software👇
2
2
19
@incident_io
incident.io
2 years
What should you be paid for being on call? 🤔 We want to know what you think! Fill in our survey 👇🏼 PS, we’ll give responders early access to the results + gift the most liked RT (by 24/05) a pair of AirPods and swag.
1
12
19
@incident_io
incident.io
3 years
This week we launched Decision Flows: encode complex decisions when it's calm, follow them simply when everything's on 🔥
0
2
18
@incident_io
incident.io
8 months
🎧 Love The Debrief? Here’s your chance to win a pair of AirPods Max! What better way to tune into the podcast than with a brand-new pair of headphones? Here's how to enter...
Tweet media one
2
10
14
@incident_io
incident.io
3 years
Today we launch Announcement Rules, allowing you to subscribe Slack channels to announcement posts for incidents that match some conditions: - is severity > Major - incident type Data Breach? This ones been a while coming- let us know how you find it!
0
0
18
@incident_io
incident.io
2 years
🎵 It's beginning to look a lot like Christmas🎵
Tweet media one
0
0
17
@incident_io
incident.io
3 years
Being a hero feels really good for a while, but over time, it loses its shine 🦸‍♂️ Many of us will have experienced working with a so-called "hero-engineer", and this week @isaacseymour shares his personal experiences, thoughts and advice on the topic.
2
3
16
@incident_io
incident.io
3 years
For a load of reasons – developer happiness, productivity, agility – we keep our CI pipelines fast. @lawrjones shares how we reached <5m from merging your change to it hitting production, going into the gory details of CircleCI Docker layer caching.
1
4
17
@incident_io
incident.io
2 years
We are very excited to declare that we have some [cute] company in the office today 🐶
Tweet media one
0
0
16
@incident_io
incident.io
3 years
We're really excited to have @isaacseymour join us as a Product Engineer. Welcome, Isaac!
1
0
17
@incident_io
incident.io
7 months
Tomorrow is the day…👀🚀
Tweet media one
1
2
17
@incident_io
incident.io
3 years
We've released Custom Fields. You can now define your own custom data that you want to collect on an incident, so you can track data specific to your company. This was one of our most requested features — can't wait to see what you build with it!
1
3
17
@incident_io
incident.io
4 years
@linear is a phenomenal tool for shipping product (we're big fans). This morning, we released our integration with them, so now you can use it to follow up on your incident actions, too 🛠🚀
0
2
16
@incident_io
incident.io
3 years
All on-call compensation models come with their pros and cons. So what's the fairest of them all? Looking at the 4 most common ones: • No $ for on-call🚫 • $ as part of base salary💰 • $ per incident🔥 • $ by time⏰ + Our advice on getting started 👇
1
0
15
@incident_io
incident.io
2 years
Only an hour left until we launch something really cool to make dealing with incidents a lot easier. Watch this space 👀
Tweet media one
0
2
15
@incident_io
incident.io
3 years
Okta are investigating reports of a data breach ⚠️ We really hope it's not as bad as it looks, but if you're a user of Okta, now would be a good time to prepare your response with a private incident 🔒
1
0
16
@incident_io
incident.io
2 years
🧮 We’re making our on-call calculator free today 🧮 Collectively, we’ve been on-call for thousands of hours, and have seen first hand how calculating who is owed what at the end of the month often requires manual calculations and ends up with people being paid incorrectly 😩
1
3
16
@incident_io
incident.io
2 years
We've just released Incident Types! Customise @incident_io for your whole org. You can now: 🛠 Define custom fields and workflows uniquely by type 📉View analytics by type to gain further insight 🔐 Use types to enforce private incidents More here 👇
0
3
14
@incident_io
incident.io
2 years
Last Friday of the month means company-wide day off. And what better way to celebrate than with puzzles, board games and MarioKart? 🙌🕹️🧩
Tweet media one
Tweet media two
1
0
15
@incident_io
incident.io
3 years
Ever join an incident, and find yourself scrolling endlessly to find the link to the Zoom? Incidents are a team sport, and being on your own is no fun. With , just /zoom, and we'll make it easy for others to see where you're hanging out.
0
1
15
@incident_io
incident.io
3 years
Good copy can be the difference between a decent product and a great one. Engineer @type__error explains how copywriting is a central part of product development - and at startups, it's often an engineer's job 📝
0
3
14
@incident_io
incident.io
2 years
🤔 What would you like us to write about? 📝Today is content day at @incident_io - when we all down tools and focus on writing blog posts. Here's a post @sjwhitworth wrote about the value of content day earlier this year:
1
0
15
@incident_io
incident.io
2 years
Our on-call survey results are (almost) in! Based on 200+ responses, we’ve found the average weekly compensation for on-call is $540 💰 Watch this space for the full report findings, or...
1
1
15
@incident_io
incident.io
2 years
We really tried our best to hold back from jumping on the ChatGPT train, but the cast of Friends were so passionate about , it felt almost rude not to share this.
Tweet media one
0
2
14
@incident_io
incident.io
2 years
Happy Halloweencident! 🎃👻
Tweet media one
0
1
15
@incident_io
incident.io
10 months
You know how you always forget to provide a summary mid-incident? Yeah, us too. And now, we've got you covered with auto-summary. You manage your incident, we've got the rest✨
0
3
14
@incident_io
incident.io
3 years
Engineering interviews can be stressful, and not knowing what’s coming makes things worse. That’s why we’re sharing our entire process, including why we do each stage, who you'll speak to, and in some cases the exact questions we’ll be asking.
0
1
13
@incident_io
incident.io
3 years
No matter where you are in the world, things will go wrong. We're already helping folks around the globe to better handle and learn from their incidents! 🌎🔥
Tweet media one
0
0
14
@incident_io
incident.io
2 years
🚨 We have some extra swag we're trying to get off our hands so here's what we'll do: reply in this thread with your best product feature idea and, if we think it's worth adding to our roadmap, we'll send you a shirt!
22
1
13
@incident_io
incident.io
4 years
It's been a few days, about time for another integration! @sjwhitworth has been beavering away and excited to say you can now sync actions from incident debriefs into @github issues 🎉 This is fun, who should we integrate with next...? 😀
1
1
13
@incident_io
incident.io
3 years
This week we've shipped @Zoom support, for auto-creating meetings whenever an incident is declared. Creating a video chat at the start of an incident is always best practice, but especially so when you have remote responders (and who doesn't, nowadays!)
1
2
13
@incident_io
incident.io
1 year
During KubeCon, we responded to one of the most consequential incidents we've had to date. After completing a post-mortem, we're finally ready to discuss what happened and how we fixed it. Here's the story about how we...ran out of shirts at KubeCon.
1
0
13
@incident_io
incident.io
1 year
✨ Workflows is one of our most popular product features, and we’re excited to announce that we’ve given it a well-deserved glow-up. Read more to see what’s changed ⏩
Tweet media one
1
3
11
@incident_io
incident.io
3 years
When you're in the midst of an incident, it can be hard to remember to communicate regularly. With /incident update, we make it easy!
0
1
12
@incident_io
incident.io
3 years
Gone are the days when incidents only occurred in technology, with limited understanding for others. Incidents are for everyone, not just for engineers. And we're building organisation-wide incident management to solve it. Why? Read on 👇🏼
1
1
12
@incident_io
incident.io
3 years
Supercharge your Workflows with variables! ⚡️ Automatically post Slack messages as part of Workflows featuring dynamic variables such as incident name, severity, the value of a custom field, and many more 🪄
0
0
12
@incident_io
incident.io
9 months
Happy holidays from the team ❤️
Tweet media one
0
1
12
@incident_io
incident.io
2 years
We're super excited to welcome Dani to team incident as Head of Talent! 👪 On top of being a top tier talent strategist, she also knows the bests spots in town for coffee☕️
Tweet media one
0
0
12
@incident_io
incident.io
2 months
Fast, effortless to use and beautifully designed. @linear is a phenomenal product for modern software development ✨ This week on The Debrief, we talk to @sabin_roman , engineering manager at Linear about how they build… Linear!
1
2
15
@incident_io
incident.io
2 years
We've been working on something really fun (and importantly, super useful!) behind the scenes 🔥 we can't wait to share it! Coming soon... 👀🙌
Tweet media one
3
0
12
@incident_io
incident.io
1 year
Happy weekend incident responders! Hope the pagers remain quiet 🫶
Tweet media one
0
3
12
@incident_io
incident.io
2 years
Mixing it up with the big kids at @KubeCon_ 😎
Tweet media one
1
1
12
@incident_io
incident.io
2 years
Tweet media one
1
1
11
@incident_io
incident.io
2 years
📊 Curious about how to set up a modern data stack? We've updated ours using a combination of @metabase , @fivetran , @dbt_labs , @segment , and @CircleCI . Summary 👇
1
1
12
@incident_io
incident.io
3 years
Another new joiner post: say hello to @lawrjones , joining us with a load of SRE and product-building experience Feels like we're really gaining momentum now, with a full-time team helping build-out our upcoming roadmap. Stay tuned for more!
1
1
11