tag:status.schedulehead.com,2005:/historyRoosted Status - Incident History2024-03-28T17:06:33-07:00Roostedtag:status.schedulehead.com,2005:Incident/98982972022-05-02T12:31:35-07:002022-05-02T12:39:04-07:00Cannot add or move workers' shifts<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>12:31</var> PDT</small><br><strong>Resolved</strong> - Today at approximately noon CDT, Schedulehead suffered from problems with adding or moving workers shifts. Workers themselves, as well as admins, were still able to login, view shifts, create time punches, pull reports, add new workers, and nearly all other Schedulehead functionality properly. The issue was resolved just after 2pm CDT. No data was lost during this interruption. Workers themselves would not have seen any problems.<br />Thank you for your patience. For more information please contact Stellar Support from inside your Schedulehead portal.</p>tag:status.schedulehead.com,2005:Incident/76264992021-07-28T09:13:12-07:002021-07-28T11:23:49-07:00Schedulehead Outage<p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>09:13</var> PDT</small><br><strong>Resolved</strong> - At approximately 11:04 CST, one of our primary cloud providers lost connectivity due to currently unknown issues in our New York City data center. This impacted Schedulehead web services worldwide, although the remainder of Schedulehead services continued to function. Schedulehead’s failover routine automatically began to restore affected services by transferring service to our San Francisco data center. This process took approximately 9 minutes.<br />We sincerely apologize for any inconvenience that this downtime caused you. Only web services were impacted, API and mobile app services remained functional. During Schedulehead’s testing, our failover routines occur instantly, and today it took longer than expected. We are investigating this so that we can provide our customers with uninterruptible service.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>09:04</var> PDT</small><br><strong>Identified</strong> - Current web services outage identified. Engineers are investigating.</p>tag:status.schedulehead.com,2005:Incident/44305262020-06-22T05:00:00-07:002020-06-22T05:42:35-07:00System outage<p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>05:00</var> PDT</small><br><strong>Resolved</strong> - Updates this morning in our NA datacenter encountered some problems that caused a system outage for the majority of users from 5am PST to 5:36PST. Services are 100% restored and functioning.</p>tag:status.schedulehead.com,2005:Incident/30689822019-10-04T13:25:25-07:002019-10-04T13:25:25-07:00Slow performance resolved<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>13:25</var> PDT</small><br><strong>Resolved</strong> - This incident has been fully resolved.<br /><br />Schedulehead did experience approximately 1 hour of slowed service in our North American service area.<br /><br />We have identified the cause of the issue, faulty equipment. The equipment was replaced, and normal service restored.<br /><br />All services are operating within normal parameters.</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>11:29</var> PDT</small><br><strong>Monitoring</strong> - We have identified the issue, corrected, and are monitoring.<br /><br />All Schedulehead services have returned to optimal performance.</p>tag:status.schedulehead.com,2005:Incident/30689742019-10-04T12:00:00-07:002019-10-04T11:28:37-07:00Slow performance<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>12:00</var> PDT</small><br><strong>Resolved</strong> - At 12:18 CST, we discovered that some of our services were experiencing a slow performance in our North America region.
<br />
<br />Schedulehead is functional, but performance may be impacted in your area.
<br />
<br />We are aware of the issue, and are working to resolve the problem.</p>tag:status.schedulehead.com,2005:Incident/29983172019-08-11T11:11:29-07:002019-09-14T10:22:52-07:00Texting Delayed to Singapore<p><small>Aug <var data-var='date'>11</var>, <var data-var='time'>11:11</var> PDT</small><br><strong>Resolved</strong> - Our provider has resolved the issue causing delayed texting to Singapore, and all messages that were previously delayed are now marked as delivered. Thank you for your patience.</p><p><small>Aug <var data-var='date'>11</var>, <var data-var='time'>10:45</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Aug <var data-var='date'>11</var>, <var data-var='time'>10:19</var> PDT</small><br><strong>Identified</strong> - Our primary SMS text provider is experiencing issues causing delayed text messages to Singapore. Messages sent to and received from Singapore carriers are experiencing approximately a 10 minute delay. Our provider is aware of and addressing the issue. We will update the status with more information as it becomes available.</p>