<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Whippy Status - Incident history</title>
    <link>https://status.whippy.co</link>
    <description>Whippy</description>
    <pubDate>Thu, 18 Dec 2025 15:45:35 +0000</pubDate>
    
<item>
  <title>Issue with Cloudflare Network in Some Regions</title>
  <description>
    Type: Incident
    Duration: 7 hours and 44 minutes

    Affected Components: Web Application - Dashboard
    Dec 18, 15:45:35 GMT+0 - Monitoring - Cloudflare is currently investigating increased latency with [Cloudflare Gateway](https://www.google.com/search?q=Cloudflare+Gateway&amp;sca%5Fesv=0ccf53d8b4904cec&amp;sxsrf=AE3TifOFhHnHVn-KUNUmlX04kM%5FOmxm0tg%3A1766072569406&amp;ei=-SBEaZnFGJyFhbIP5dHQQA&amp;ved=2ahUKEwii6JSEvceRAxUKXEEAHSQ3PTkQgK4QegQIARAB&amp;uact=5&amp;oq=cloudflare+dns+issue&amp;gs%5Flp=Egxnd3Mtd2l6LXNlcnAiFGNsb3VkZmxhcmUgZG5zIGlzc3VlMgsQABiABBiKBRiRAjIGEAAYBxgeMgYQABgHGB4yBRAAGIAEMgQQABgeMgQQABgeMgYQABgIGB4yBhAAGAgYHjIGEAAYCBgeMgsQABiABBiKBRiGA0jMDFCEB1jACXAAeAKQAQCYAVOgAYACqgEBNLgBA8gBAPgBAZgCBaACjwLCAgQQABhHwgIHECMYsAIYJ8ICBxAAGIAEGA3CAggQABgIGAcYHsICBhAAGB4YDcICCBAAGAgYHhgNmAMA4gMFEgExIECIBgGQBgiSBwE1oAeMG7IHATS4B40CwgcDMC41yAcKgAgB&amp;sclient=gws-wiz-serp&amp;mstk=AUtExfBdGhp9w6-IDfhH%5FGBE0QJQ-eFmGoXTKrhToZMkjRXXoQ0hTC2Xo6n4GRWrRkuOselAbSVCOUxU7tqd2qrxddPNYDJVmdYTFwU4R8vZO7uuMe8njx5GnDBcF42lVAU1ls%5FYPOvIiAurfETU%5Fb8czdNRwKQ%5F-%5Fl9lA--BTKH8Sx09ya1Jb3%5FGff5Sz-UQQ8--66o6sqzXdnomsCrl7IxmFz4KeTRUjF3r2tKT4mp91g7ksccZ33R31ErDf-egkSy6wPbVdhONahroBjMDmQQHubN&amp;csui=3) (Sacramento) as of Dec 18, 2025\. Recent issues stemmed from a Nov 2025 outage caused by a config file update disrupting traffic, rather than an attack. Typical user DNS issues include **incorrect records, misconfigured DNSSEC, or incorrect nameservers** Dec 18, 23:29:08 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:45:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Cloudflare is currently investigating increased latency with [Cloudflare Gateway](https://www.google.com/search?q=Cloudflare+Gateway&amp;sca%5Fesv=0ccf53d8b4904cec&amp;sxsrf=AE3TifOFhHnHVn-KUNUmlX04kM%5FOmxm0tg%3A1766072569406&amp;ei=-SBEaZnFGJyFhbIP5dHQQA&amp;ved=2ahUKEwii6JSEvceRAxUKXEEAHSQ3PTkQgK4QegQIARAB&amp;uact=5&amp;oq=cloudflare+dns+issue&amp;gs%5Flp=Egxnd3Mtd2l6LXNlcnAiFGNsb3VkZmxhcmUgZG5zIGlzc3VlMgsQABiABBiKBRiRAjIGEAAYBxgeMgYQABgHGB4yBRAAGIAEMgQQABgeMgQQABgeMgYQABgIGB4yBhAAGAgYHjIGEAAYCBgeMgsQABiABBiKBRiGA0jMDFCEB1jACXAAeAKQAQCYAVOgAYACqgEBNLgBA8gBAPgBAZgCBaACjwLCAgQQABhHwgIHECMYsAIYJ8ICBxAAGIAEGA3CAggQABgIGAcYHsICBhAAGB4YDcICCBAAGAgYHhgNmAMA4gMFEgExIECIBgGQBgiSBwE1oAeMG7IHATS4B40CwgcDMC41yAcKgAgB&amp;sclient=gws-wiz-serp&amp;mstk=AUtExfBdGhp9w6-IDfhH%5FGBE0QJQ-eFmGoXTKrhToZMkjRXXoQ0hTC2Xo6n4GRWrRkuOselAbSVCOUxU7tqd2qrxddPNYDJVmdYTFwU4R8vZO7uuMe8njx5GnDBcF42lVAU1ls%5FYPOvIiAurfETU%5Fb8czdNRwKQ%5F-%5Fl9lA--BTKH8Sx09ya1Jb3%5FGff5Sz-UQQ8--66o6sqzXdnomsCrl7IxmFz4KeTRUjF3r2tKT4mp91g7ksccZ33R31ErDf-egkSy6wPbVdhONahroBjMDmQQHubN&amp;csui=3) (Sacramento) as of Dec 18, 2025\. Recent issues stemmed from a Nov 2025 outage caused by a config file update disrupting traffic, rather than an attack. Typical user DNS issues include **incorrect records, misconfigured DNSSEC, or incorrect nameservers**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:29:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 18 Dec 2025 15:45:35 +0000</pubDate>
  <link>https://status.whippy.co/incident/cmjbm3j8x01ckg2sikjlc368j</link>
  <guid>https://status.whippy.co/incident/cmjbm3j8x01ckg2sikjlc368j</guid>
</item>

<item>
  <title>Connecting to AI Calls</title>
  <description>
    Type: Incident
    Duration: 11 minutes

    Affected Components: Web Application - Dashboard
    Dec 16, 15:44:59 GMT+0 - Investigating - We are having issues connecting inbound phone calls to AI Agents. We are currently investigating this incident. Dec 16, 15:55:40 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:44:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are having issues connecting inbound phone calls to AI Agents. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:55:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 16 Dec 2025 15:44:59 +0000</pubDate>
  <link>https://status.whippy.co/incident/cmj8r71pq00ba3a73zo2kmdam</link>
  <guid>https://status.whippy.co/incident/cmj8r71pq00ba3a73zo2kmdam</guid>
</item>

<item>
  <title>Whippy Affected by Cloudflare Outage</title>
  <description>
    Type: Incident
    Duration: 13 minutes

    Affected Components: Messaging, Automations, Web Application - Dashboard, Webchat, Reviews, Campaigns
    Dec 5, 09:01:43 GMT+0 - Identified - Cloudflare is currently experiencing an outage that is affecting user access to Whippy - &lt;https://www.cloudflarestatus.com/&gt;.

We will post an update as soon as we have one.  Dec 5, 09:14:45 GMT+0 - Resolved - A fix has been implemented by Cloudflare, and we are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:01:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Cloudflare is currently experiencing an outage that is affecting user access to Whippy - &lt;https://www.cloudflarestatus.com/&gt;.

We will post an update as soon as we have one. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:14:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  A fix has been implemented by Cloudflare, and we are currently monitoring the result..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 5 Dec 2025 09:01:43 +0000</pubDate>
  <link>https://status.whippy.co/incident/cmismy47709muk7rm6k84rket</link>
  <guid>https://status.whippy.co/incident/cmismy47709muk7rm6k84rket</guid>
</item>

<item>
  <title>DNS Issue with Cloud Provider</title>
  <description>
    Type: Incident
    

    Affected Components: Web Application - Dashboard
    Nov 5, 19:30:44 GMT+0 - Resolved - Our cloud provider Render is having an issue with their Oregan data centre, causing the web dashboard to not load in for some customer. They implemented a fix and are currently monitoring the result. Nov 5, 20:07:19 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Our cloud provider Render is having an issue with their Oregan data centre, causing the web dashboard to not load in for some customer. They implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:07:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 5 Nov 2025 19:30:44 +0000</pubDate>
  <link>https://status.whippy.co/incident/cmhmgn7jw012y8rehy421979c</link>
  <guid>https://status.whippy.co/incident/cmhmgn7jw012y8rehy421979c</guid>
</item>

<item>
  <title>Not Found Error on Non Route Domains</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: Web Application - Dashboard
    Feb 9, 00:23:44 GMT+0 - Identified - We have identified an issue where if you refresh Whippy on any page but out root domain (&lt;https://app.whippy.co&gt;) then the website shows &quot;Not Found&quot;.

To remedy this while we fix this with our hosting provider please access Whippy from &lt;https://app.whippy.co&gt; only.

Bar this the application is fully functional at this time; however, the chrome extension is not accessible at this time.  Feb 9, 00:32:06 GMT+0 - Resolved - This incident has been resolved, our cloud provider has rolled back a change to their proxy server that caused our dashboard to show not found unless accessed from the root domain.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:23:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified an issue where if you refresh Whippy on any page but out root domain (&lt;https://app.whippy.co&gt;) then the website shows &quot;Not Found&quot;.

To remedy this while we fix this with our hosting provider please access Whippy from &lt;https://app.whippy.co&gt; only.

Bar this the application is fully functional at this time; however, the chrome extension is not accessible at this time. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:32:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved, our cloud provider has rolled back a change to their proxy server that caused our dashboard to show not found unless accessed from the root domain. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 9 Feb 2024 00:23:44 +0000</pubDate>
  <link>https://status.whippy.co/incident/clsdwmuru24870bcn5ji5en0wd</link>
  <guid>https://status.whippy.co/incident/clsdwmuru24870bcn5ji5en0wd</guid>
</item>

<item>
  <title>Slow Loading</title>
  <description>
    Type: Incident
    Duration: 2 hours and 22 minutes

    Affected Components: Web Application - Dashboard
    Dec 5, 13:54:51 GMT+0 - Identified - We have identified the issue caused by excessive login attempts from a bad actor who we are in the process of blocking.

Some users will be unable to login. Currently logged in users should not experience any issues. 

We are will post an update shortly. Dec 5, 12:40:23 GMT+0 - Investigating - We&#039;re currently investigating reports of slow loading. We will post an update shortly.  Dec 5, 15:02:16 GMT+0 - Resolved - An earlier issue that caused slow loading and blocked already logged out users from logging in has been resolved. However, we are still monitoring the fix.

The issue was caused by a bad actor trying to run a scraping bot on our systems.

We blocked this bad actor, but needed to temporally pause logins to make sure we could block all related IP Addresses.

Thank you for your patience while be resolved this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:54:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the issue caused by excessive login attempts from a bad actor who we are in the process of blocking.

Some users will be unable to login. Currently logged in users should not experience any issues. 

We are will post an update shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:40:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;re currently investigating reports of slow loading. We will post an update shortly. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:02:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  An earlier issue that caused slow loading and blocked already logged out users from logging in has been resolved. However, we are still monitoring the fix.

The issue was caused by a bad actor trying to run a scraping bot on our systems.

We blocked this bad actor, but needed to temporally pause logins to make sure we could block all related IP Addresses.

Thank you for your patience while be resolved this issue..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 5 Dec 2023 12:40:23 +0000</pubDate>
  <link>https://status.whippy.co/incident/clpsbvz4e49222bloh53k26kpb</link>
  <guid>https://status.whippy.co/incident/clpsbvz4e49222bloh53k26kpb</guid>
</item>

<item>
  <title>Login &amp; API Issues</title>
  <description>
    Type: Incident
    Duration: 9 hours

    Affected Components: Campaigns, Webchat, Web Application - Dashboard, Messaging, Automations, Reviews
    Nov 21, 19:00:00 GMT+0 - Investigating - Issue: We are currently experiencing technical difficulties with our login system and API services. This may affect your ability to access your account and utilize our API functionalities.

Impact: Users may face challenges logging into their accounts or experience intermittent issues with API connectivity.

Current Status: Our technical team is actively working to resolve these issues. We apologize for any inconvenience caused and appreciate your patience as we work towards a solution. Nov 21, 19:09:00 GMT+0 - Resolved - Resolved Issue: We are pleased to inform you that the technical difficulties impacting our login system and API services have been resolved.

Cause of Disruption: Our team has identified that the disruption was due to an outage caused by one of our downstream cloud partners. This outage was blocking requests to our Whippy service, leading to the issues experienced by our users.

Current Status: All systems are now fully operational, and users should be able to access their accounts and use our API services without any interruptions.

Ongoing Actions: We are actively investigating this matter to understand the root cause in depth. Our aim is to implement measures that will prevent similar occurrences in the future. We are committed to maintaining a reliable and secure platform for all our users.

Acknowledgement: We sincerely apologize for any inconvenience caused and thank you for your patience and understanding during this time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Issue: We are currently experiencing technical difficulties with our login system and API services. This may affect your ability to access your account and utilize our API functionalities.

Impact: Users may face challenges logging into their accounts or experience intermittent issues with API connectivity.

Current Status: Our technical team is actively working to resolve these issues. We apologize for any inconvenience caused and appreciate your patience as we work towards a solution..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:09:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Resolved Issue: We are pleased to inform you that the technical difficulties impacting our login system and API services have been resolved.

Cause of Disruption: Our team has identified that the disruption was due to an outage caused by one of our downstream cloud partners. This outage was blocking requests to our Whippy service, leading to the issues experienced by our users.

Current Status: All systems are now fully operational, and users should be able to access their accounts and use our API services without any interruptions.

Ongoing Actions: We are actively investigating this matter to understand the root cause in depth. Our aim is to implement measures that will prevent similar occurrences in the future. We are committed to maintaining a reliable and secure platform for all our users.

Acknowledgement: We sincerely apologize for any inconvenience caused and thank you for your patience and understanding during this time..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 21 Nov 2023 19:00:00 +0000</pubDate>
  <link>https://status.whippy.co/incident/clp8rpz2v7763bln8evnn8q3l</link>
  <guid>https://status.whippy.co/incident/clp8rpz2v7763bln8evnn8q3l</guid>
</item>

<item>
  <title>Scheduled Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 27 minutes

    Affected Components: Campaigns, Webchat, Web Application - Dashboard, Messaging, Automations, Reviews
    Oct 22, 07:00:00 GMT+0 - Identified - We wanted to inform you about a scheduled maintenance window set for this upcoming Sunday. During this time, service may be unavailable but all inbound/outbound messages will be preserved. Please reach out to Support if you have any questions!

Date:

- Sunday, 22nd October 2023.

Times:

- UTC: 07:00 AM - 10:00 AM
- EST: 03:00 AM - 06:00 AM
- Central: 02:00 AM - 05:00 AM
- PST: 12:00 AM (Midnight) Saturday - 03:00 AM Sunday Oct 22, 09:27:01 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We wanted to inform you about a scheduled maintenance window set for this upcoming Sunday. During this time, service may be unavailable but all inbound/outbound messages will be preserved. Please reach out to Support if you have any questions!

Date:

- Sunday, 22nd October 2023.

Times:

- UTC: 07:00 AM - 10:00 AM
- EST: 03:00 AM - 06:00 AM
- Central: 02:00 AM - 05:00 AM
- PST: 12:00 AM (Midnight) Saturday - 03:00 AM Sunday.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:27:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 22 Oct 2023 07:00:00 +0000</pubDate>
  <link>https://status.whippy.co/maintenance/clnz28x55108960b7n0mcjlnfv6</link>
  <guid>https://status.whippy.co/maintenance/clnz28x55108960b7n0mcjlnfv6</guid>
</item>

<item>
  <title>Our Cloud Service Provider is Reporting Slow Loading</title>
  <description>
    Type: Incident
    Duration: 38 minutes

    Affected Components: Campaigns, Webchat, Web Application - Dashboard, Messaging, Automations, Reviews
    Sep 25, 20:54:15 GMT+0 - Investigating - We are currently investigating this incident. 

Our cloud service provider is currently experiencing some issues causing some users cannot log in.

We&#039;ll post an update shortly.  Sep 25, 21:02:15 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 25, 21:32:36 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:54:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident. 

Our cloud service provider is currently experiencing some issues causing some users cannot log in.

We&#039;ll post an update shortly. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:02:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:32:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 25 Sep 2023 20:54:15 +0000</pubDate>
  <link>https://status.whippy.co/incident/clmzd9l473379bkndnzknlsm1</link>
  <guid>https://status.whippy.co/incident/clmzd9l473379bkndnzknlsm1</guid>
</item>

<item>
  <title>Third Party Phone Carrier Issue</title>
  <description>
    Type: Incident
    Duration: 37 minutes

    Affected Components: Messaging
    Aug 31, 16:13:15 GMT+0 - Resolved - This incident has been resolved. Aug 31, 15:36:14 GMT+0 - Investigating - One of our Third Party phone carrier partners is currently investigating an issue with Failing SMS Messages. This will only effect a subset of customers. If you see a failing message in red, please note we are actively monitoring this with out the carrier and will post an update shortly. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 37 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:13:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:36:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One of our Third Party phone carrier partners is currently investigating an issue with Failing SMS Messages. This will only effect a subset of customers. If you see a failing message in red, please note we are actively monitoring this with out the carrier and will post an update shortly..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 31 Aug 2023 15:36:14 +0000</pubDate>
  <link>https://status.whippy.co/incident/cllzbwbyj9820bdoi5x7him7c</link>
  <guid>https://status.whippy.co/incident/cllzbwbyj9820bdoi5x7him7c</guid>
</item>

<item>
  <title>Slow Loading</title>
  <description>
    Type: Incident
    Duration: 3 hours and 5 minutes

    Affected Components: Campaigns, Webchat, Web Application - Dashboard, Messaging, Automations, Reviews
    May 8, 19:30:16 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 8, 21:01:16 GMT+0 - Resolved - This incident has been resolved. May 8, 18:16:56 GMT+0 - Investigating - We are currently investigating this incident. May 8, 18:12:54 GMT+0 - Monitoring - Our cloud producer has made a fix to a proxy server that was causing slow loading in some revisions and are currently monitoring the result. May 8, 17:56:01 GMT+0 - Investigating - We are currently investigating this incident where the application is running slow in some regions.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:01:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:16:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:12:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Our cloud producer has made a fix to a proxy server that was causing slow loading in some revisions and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:56:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident where the application is running slow in some regions. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 8 May 2023 17:56:01 +0000</pubDate>
  <link>https://status.whippy.co/incident/clhf594jk7543uemzgzi6yhxg</link>
  <guid>https://status.whippy.co/incident/clhf594jk7543uemzgzi6yhxg</guid>
</item>

<item>
  <title>Degraded API Performance </title>
  <description>
    Type: Incident
    

    Affected Components: Web Application - Dashboard
    Apr 20, 20:17:55 GMT+0 - Resolved - Our cloud provider is currently experiencing a Networking issue in some regions causing data to load slowly in Whippy. 

We are currently investigating this incident. We will post an update here shortly.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:17:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Our cloud provider is currently experiencing a Networking issue in some regions causing data to load slowly in Whippy. 

We are currently investigating this incident. We will post an update here shortly. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 20 Apr 2023 20:17:55 +0000</pubDate>
  <link>https://status.whippy.co/incident/clgpke9z21019023kjohs1d4phg0</link>
  <guid>https://status.whippy.co/incident/clgpke9z21019023kjohs1d4phg0</guid>
</item>

<item>
  <title>Scheduled Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Web Application - Dashboard, Messaging, Webchat, Campaigns, Reviews, Automations
    Dec 18, 08:00:00 GMT+0 - Identified - Tomorrow, Sunday 18th of December 2022 between 03:00 a.m EST (00:00 PST) an 04:000 am EST (01:00 PCT) Whippy will perform scheduled maintenance, as part of a routine improvements to our production systems.

This means that you will not be able to login to Whippy during this hour. Any messages received during this time will be available once scheduled maintenance has completed. Dec 18, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 18, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Tomorrow, Sunday 18th of December 2022 between 03:00 a.m EST (00:00 PST) an 04:000 am EST (01:00 PCT) Whippy will perform scheduled maintenance, as part of a routine improvements to our production systems.

This means that you will not be able to login to Whippy during this hour. Any messages received during this time will be available once scheduled maintenance has completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 18 Dec 2022 08:00:00 +0000</pubDate>
  <link>https://status.whippy.co/maintenance/clbs2p15b12776hon7wnx2ma79</link>
  <guid>https://status.whippy.co/maintenance/clbs2p15b12776hon7wnx2ma79</guid>
</item>

  </channel>
  </rss>