<?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>SavvyCal Status - Incident history</title>
    <link>https://savvycal.instatus.com</link>
    <description>SavvyCal</description>
    <pubDate>Thu, 13 Nov 2025 19:05:35 +0000</pubDate>
    
<item>
  <title>App is currently experiencing an outage</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: App
    Nov 13, 19:32:52 GMT+0 - Resolved - This incident has been resolved. Nov 13, 19:26:11 GMT+0 - Monitoring - Connectivity with our database provider is returning to normal. We are continuing to monitor. Nov 13, 19:05:35 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>19:32:52</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>19:26:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  Connectivity with our database provider is returning to normal. We are continuing to monitor..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>19:05:35</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 13 Nov 2025 19:05:35 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/cmhxsu9vr07pl1302rx3ekgg7</link>
  <guid>https://savvycal.instatus.com/incident/cmhxsu9vr07pl1302rx3ekgg7</guid>
</item>

<item>
  <title>App is unavailable</title>
  <description>
    Type: Incident
    Duration: 1 hour and 51 minutes

    Affected Components: App
    Feb 16, 14:15:59 GMT+0 - Resolved - This incident has been resolved. Feb 16, 13:53:04 GMT+0 - Monitoring - The app is now resolving, but we are continuing to monitor. Feb 16, 12:24:35 GMT+0 - Identified - Our hosting provider is experiencing a major outage. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 51 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>14:15:59</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>13:53:04</var> GMT+0</small><br><strong>Monitoring</strong> -
  The app is now resolving, but we are continuing to monitor..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>12:24:35</var> GMT+0</small><br><strong>Identified</strong> -
  Our hosting provider is experiencing a major outage..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 16 Feb 2025 12:24:35 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/cm77lmlpk008qkcyyvafdw878</link>
  <guid>https://savvycal.instatus.com/incident/cm77lmlpk008qkcyyvafdw878</guid>
</item>

<item>
  <title>Massive spam attack</title>
  <description>
    Type: Incident
    Duration: 4 hours and 18 minutes

    Affected Components: App
    Nov 5, 19:56:43 GMT+0 - Resolved - This incident has been resolved. Nov 5, 18:52:18 GMT+0 - Monitoring - Out of the abundance of caution, user registration is still disabled while we test out our abuse prevention mechanisms. Nov 5, 16:41:14 GMT+0 - Identified - Between the hours of \~4:40am and 9:30am (Central Time), emails that SavvyCal attempted to send to users were paused by our email sending provider. We are now processing the backlog of these delayed emails. Nov 5, 15:38:14 GMT+0 - Investigating - SavvyCal is experiencing a distributed attack from spammers seeking to abuse our email sending infrastructure. We are currently working to mitigate the attack and send emails that have been delayed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>19:56:43</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>18:52:18</var> GMT+0</small><br><strong>Monitoring</strong> -
  Out of the abundance of caution, user registration is still disabled while we test out our abuse prevention mechanisms..</p>
<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>16:41:14</var> GMT+0</small><br><strong>Identified</strong> -
  Between the hours of \~4:40am and 9:30am (Central Time), emails that SavvyCal attempted to send to users were paused by our email sending provider. We are now processing the backlog of these delayed emails..</p>
<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>15:38:14</var> GMT+0</small><br><strong>Investigating</strong> -
  SavvyCal is experiencing a distributed attack from spammers seeking to abuse our email sending infrastructure. We are currently working to mitigate the attack and send emails that have been delayed..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 5 Nov 2024 15:38:14 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/cm34m6w02001i48x4hc8fp7m7</link>
  <guid>https://savvycal.instatus.com/incident/cm34m6w02001i48x4hc8fp7m7</guid>
</item>

<item>
  <title>Network outage</title>
  <description>
    Type: Incident
    Duration: 49 minutes

    Affected Components: App
    Sep 1, 20:42:46 GMT+0 - Resolved - This incident has been resolved. Sep 1, 20:22:03 GMT+0 - Monitoring - Our hosting provider has implemented a fix and are currently monitoring the result. Sep 1, 19:54:09 GMT+0 - Identified - Our hosting provider is reporting a network outage causing intermittent downtime for SavvyCal. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>20:42:46</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>20:22:03</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our hosting provider has implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>19:54:09</var> GMT+0</small><br><strong>Identified</strong> -
  Our hosting provider is reporting a network outage causing intermittent downtime for SavvyCal..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 1 Sep 2024 19:54:09 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/cm0jzs2se00273t6jawwrsla9</link>
  <guid>https://savvycal.instatus.com/incident/cm0jzs2se00273t6jawwrsla9</guid>
</item>

<item>
  <title>Networking issues</title>
  <description>
    Type: Incident
    Duration: 38 minutes

    Affected Components: App
    May 31, 17:57:48 GMT+0 - Resolved - This incident has been resolved. May 31, 17:48:49 GMT+0 - Monitoring - Our hosting provider has indicated a fix is now in place and full connectivity has been restored. We are continuing to monitor. May 31, 17:20:00 GMT+0 - Identified - Our hosting provider is reporting intermittent networking issues across their platform, related to firewall configuration. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 31</var>, <var data-var='time'>17:57:48</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 31</var>, <var data-var='time'>17:48:49</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our hosting provider has indicated a fix is now in place and full connectivity has been restored. We are continuing to monitor..</p>
<p><small>May <var data-var='date'> 31</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Identified</strong> -
  Our hosting provider is reporting intermittent networking issues across their platform, related to firewall configuration..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 31 May 2024 17:20:00 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/clwuz0vni27855bhn0ubhw58jg</link>
  <guid>https://savvycal.instatus.com/incident/clwuz0vni27855bhn0ubhw58jg</guid>
</item>

<item>
  <title>SquadCast API is down</title>
  <description>
    Type: Incident
    Duration: 5 hours and 6 minutes

    Affected Components: SquadCast
    Feb 8, 04:24:32 GMT+0 - Resolved - This incident has been resolved. Feb 7, 23:18:04 GMT+0 - Identified - We&#039;ve confirmed with the SquadCast team their API is currently experiencing an outage. Unfortunately, customers with SquadCast connected to their SavvyCal account may have experienced a flood of sessions getting created in their SquadCast account, due to the retry logic on our end. Until we confirm a fix from the SquadCast team, we&#039;ve fully disabled the integration on our side. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>04:24:32</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>23:18:04</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;ve confirmed with the SquadCast team their API is currently experiencing an outage. Unfortunately, customers with SquadCast connected to their SavvyCal account may have experienced a flood of sessions getting created in their SquadCast account, due to the retry logic on our end. Until we confirm a fix from the SquadCast team, we&#039;ve fully disabled the integration on our side..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 7 Feb 2024 23:18:04 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/clsceuj4342814bmmy3jv9xvq5</link>
  <guid>https://savvycal.instatus.com/incident/clsceuj4342814bmmy3jv9xvq5</guid>
</item>

<item>
  <title>Errors communicating with the Google Calendar API</title>
  <description>
    Type: Incident
    Duration: 2 hours and 33 minutes

    Affected Components: Google Calendar
    Sep 21, 17:27:06 GMT+0 - Resolved - This incident has been resolved. Sep 21, 16:15:51 GMT+0 - Monitoring - Error levels appear to have returned to normal levels. We will continue monitoring. Sep 21, 14:54:22 GMT+0 - Investigating - We are currently investigating this incident. 

Google is reporting a Service Disruption that we are tracking here: https://www.google.com/appsstatus/dashboard/incidents/7uJZ5F1Uy4n1n74iMacQ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>17:27:06</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>16:15:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  Error levels appear to have returned to normal levels. We will continue monitoring..</p>
<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>14:54:22</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. 

Google is reporting a Service Disruption that we are tracking here: https://www.google.com/appsstatus/dashboard/incidents/7uJZ5F1Uy4n1n74iMacQ.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 21 Sep 2023 14:54:22 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/clmtand0z170158b8n396f7jwxo</link>
  <guid>https://savvycal.instatus.com/incident/clmtand0z170158b8n396f7jwxo</guid>
</item>

<item>
  <title>Errors fetching availability from Microsoft 365</title>
  <description>
    Type: Incident
    Duration: 3 hours and 8 minutes

    Affected Components: Microsoft 365
    Jun 5, 22:49:11 GMT+0 - Resolved - The API seem to have returned to normal behavior. We&#039;ll keep an eye on monitoring and open a new incident if errors and timeouts spike again. Jun 5, 20:22:41 GMT+0 - Monitoring - Microsoft provided the following update:

&gt; We&#039;ve determined that impact associated with MO571683 and EX571516 has reoccurred and are investigating the cause. We&#039;ll be providing updates related to this event under MO572252 in the admin center.

https://twitter.com/MSFT365Status/status/1665814515198435329 Jun 5, 19:41:10 GMT+0 - Monitoring - The Microsoft 365 API experienced an unreported outage spike earlier this morning: https://downdetector.com/status/microsoft-365/

We are continuing to observe intermittent timeouts when attempting to query calendars for event data (and perform other operations). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>22:49:11</var> GMT+0</small><br><strong>Resolved</strong> -
  The API seem to have returned to normal behavior. We&#039;ll keep an eye on monitoring and open a new incident if errors and timeouts spike again..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>20:22:41</var> GMT+0</small><br><strong>Monitoring</strong> -
  Microsoft provided the following update:

&gt; We&#039;ve determined that impact associated with MO571683 and EX571516 has reoccurred and are investigating the cause. We&#039;ll be providing updates related to this event under MO572252 in the admin center.

https://twitter.com/MSFT365Status/status/1665814515198435329.</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>19:41:10</var> GMT+0</small><br><strong>Monitoring</strong> -
  The Microsoft 365 API experienced an unreported outage spike earlier this morning: https://downdetector.com/status/microsoft-365/

We are continuing to observe intermittent timeouts when attempting to query calendars for event data (and perform other operations)..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 5 Jun 2023 19:41:10 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/clij9c6p31289201awn879vuobxb</link>
  <guid>https://savvycal.instatus.com/incident/clij9c6p31289201awn879vuobxb</guid>
</item>

<item>
  <title>Database maintenance</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: App
    Jul 3, 01:15:00 GMT+0 - Completed - Maintenance has completed successfully Jul 3, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 3, 01:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>01:15:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 3 Jul 2022 01:00:00 +0000</pubDate>
  <link>https://savvycal.instatus.com/maintenance/cl53zotj83492hlmz11xjr6eg</link>
  <guid>https://savvycal.instatus.com/maintenance/cl53zotj83492hlmz11xjr6eg</guid>
</item>

<item>
  <title>App is unavailable</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: App
    Feb 24, 17:25:04 GMT+0 - Resolved - The issue is resolved! Feb 24, 17:12:32 GMT+0 - Monitoring - Requests appear to be flowing again. We are monitoring. Feb 24, 17:00:20 GMT+0 - Investigating - Heroku has confirmed there is an ongoing incident: [https://status.heroku.com/incidents/2402](https://status.heroku.com/incidents/2402)

We are following this closely. Feb 24, 16:40:23 GMT+0 - Investigating - We are currently investigating this incident. This appears to be caused by an outage with our hosting provider, Heroku. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>17:25:04</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue is resolved!.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>17:12:32</var> GMT+0</small><br><strong>Monitoring</strong> -
  Requests appear to be flowing again. We are monitoring..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>17:00:20</var> GMT+0</small><br><strong>Investigating</strong> -
  Heroku has confirmed there is an ongoing incident: [https://status.heroku.com/incidents/2402](https://status.heroku.com/incidents/2402)

We are following this closely..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:40:23</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. This appears to be caused by an outage with our hosting provider, Heroku..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Feb 2022 16:40:23 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/cl017oqim354421gyoiwlhoitn4</link>
  <guid>https://savvycal.instatus.com/incident/cl017oqim354421gyoiwlhoitn4</guid>
</item>

<item>
  <title>App is offline</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: App
    Sep 1, 01:53:09 GMT+0 - Resolved - We just resolved the issue! Sep 1, 01:49:56 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>01:53:09</var> GMT+0</small><br><strong>Resolved</strong> -
  We just resolved the issue!.</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>01:49:56</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 1 Sep 2021 01:49:56 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/ckt0ue3ay368547vndeboklofq</link>
  <guid>https://savvycal.instatus.com/incident/ckt0ue3ay368547vndeboklofq</guid>
</item>

<item>
  <title>Delays with notifications and calendar event creation</title>
  <description>
    Type: Incident
    Duration: 50 minutes

    Affected Components: App
    Jul 7, 19:25:00 GMT+0 - Resolved - This issue is resolved, but we will continue to monitor. Jul 7, 18:53:11 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Jul 7, 18:35:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>19:25:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This issue is resolved, but we will continue to monitor..</p>
<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>18:53:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>18:35:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 7 Jul 2021 18:35:00 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/ckqttn7mk322065a7ojz1oqpbl0</link>
  <guid>https://savvycal.instatus.com/incident/ckqttn7mk322065a7ojz1oqpbl0</guid>
</item>

<item>
  <title>Google rate limiting issues</title>
  <description>
    Type: Incident
    Duration: 4 days, 21 hours and 49 minutes

    Affected Components: App
    Mar 12, 16:29:41 GMT+0 - Resolved - This issue appears to be resolved now. We will continue monitoring the system closely! Mar 12, 16:01:11 GMT+0 - Monitoring - API errors have subsided. Our background processing for event changes is still disabled until we can be confident it will not trigger more errors. Mar 12, 14:50:38 GMT+0 - Investigating - To help reduce our volume of API requests, we&#039;ve temporarily disabled consuming webhook notifications of changes to calendar events. This means you move or cancel a SavvyCal event on your Google Calendar, that change may not propagate back to SavvyCal. Mar 12, 14:31:53 GMT+0 - Investigating - We are currently receiving intermittent rate limiting errors from Google when attempting to access their API. This may affect the accuracy of availability displayed on booking pages, calendar overlays, and the creation of calendar events. We are working to resolved this problem as quickly as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 21 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>16:29:41</var> GMT+0</small><br><strong>Resolved</strong> -
  This issue appears to be resolved now. We will continue monitoring the system closely!.</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>16:01:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  API errors have subsided. Our background processing for event changes is still disabled until we can be confident it will not trigger more errors..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>14:50:38</var> GMT+0</small><br><strong>Investigating</strong> -
  To help reduce our volume of API requests, we&#039;ve temporarily disabled consuming webhook notifications of changes to calendar events. This means you move or cancel a SavvyCal event on your Google Calendar, that change may not propagate back to SavvyCal..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>14:31:53</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently receiving intermittent rate limiting errors from Google when attempting to access their API. This may affect the accuracy of availability displayed on booking pages, calendar overlays, and the creation of calendar events. We are working to resolved this problem as quickly as possible..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 12 Mar 2021 14:31:53 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/ckm6ekbw1958567y4n1ddjec2vz</link>
  <guid>https://savvycal.instatus.com/incident/ckm6ekbw1958567y4n1ddjec2vz</guid>
</item>

<item>
  <title>DNS Resolution Issues</title>
  <description>
    Type: Incident
    Duration: 3 days, 20 hours and 40 minutes

    Affected Components: App
    Mar 2, 21:15:38 GMT+0 - Resolved - This issue is now resolved. Mar 2, 20:30:04 GMT+0 - Monitoring - DNSimple has resolved the issue and is monitoring to ensure they have addressed all resolution issues. Mar 2, 19:42:58 GMT+0 - Identified - Our DNS provider (DNSimple) is reporting resolution failures in some regions, which is impacting the availability of SavvyCal for some users. We are monitoring the situation closely.

https://dnsimple.statuspage.io/ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 20 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>21:15:38</var> GMT+0</small><br><strong>Resolved</strong> -
  This issue is now resolved..</p>
<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>20:30:04</var> GMT+0</small><br><strong>Monitoring</strong> -
  DNSimple has resolved the issue and is monitoring to ensure they have addressed all resolution issues..</p>
<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>19:42:58</var> GMT+0</small><br><strong>Identified</strong> -
  Our DNS provider (DNSimple) is reporting resolution failures in some regions, which is impacting the availability of SavvyCal for some users. We are monitoring the situation closely.

https://dnsimple.statuspage.io/.</p>
]]>
  </content:encoded>
  <pubDate>Tue, 2 Mar 2021 19:42:58 +0000</pubDate>
  <link>https://savvycal.instatus.com/incident/cklsf92c1492344wfn802svr6uk</link>
  <guid>https://savvycal.instatus.com/incident/cklsf92c1492344wfn802svr6uk</guid>
</item>

<item>
  <title>Database maintenance</title>
  <description>
    Type: Maintenance
    

    Affected Components: App
    Dec 28, 01:00:00 GMT+0 - Identified - Maintenance is now in progress. Dec 28, 01:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Dec 28, 01:00:00 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
<p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 28 Dec 2020 01:00:00 +0000</pubDate>
  <link>https://savvycal.instatus.com/maintenance/ckizb1xud6m3h0787i220agh8</link>
  <guid>https://savvycal.instatus.com/maintenance/ckizb1xud6m3h0787i220agh8</guid>
</item>

  </channel>
  </rss>