<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:savvycal.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://savvycal.instatus.com/history.atom"/>
  <title>SavvyCal Status - Incident history</title>
  <updated>2025-11-13T19:05:35.211+00:00</updated>
  <author>
    <name>SavvyCal</name>
  </author>
  
<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/cmhxsu9vr07pl1302rx3ekgg7</id>
  <published>2025-11-13T19:05:35.211+00:00</published>
  <updated>2025-11-13T19:32:52.560+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/cmhxsu9vr07pl1302rx3ekgg7"/>
  <title>App is currently experiencing an outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/cm77lmlpk008qkcyyvafdw878</id>
  <published>2025-02-16T12:24:35.643+00:00</published>
  <updated>2025-02-16T14:15:59.135+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/cm77lmlpk008qkcyyvafdw878"/>
  <title>App is unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 51 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/cm34m6w02001i48x4hc8fp7m7</id>
  <published>2024-11-05T15:38:14.611+00:00</published>
  <updated>2024-11-05T19:56:43.123+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/cm34m6w02001i48x4hc8fp7m7"/>
  <title>Massive spam attack</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/cm0jzs2se00273t6jawwrsla9</id>
  <published>2024-09-01T19:54:09.003+00:00</published>
  <updated>2024-09-01T20:42:46.567+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/cm0jzs2se00273t6jawwrsla9"/>
  <title>Network outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 49 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/clwuz0vni27855bhn0ubhw58jg</id>
  <published>2024-05-31T17:20:00.000+00:00</published>
  <updated>2024-05-31T17:57:48.568+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/clwuz0vni27855bhn0ubhw58jg"/>
  <title>Networking issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/clsceuj4342814bmmy3jv9xvq5</id>
  <published>2024-02-07T23:18:04.299+00:00</published>
  <updated>2024-02-08T04:24:32.921+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/clsceuj4342814bmmy3jv9xvq5"/>
  <title>SquadCast API is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> SquadCast</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/clmtand0z170158b8n396f7jwxo</id>
  <published>2023-09-21T14:54:22.432+00:00</published>
  <updated>2023-09-21T17:27:06.934+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/clmtand0z170158b8n396f7jwxo"/>
  <title>Errors communicating with the Google Calendar API</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> Google Calendar</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/clij9c6p31289201awn879vuobxb</id>
  <published>2023-06-05T19:41:10.413+00:00</published>
  <updated>2023-06-05T22:49:11.627+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/clij9c6p31289201awn879vuobxb"/>
  <title>Errors fetching availability from Microsoft 365</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> Microsoft 365</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Maintenance/cl53zotj83492hlmz11xjr6eg</id>
  <published>2022-07-03T01:00:00.000+00:00</published>
  <updated>2022-07-03T01:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/maintenance/cl53zotj83492hlmz11xjr6eg"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/cl017oqim354421gyoiwlhoitn4</id>
  <published>2022-02-24T16:40:23.379+00:00</published>
  <updated>2022-02-24T17:25:04.398+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/cl017oqim354421gyoiwlhoitn4"/>
  <title>App is unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/ckt0ue3ay368547vndeboklofq</id>
  <published>2021-09-01T01:49:56.054+00:00</published>
  <updated>2021-09-01T01:53:09.167+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/ckt0ue3ay368547vndeboklofq"/>
  <title>App is offline</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/ckqttn7mk322065a7ojz1oqpbl0</id>
  <published>2021-07-07T18:35:00.143+00:00</published>
  <updated>2021-07-07T19:25:00.964+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/ckqttn7mk322065a7ojz1oqpbl0"/>
  <title>Delays with notifications and calendar event creation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/ckm6ekbw1958567y4n1ddjec2vz</id>
  <published>2021-03-12T14:31:53.047+00:00</published>
  <updated>2021-03-12T16:29:41.208+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/ckm6ekbw1958567y4n1ddjec2vz"/>
  <title>Google rate limiting issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 21 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Incident/cklsf92c1492344wfn802svr6uk</id>
  <published>2021-03-02T19:42:58.952+00:00</published>
  <updated>2021-03-02T21:15:38.646+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/incident/cklsf92c1492344wfn802svr6uk"/>
  <title>DNS Resolution Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 20 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> App</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>
</entry>

<entry>
  <id>tag:savvycal.instatus.com,2005:Maintenance/ckizb1xud6m3h0787i220agh8</id>
  <published>2020-12-28T01:00:00.000+00:00</published>
  <updated>2020-12-28T01:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://savvycal.instatus.com/maintenance/ckizb1xud6m3h0787i220agh8"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> App</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>
</entry>

</feed>