Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Kustomer and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Kustomer.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Regional Incident | Active |
Prod1 (US) | Active |
Analytics | Active |
API | Active |
Bulk Jobs | Active |
Channel - Chat | Active |
Channel - Email | Active |
Channel - Facebook | Active |
Channel - Instagram | Active |
Channel - SMS | Active |
Channel - Twitter | Active |
Channel - WhatsApp | Active |
CSAT | Active |
Events / Audit Log | Active |
Exports | Active |
Knowledge base | Active |
Kustomer Voice | Active |
Notifications | Active |
Registration | Active |
Search | Active |
Tracking | Active |
Web Client | Active |
Web/Email/Form Hooks | Active |
Workflow | Active |
Prod2 (EU) | Active |
Analytics | Active |
API | Active |
Bulk Jobs | Active |
Channel - Chat | Active |
Channel - Email | Active |
Channel - Facebook | Active |
Channel - Instagram | Active |
Channel - SMS | Active |
Channel - Twitter | Active |
Channel - WhatsApp | Active |
CSAT | Active |
Events / Audit Log | Active |
Exports | Active |
Knowledge base | Active |
Kustomer Voice | Active |
Notifications | Active |
Registration | Active |
Search | Active |
Tracking | Active |
Web Client | Active |
Web/Email/Form Hooks | Active |
Workflow | Active |
Third Party | Active |
OpenAI | Active |
PubNub | Active |
View the latest incidents for Kustomer and check for official updates:
Description: Kustomer has resolved an event affecting Chat Channel in PROD 1 that caused long delays in chat messaging or messages to not be sent at all. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support through Chat or Email if you have additional questions or concerns.
Status: Resolved
Impact: Minor | Started At: Nov. 14, 2024, 11:20 p.m.
Description: Kustomer has resolved an event affecting searches that may cause Degraded Performance when performing searches. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at if you have additional questions or concerns.
Status: Resolved
Impact: Minor | Started At: Oct. 24, 2024, 2:47 p.m.
Description: Kustomer has resolved an event affecting the platform that caused a delay in notifications, chat sending and any updates in the platform. To resolve this issue, our team has worked with our third party vendor. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.
Status: Resolved
Impact: None | Started At: Oct. 24, 2024, 12:46 p.m.
Description: Kustomer has resolved an event affecting Searches that may cause searches to be unavailable within the platform for some orgs. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.
Status: Resolved
Impact: Minor | Started At: Oct. 10, 2024, 4:51 p.m.
Description: # **Summary** We had an increase in errors across search and reporting for a subset of customers in Prod1 # **Root Cause** We had multiple organizations with badly performing search queries that were continuously polling. This led to degraded performance across our cluster as the cascading effect led to other search queries beginning to slow down being in queue and our CPU usage began to increase. We identified the two orgs who had searches that were negatively impacting the cluster and stopped those searches to resolve the issue # **Timeline** * 9:35 AM EDT Increased latency began with search and reporting * 9:52 AM EDT We began to get alerted to search related errors in the platform and began investigating the root cause * 10:25 AM EDT We identified that the root cause was an abundance of slow search queries being backed up in their queue which increased our CPU usage. We then began investigating the source of the slow queries * 11:30 AM EDT We identified an org that we believed to be the source due to having badly performing search queries running. We stopped the searches for that org which improved performance but didn’t resolve it fully as CPU usage remained high. We continued investigating to find what other org might be leading to the increased CPU usage * 12:56 AM EDT We stopped the badly performing searches for a second org which improved performance back to pre-incident levels # **Lessons/Improvements** * **Decrease the impact of badly performing searches** - We’ve begun limiting the cases in which we poll for searches and have also begun disabling polling for badly performing searches. We are updating our search builder so that users can consolidate search queries to make them more performant * \[DONE\] Automatically disabling badge count polling on badly performing searches * \[IN PROGRESS\] Upgrading our hardware to a more recent version that is more resilient and more performant * \[TO DO\] Improved the search builder to give it the ability to consolidate queries * **Improve internal monitoring for search failures** - We were alerted to search related errors but during investigation realized that we could improve our monitoring and alerting to be notified of the issues earlier so that we could triage faster * \[IN PROGRESS\] Investigate and implement optimal monitoring and alerting strategies for slow search queries
Status: Postmortem
Impact: Minor | Started At: Sept. 30, 2024, 2:44 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.