Chili Piper Outage History

Chili Piper is up right now

Pingoru has recorded 50 incidents for Chili Piper: 16 in the last 12 months and 1 in the last 90 days.

Source: status.chilipiper.com

50incidents recorded
16last 12 months
1last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Chili Piper in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202646 of 720 (1%)
May 202610 of 744 (0%)
June 202611 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 2026124 of 720 (3%)
October 202600 of 591 (0%)

Incidents, newest first

Major April 8, 2025 [Legacy app] Admin center unresponsive in Chrome v135 6h 31m

Started Apr 08, 2025, 06:27 PM UTC· resolved Apr 09, 2025, 12:58 AM UTC

  1. investigating Apr 08, 2025, 06:27 PM UTC

    We have discovered that as of the latest update in Google Chrome version 135, the "Admin Center" in our legacy app (apps.chilipiper.com) becomes unresponsive due to memory usage. You are still able to navigate around workspaces, and from workspace-to-workspace, but the browser will become unresponsive if you attempt to navigate back to the Admin Center. Our engineers are investigating the cause right now as it relates to v135. Older versions of Chrome are confirmed not to be impacted. Other browsers or chrome-based browsers appear to be unaffected as well. This does not impact our Demand Conversion Platform (Fire) app.

  2. resolved Apr 09, 2025, 12:58 AM UTC

    We identified a third-party script was causing the admin center page to hang. We have blocked this script, and pages now load as expected. No further impact is expected as a result of blocking this script.

Read the full incident report →

Minor March 13, 2025 [Fire] Constant loading of Concierge services and no Handoff routers loading –

Started Mar 13, 2025, 03:30 PM UTC· resolved Mar 13, 2025, 03:30 PM UTC

  1. resolved Mar 13, 2025, 04:08 PM UTC

    Our team was made aware of a wide-spread issue involving the ChiliCal scheduler for Handoff not loading routers, 404 pages being experienced, errors indicating a connection cannot be established, and perpetual loading of Concierge routes. This issue was a result of unplanned database maintenance which triggered the temporary outage. This does not appear to have impacted our legacy / classic services at this time. We are seeing all services up and running after a brief approximately 20 minute outage.

Read the full incident report →

Major March 11, 2025 Multiple Language Settings in browser cause a "Something Went Wrong Page" 49m Booking Links

Started Mar 11, 2025, 09:01 AM UTC· resolved Mar 11, 2025, 09:51 AM UTC

  1. investigating Mar 11, 2025, 09:01 AM UTC

    We are currently investigating an issue where Chili Piper Concierge or Scheduling links display a "Something Went Wrong" error page for users with multiple languages set in their Google Chrome settings. Our team is treating this with the utmost urgency, and we are working diligently to identify and resolve the cause. We will provide updates as soon as we have more information.

  2. resolved Mar 11, 2025, 09:51 AM UTC

    Issue is now resolved and users will no longer see the "Something Went Wrong" Page if they have multiple languages in their browser. Thank you for your continued patience and understanding.

Read the full incident report →

Minor February 13, 2025 Issue loading Concierge for marketing script customers 10m

Started Feb 13, 2025, 07:02 PM UTC· resolved Feb 13, 2025, 07:12 PM UTC

  1. monitoring Feb 13, 2025, 07:02 PM UTC

    Customers using our "marketing.js" Concierge snippet on their landing pages will have experienced an issue where no submissions were coming through. Symptom is that the snippet sends an error to the Chrome developer console noting an "undefined" "jwt bearer token". We were alerted to this incident around 12:45 PM ET, and the code causing the issue was rolled back at approximately 2:00 PM ET, meaning there was a window of just over an hour where no submissions would come through. As we've rolled back the code, we are now monitoring to determine if the incident is now resolved and will act quickly if we still see any occurrences.

  2. resolved Feb 13, 2025, 07:12 PM UTC

    We've confirmed the fix is in place, and routing is working as expected.

Read the full incident report →

Minor December 9, 2024 HS Custom Properties and Router Flow Issue 3h 14m

Started Dec 09, 2024, 11:07 AM UTC· resolved Dec 09, 2024, 02:22 PM UTC

  1. identified Dec 09, 2024, 11:07 AM UTC

    We are currently experiencing an issue where HS custom properties are not being updated as expected. Additionally, the router flow is encountering a blockage at the "Create/Update Contact" node, preventing the execution of subsequent tasks. Our team is actively investigating the root cause and working to resolve this issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we work toward a solution.

  2. resolved Dec 09, 2024, 02:22 PM UTC

    Our Engineering Team identified the root cause of this issue and deployed the required fix. HubSpot actions like "Update Property", "Create/Update Contact, and "Create Engagement" nodes should work as they should from now on. If you still notice any issues, please reach out to [email protected] with examples so they can be further investigated.

Read the full incident report →

Notice December 6, 2024 Cache is preventing pages from loading properly –

Started Dec 06, 2024, 01:30 PM UTC· resolved Dec 06, 2024, 01:30 PM UTC

  1. resolved Dec 10, 2024, 04:37 PM UTC

    Some users may experience a "Something went wrong" message when accessing admin-center dashboards or pages in our Fire UI. This was due to a caching issue with a previous deployment. To fix this issue, simply clear your browser cache, or clear all browsing data. In your browser you can press COMMAND + Shift + R (or CTRL + Shift + R) to hard-refresh the page. Or, you can use the browser's settings menu to select "Delete Browsing Data", making sure to select the cached images and files for deletion. Otherwise, this issue will resolve itself with time as the cache expires. Please don't hesitate to reach out to [email protected] if you have attempted to clear your cache and still experience issues loading pages.

Read the full incident report →