# Localytics' Process for Responding to Service Incidents

DevFeed: [Localytics' Process for Responding to Service Incidents](<https://devfeed.tech/articles/when-things-go-wrong-28636.md>)

Original publisher: [Read original article](<https://eng.localytics.com/when-things-go-wrong/>)

Author: Tony Wieczorek

Published: 2016-09-13T18:24:39Z

Content type: article

Language: en

Sources: [Localytics](<https://devfeed.tech/sources/localytics.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [realtime](<https://devfeed.tech/topics/realtime.md>)

Tags: [downtime](<https://devfeed.tech/tags/downtime.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [incident](<https://devfeed.tech/tags/incident.md>), [pagerduty](<https://devfeed.tech/tags/pagerduty.md>), [postmortem](<https://devfeed.tech/tags/postmortem.md>), [realtime](<https://devfeed.tech/tags/realtime.md>), [slack](<https://devfeed.tech/tags/slack.md>), [systems](<https://devfeed.tech/tags/systems.md>)

## AI overview

Localytics describes its process for responding to service degradations and downtime. The process uses Slack and PagerDuty to coordinate triage, debugging, incident follow-up, postmortems, and communication with company leaders and customers.

## Source excerpt

We believe the highest performing engineering teams have a process to identify, triage, fix and learn from service degradations and downtime. At Localytics, we build highly available and scalable systems, and part of the key to our success is learning from failures. One way we foster a learning culture is