Kustomer logo

Is Kustomer Down?

MarketingLive status, outages, and incident history

No. Kustomer is up right now.

Every monitored Kustomer system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Kustomer breaks

Kustomer is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Kustomer status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Kustomer Status Summary

As of 21:01 UTC on 9 November 2026, Kustomer is operational. PulsAPI checked Kustomer's official status page and found 56 of 56 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Kustomer, counting degraded performance as up. The latest incident, "Workflows delays in processing PROD2", was on Nov 3, 2026 and lasted 1h 9m.

Cite as: PulsAPI, “Kustomer status”, checked 9 November 2026, 21:01 UTC. https://www.pulsapi.com/services/kustomer

Kustomer Component Status

The main Kustomer systems on this page. All 56 are operational right now.

56operational
Kustomer Voice & Text » Kustomer Voice
Operational
Prod1 (US) » Analytics
Operational
Prod1 (US) » API
Operational

53 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Prod1 (US) » Bulk Jobs, Prod1 (US) » Channel - Chat, Prod1 (US) » Channel - Email, Prod1 (US) » CSAT, Prod1 (US) » Events / Audit Log, Prod1 (US) » Exports, Prod1 (US) » Knowledge base, Prod1 (US) » Notifications, Prod1 (US) » Registration, Prod1 (US) » Search, Prod1 (US) » Tracking, Prod1 (US) » Web Client, and 41 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Kustomer Outages & Incidents

Incident history from the official Kustomer status page, including resolution updates.

Workflows delays in processing PROD2Resolved Nov 3, 2026 · 1h 9mResolved

## Summary On November 3, 2026, customers in Kustomer’s EU environment experienced delayed workflow execution from approximately 16:30 to 18:10 UTC, lasting about 1 hour and 40 minutes. The incident is resolved. Workflow processing returned to normal and the processing backlog was cleared by 18:10 UTC. ## Impact Workflow execution was delayed for customers in the affected EU environment, which may have delayed automated conversation updates and routing. Other environments were unaffected. No data loss is expected. ## Timeline All times are UTC on November 3, 2026. * **16:30:** Workflow delays began accumulating. * **16:54:** Monitoring alerted responders, who began investigating. * **17:21:** The workflows generating excessive activity were disabled, stopping the source of the incident. * **18:10:** The remaining processing backlog was cleared and normal workflow processing was restored. ## Root Cause Repeated automated workflow activity generated an unusually high volume of processing requests. This increased processing demand and delayed workflow execution in the affected EU environment. ## Resolution We disabled the workflows generating the excessive activity, temporarily increased processing capacity, and recovered pending work to clear the backlog. Temporary recovery settings were restored after processing recovered. ## Preventative Actions Our follow-up work focuses on identifying excessive workflow activity earlier and reducing the risk of recurrence: * Review monitoring thresholds to detect workflow processing delays sooner. * Evaluate automated safeguards and customer notifications for workflows with sustained high error rates. * Evaluate workflow configuration checks to help identify unintended repeated execution. --- [2026-11-03T13:30:55.245-05:00] (resolved) Kustomer has resolved an event affecting workflows that caused delays in workflow processing. Our team has cleared the queue for workflows. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at support@kustomer.com if you have additional questions or concerns. --- [2026-11-03T12:52:57.900-05:00] (monitoring) Kustomer has implemented an update to address an event affecting workflows that caused delays in workflow processing. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at support@kustomer.com if you have additional questions or concerns. --- [2026-11-03T12:42:22.557-05:00] (identified) Kustomer has identified an increased error rate within workflows that is causing a delay in processing. Our team is currently working to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at support@kustomer.com if you have additional questions or concerns. --- [2026-11-03T12:21:13.470-05:00] (investigating) Kustomer is aware of an event affecting workflow that may cause delays workflow execution. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support support@kustomer.com for any further questions or updates.

[Kustomer Voice] Unable to Dial Outbound Calls - All PRODSResolved Sep 9, 2026 · 26 minResolved

## Summary On September 9, 2026, a service event prevented users from initiating some outbound Voice calls. When affected users selected **Call**, the call did not begin. ## Impact The event affected outbound Voice call initiation for four organizations. Other Voice workflows may have continued to operate normally. No data loss or security impact has been identified. ## Timeline * **September 9, 12:27 PM ET:** A Voice application update was released. * **September 9, approximately 2:00 PM ET:** Reports of affected outbound calls began. * **September 9, approximately 3:19 PM ET:** Mitigation began. * **September 9, approximately 3:30 PM ET:** Outbound Voice calling was restored. ## Root Cause A Voice application update caused some outbound call attempts to fail. The affected update was rolled back. ## Resolution The affected update was rolled back, restoring outbound Voice calling for affected users. The incident investigation is complete. ## Preventative Actions * Improve recovery procedures to reduce service restoration time during future service events. * Add validation coverage for supported outbound-calling configurations before future releases. * Improve monitoring, internal alerting, and user feedback when a call cannot be initiated. --- [2026-09-09T15:52:08.604-04:00] (resolved) Kustomer has resolved an event affecting Kustomer Voice across all PRODs. To resolve this issue, our team has rolled back an update. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at support@kustomer.com if you have additional questions or concerns. --- [2026-09-09T15:45:04.921-04:00] (monitoring) Kustomer has implemented an update to address an event affecting Kustomer Voice across all PRODs. Our team is currently monitoring this update to ensure the issue is fully resolved. In order to fully resolve the issue on your end please have all agents refresh their Kustomer Instance. --- [2026-09-09T15:25:29.533-04:00] (investigating) Kustomer has identified an event affecting Kustomer Voice across all PRODS that may cause issues when attempting to make outbound calls. Our team is currently working to implement a resolution. Please expect further updates within the next 30 minutes.

kustomer.help Default Domain – Visibility Issue – ALL PRODsResolved Sep 8, 2026 · 16 minResolved

# **Summary** On September 7–8, 2026, some customers were unable to access Knowledge Base pages and related survey links hosted on the default `*.kustomer.help` domain. Customers using the default Knowledge Base domain in the prod1 environment encountered browser certificate warnings that prevented access to Knowledge Base content. Related links using the same domain, including some survey links, were also affected. Customers using custom Knowledge Base domains and shared Knowledge Base domains in other production environments were not affected. # **Root Cause** A security certificate used by the shared Knowledge Base domain expired before its renewal validation was completed. This caused browsers to reject connections to links served through that domain, while the underlying Knowledge Base service remained available. # **Timeline** **Sep 7, 2026** **8:00 PM ET**: Kustomer’s default Knowledge Base Domain certificate expired. At this time, customers may have begun encountering certificate warnings when accessing Knowledge Base content. ‌ **Sep 8, 2026** **8:37 AM ET** Kustomer receives reports of certificate warnings for default Knowledge Base Domain content and related links **8:38 AM ET** Kustomer Engineering is notified and begins our On-Call Incident Management process **9:00 AM ET** Kustomer Engineering identifies the shared-domain certificate issue and begins remediation steps **9:24 AM ET** Kustomer Engineering completes remediation steps **9:37 AM ET** Kustomer’s certificate provider acknowledges the remediation steps were complete and provisions a new certificate for the default Knowledge Base domain, restoring service # **Lessons/Improvements** Kustomer Engineering has a dedicated Infrastructure team that continuously works to maintain and improve Kustomer’s availability, reliability, fault tolerance. As part of our continual investment in these areas, we have identified the following action items related to this issue: * Move the shared-domain certificate to an automated renewal approach. * Add proactive monitoring and alerting for certificate expiration across shared customer-facing domains. * Review other certificates using the same renewal approach and prioritize any needed updates. * Document recovery procedures and ownership for certificate renewal activities. --- [2026-09-08T09:39:02.271-04:00] (resolved) Kustomer has resolved an event affecting links and content utilising the default kustomer.help domain (not custom client domains) that caused visibility issues. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer Support at support@kustomer.com if you have additional questions or concerns. --- [2026-09-08T09:24:04.179-04:00] (investigating) We are continuing to investigate this issue. --- [2026-09-08T09:23:00.252-04:00] (investigating) Kustomer is aware of an event affecting links and content utilising the default kustomer.help domain (not custom client domains) — including Help Center URLs and CSAT surveys — that may cause visibility issues. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support at support@kustomer.com for any further questions or updates.

Kustomer Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Kustomer incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 4 days with incidentsNov 9

Going further back: Kustomer uptime by month and every recorded Kustomer outage.

Live Kustomer Outage Reports

Problems reported by engineers using Kustomer. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Kustomer problems reported yet.

Something wrong with Kustomer on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Kustomer

Kustomer exposes 61 monitored components on its status page at status.kustomer.com — Analytics, Prod1 (US) and Kustomer Voice among them. Follow Kustomer downtime, degraded performance and resolved incidents here, with uptime history alongside your other marketing services.

Over the past 30 days, PulsAPI has measured Kustomer uptime at 100.00%. Response times, incident history, and SLA tracking for Kustomer are available on the PulsAPI dashboard.

Kustomer Status FAQ

Is Kustomer down right now?

The verdict at the top of this page comes from the latest poll of the official Kustomer status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Kustomer is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Kustomer recovers.

How do I check Kustomer uptime history?

PulsAPI tracks Kustomer uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Kustomer changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Kustomer outages?

PulsAPI reads the official Kustomer status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Kustomer components?

Yes. PulsAPI monitors 56 individual Kustomer components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Kustomer goes down?

Yes. Create a free account and subscribe to Kustomer: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Kustomer to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Kustomer problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Kustomer?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Kustomer plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Kustomer with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services