Is Kustomer down?

Last checked just now
Current status
Kustomer is up

No incidents right now.

Kustomer is operational right now. Last checked just now; the most recent incident resolved 50d ago.

Real-time Kustomer status, recent outages, and incident history: pulled directly from Kustomer's official status page at status.kustomer.com every 5 minutes. Pingoru tracks 56 Kustomer services and has captured 3 incidents in the last 90 days (99.76% uptime). Get email, Slack, Discord, or webhook alerts the moment Kustomer reports a new incident, free for 3 monitors, no credit card.

Users who monitor Kustomer also follow these Sales services: Gong LinkedIn API Salesloft Clari Apollo.io Seismic Software Proposify Huggy Mindtickle Cirrus Insight View all 8,000+ providers
Kustomer uptime 99.76% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 26m
    Started Sep 09, 2026, 07:25 PM UTC · Resolved Sep 09, 2026, 07:52 PM UTC
    Kustomer Voice
    Timeline · 4 updates
    • investigating · Sep 09, 2026, 07:25 PM UTC

      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.

    • monitoring · Sep 09, 2026, 07:45 PM UTC

      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.

    • resolved · Sep 09, 2026, 07:52 PM UTC

      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 [email protected] if you have additional questions or concerns.

    • postmortem · Oct 02, 2026, 05:55 PM UTC

      ## 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.

    Latest: ## 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…

  2. Resolved 16m
    Started Sep 08, 2026, 01:23 PM UTC · Resolved Sep 08, 2026, 01:39 PM UTC
    CSATCSATCSATKnowledge baseKnowledge baseKnowledge base
    Timeline · 4 updates
    • investigating · Sep 08, 2026, 01:23 PM UTC

      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 [email protected] for any further questions or updates.

    • investigating · Sep 08, 2026, 01:24 PM UTC

      We are continuing to investigate this issue.

    • resolved · Sep 08, 2026, 01:39 PM UTC

      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 [email protected] if you have additional questions or concerns.

    • postmortem · Sep 10, 2026, 09:05 PM UTC

      # **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.

    Latest: # **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 u…

  3. Resolved 25m
    Started Aug 25, 2026, 01:51 PM UTC · Resolved Aug 25, 2026, 02:17 PM UTC
    Channel - ChatNotificationsTrackingPubNubWeb Client
    Timeline · 2 updates
    • monitoring · Aug 25, 2026, 01:51 PM UTC

      Kustomer is aware of an event reported by one of our third party vendors (PubNub) affecting real-time messaging for orgs in Prod1 that may cause chat messages, agent notifications, and live updates to be delayed or not appear in real time within the platform. Our team is actively monitoring the incident, and working with the vendor where possible to resolve the issue. You can also follow PubNub's status here: https://status.pubnub.com/incidents/cz6q37z3s1d5. Please expect further updates within the next 3 hours, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

    • resolved · Aug 25, 2026, 02:17 PM UTC

      The PubNub-related event previously reported affecting real-time messaging for orgs in Prod1 has been resolved. PubNub has confirmed the issue has been mitigated on their end - no messages were missed and no customer impact occurred during the event. All affected areas remain fully operational. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

    Latest: The PubNub-related event previously reported affecting real-time messaging for orgs in Prod1 has been resolved. PubNub has confirmed the issue has been mitigated on their end - no …

Incident record

Since April 2026 · Statuspage by Atlassian · 56 components checked every 5 minutes
50incidents recorded
24last 12 months
3last 90 days
3 hourstypical duration, 12 months

The longest incident in the last year, [Satisfaction Surveys] CSATs may not send for voice, email and sms channels - Prod 1 on January 27, 2026, ran for 28 hours.

Most affected components, last 12 months

  • Channel - Chat10
  • Channel - Email6
  • Channel - Email3
  • Knowledge base3
  • CSAT2

Latest incidents

  • [Kustomer Voice] Unable to Dial Outbound Calls - All PRODS September 9, 2026 · 26 minutes · degraded service

    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…

  • kustomer.help Default Domain – Visibility Issue – ALL PRODs September 8, 2026 · 16 minutes · degraded service

    Kustomer is aware of an event affecting links and content utilising the default kustomer.help domain (not custom client domains) — including Help Center URLs…

  • Reported Third Party Event - [PubNub] August 25, 2026 · 25 minutes · degraded service

    Kustomer is aware of an event reported by one of our third party vendors (PubNub) affecting real-time messaging for orgs in Prod1 that may cause chat messages…

Outage history

Past 90 days · 3 incidents View full outage history →