<?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>JobStaq Status - Incident history</title>
    <link>https://jobstaq.instatus.com</link>
    <description>JobStaq</description>
    <pubDate>Fri, 13 Nov 2026 09:22:28 +0000</pubDate>
    
<item>
  <title>Disruptions due to Microsoft Outage</title>
  <description>
    Type: Incident
    Duration: 10 hours and 2 minutes

    Affected Components: Support system / Knowledgebase, API
    Nov 13, 19:24:19 GMT+0 - Resolved - This incident has been resolved. Nov 13, 12:07:35 GMT+0 - Monitoring - We&#039;re seeing recovery of receiving email, so support is no longer impacted by this. Nov 13, 09:22:28 GMT+0 - Identified - A large Microsoft outage is causing some disruptions to services:

* We use Microsoft as our mail provider for support, so delays are expected in responses to support emails until we&#039;re able to receive these
* Any custom forms using DOCX templates may fail to generate a PDF, as we rely on impacted Microsoft services for this functionality 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>19:24:19</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'>12:07:35</var> GMT+0</small><br><strong>Monitoring</strong> -
  We&#039;re seeing recovery of receiving email, so support is no longer impacted by this..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>09:22:28</var> GMT+0</small><br><strong>Identified</strong> -
  A large Microsoft outage is causing some disruptions to services:

* We use Microsoft as our mail provider for support, so delays are expected in responses to support emails until we&#039;re able to receive these
* Any custom forms using DOCX templates may fail to generate a PDF, as we rely on impacted Microsoft services for this functionality.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 13 Nov 2026 09:22:28 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmwerqb3q0dzr13mm1v6plm1z</link>
  <guid>https://jobstaq.instatus.com/incident/cmwerqb3q0dzr13mm1v6plm1z</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 25 minutes

    Affected Components: Web interace, API, Customer portals
    Nov 11, 13:37:08 GMT+0 - Resolved - The database is back online. We&#039;re now focused on investigating in more depth what led to this, and how to prevent this happening again. Nov 11, 13:36:31 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Nov 11, 13:30:32 GMT+0 - Identified - 2 of 3 servers forming the database cluster crashed, leading to a loss of quorum requiring manual intervention to fix. We&#039;re currently working to bring the database back online. Nov 11, 13:11:06 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>13:37:08</var> GMT+0</small><br><strong>Resolved</strong> -
  The database is back online. We&#039;re now focused on investigating in more depth what led to this, and how to prevent this happening again..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>13:36:31</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>13:30:32</var> GMT+0</small><br><strong>Identified</strong> -
  2 of 3 servers forming the database cluster crashed, leading to a loss of quorum requiring manual intervention to fix. We&#039;re currently working to bring the database back online..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>13:11:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 11 Nov 2026 13:11:06 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmwc50n02041c1squsq4781mc</link>
  <guid>https://jobstaq.instatus.com/incident/cmwc50n02041c1squsq4781mc</guid>
</item>

<item>
  <title>Database upgrades</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Web interace, API, Customer portals
    Nov 3, 23:47:52 GMT+0 - Completed - Maintenance has completed successfully. Nov 3, 23:39:39 GMT+0 - Identified - Changes are taking longer than expected to apply. We anticipate this will be completed within 30 minutes. Nov 3, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 3, 22:51:16 GMT+0 - Identified - JobStaq will be inaccessible for a short maintenance period while database upgrades are applied. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>23:47:52</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>23:39:39</var> GMT+0</small><br><strong>Identified</strong> -
  Changes are taking longer than expected to apply. We anticipate this will be completed within 30 minutes..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>22:51:16</var> GMT+0</small><br><strong>Identified</strong> -
  JobStaq will be inaccessible for a short maintenance period while database upgrades are applied..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 3 Nov 2026 23:00:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/maintenance/cmw1a7x2v02fk1bnmgmjncw4x</link>
  <guid>https://jobstaq.instatus.com/maintenance/cmw1a7x2v02fk1bnmgmjncw4x</guid>
</item>

<item>
  <title>Precautionary unavailability for security incident</title>
  <description>
    Type: Incident
    Duration: 11 hours and 59 minutes

    Affected Components: Web interace, API, Customer portals
    Oct 21, 14:58:38 GMT+0 - Resolved - The security patch has been applied to all servers, and the temporary access restrictions put in place have been lifted. Oct 21, 05:52:21 GMT+0 - Identified - Until the patch has been released and applied, we&#039;re restricting access to JobStaq to IP addresses which have been used in the last 14 days by employees of active JobStaq accounts, to prevent attackers targeting the internet as a whole from being able to target JobStaq. As a result, customer portals will remain unavailable at this time (unless customers share IPs with employees), and in the event an employee connects from a new IP address (eg. via a VPN), they may be unable to access JobStaq.

We&#039;ve applied all known configuration changes to address known exploits for the time being. There may continue to be disruption to some functionality, such as file uploads, as a result of these temporary changes until the full fix is available.

If you remain unable to access JobStaq, please contact support and provide a copy of the contents of the webpage at &lt;https://cloudflare.com/cdn-cgi/trace&gt;. We will be issuing compensation for any employees who are unable to use JobStaq during this incident.

The security release we are waiting on is scheduled to be auto-installed the moment it is available, after which we&#039;ll manually confirm it has applied correctly before reverting the temporary restrictions we enforced. We&#039;d like to apologise in advance for any disruptions this may cause, however, believe the approach we&#039;ve taken here to be the best path to balance both availability and security of our customers&#039; data. Oct 21, 03:00:00 GMT+0 - Investigating - A critical security vulnerability in the programming language used for parts of JobStaq has been announced, with a planned release for 14:00 UTC on 2026-10-21 (&lt;https://news-web.php.net/php.announce/509&gt;). Before the security upgrade became available, details of exploits surfaced online (&lt;https://x.com/J4ck3LSyN/status/2112703096443097263&gt;), however, no details are yet to be shared about how to patch this (&lt;https://phpc.social/@Girgias/117476477429221001&gt;).

Out of an abundance of caution, we&#039;ve taken public facing parts of JobStaq offline until we can reduce our attack surface. Background processing and automations (eg. automatic reminders &amp; triggers) will continue as usual, and the app will continue to function offline. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>14:58:38</var> GMT+0</small><br><strong>Resolved</strong> -
  The security patch has been applied to all servers, and the temporary access restrictions put in place have been lifted..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>05:52:21</var> GMT+0</small><br><strong>Identified</strong> -
  Until the patch has been released and applied, we&#039;re restricting access to JobStaq to IP addresses which have been used in the last 14 days by employees of active JobStaq accounts, to prevent attackers targeting the internet as a whole from being able to target JobStaq. As a result, customer portals will remain unavailable at this time (unless customers share IPs with employees), and in the event an employee connects from a new IP address (eg. via a VPN), they may be unable to access JobStaq.

We&#039;ve applied all known configuration changes to address known exploits for the time being. There may continue to be disruption to some functionality, such as file uploads, as a result of these temporary changes until the full fix is available.

If you remain unable to access JobStaq, please contact support and provide a copy of the contents of the webpage at &lt;https://cloudflare.com/cdn-cgi/trace&gt;. We will be issuing compensation for any employees who are unable to use JobStaq during this incident.

The security release we are waiting on is scheduled to be auto-installed the moment it is available, after which we&#039;ll manually confirm it has applied correctly before reverting the temporary restrictions we enforced. We&#039;d like to apologise in advance for any disruptions this may cause, however, believe the approach we&#039;ve taken here to be the best path to balance both availability and security of our customers&#039; data..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  A critical security vulnerability in the programming language used for parts of JobStaq has been announced, with a planned release for 14:00 UTC on 2026-10-21 (&lt;https://news-web.php.net/php.announce/509&gt;). Before the security upgrade became available, details of exploits surfaced online (&lt;https://x.com/J4ck3LSyN/status/2112703096443097263&gt;), however, no details are yet to be shared about how to patch this (&lt;https://phpc.social/@Girgias/117476477429221001&gt;).

Out of an abundance of caution, we&#039;ve taken public facing parts of JobStaq offline until we can reduce our attack surface. Background processing and automations (eg. automatic reminders &amp; triggers) will continue as usual, and the app will continue to function offline..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 21 Oct 2026 03:00:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmvhnitym04mu1ms8ikr03fq3</link>
  <guid>https://jobstaq.instatus.com/incident/cmvhnitym04mu1ms8ikr03fq3</guid>
</item>

<item>
  <title>Email status tracking issues</title>
  <description>
    Type: Incident
    Duration: 1 day, 7 hours and 1 minute

    Affected Components: Email Sending
    Oct 12, 12:31:00 GMT+0 - Resolved -  Oct 12, 12:00:00 GMT+0 - Identified - An update deployed over the weekend resulted in issues tracking the status of emails sent through one of our communication providers. All impacted emails will have shown up in a &quot;processing&quot; state despite having been sent. When we were alerted of this error, we attempted to re-deliver all emails which were believed to be stuck in the processing state, however later discovered that these in fact had already been sent out, and the issue was tracking related.

All emails are now being routed via the email provider which was not impacted by this issue. Some customers may have received duplicate copies of emails from the last 3 days in the last hour (1-2x). No further duplicate emails will be received, and we&#039;re working on a fix to ensure this does not happen again. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 7 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>12:31:00</var> GMT+0</small><br><strong>Resolved</strong> -
  .</p>
<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  An update deployed over the weekend resulted in issues tracking the status of emails sent through one of our communication providers. All impacted emails will have shown up in a &quot;processing&quot; state despite having been sent. When we were alerted of this error, we attempted to re-deliver all emails which were believed to be stuck in the processing state, however later discovered that these in fact had already been sent out, and the issue was tracking related.

All emails are now being routed via the email provider which was not impacted by this issue. Some customers may have received duplicate copies of emails from the last 3 days in the last hour (1-2x). No further duplicate emails will be received, and we&#039;re working on a fix to ensure this does not happen again..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 12 Oct 2026 12:00:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmv58b5br01nr1nqshg9vvx5r</link>
  <guid>https://jobstaq.instatus.com/incident/cmv58b5br01nr1nqshg9vvx5r</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Web interace, Customer portals, API
    Oct 10, 21:29:31 GMT+0 - Resolved - This downtime was caused by a reboot to apply configuration changes to the load balancer. Oct 10, 21:25:06 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>21:29:31</var> GMT+0</small><br><strong>Resolved</strong> -
  This downtime was caused by a reboot to apply configuration changes to the load balancer..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>21:25:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 10 Oct 2026 21:25:06 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmv2wknx1010s0ws76iv0nckg</link>
  <guid>https://jobstaq.instatus.com/incident/cmv2wknx1010s0ws76iv0nckg</guid>
</item>

<item>
  <title>Delayed background processing</title>
  <description>
    Type: Incident
    Duration: 11 minutes

    Affected Components: Mailchimp, Letter Sending, SMS Sending, Email Sending, Xero, QuickBooks, Stripe
    Sep 29, 10:47:04 GMT+0 - Resolved -  Sep 29, 10:36:14 GMT+0 - Identified - A bug resulted in a large number of tasks being added to the background processing queue, causing delays to the processing of tasks (eg. communication delivery, notifications, integration sync). We&#039;re currently removing these tasks from the queue as fast as possible to allow important tasks to resume. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>10:47:04</var> GMT+0</small><br><strong>Resolved</strong> -
  .</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>10:36:14</var> GMT+0</small><br><strong>Identified</strong> -
  A bug resulted in a large number of tasks being added to the background processing queue, causing delays to the processing of tasks (eg. communication delivery, notifications, integration sync). We&#039;re currently removing these tasks from the queue as fast as possible to allow important tasks to resume..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 29 Sep 2026 10:36:14 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmumjjueh042x1nobfz7fgej8</link>
  <guid>https://jobstaq.instatus.com/incident/cmumjjueh042x1nobfz7fgej8</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 13 minutes

    Affected Components: Web interace, API, Customer portals
    Aug 8, 13:18:38 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Aug 8, 13:05:51 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>13:18:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>13:05:51</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 8 Aug 2026 13:05:51 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmskdzykh00dq1arpievylbbl</link>
  <guid>https://jobstaq.instatus.com/incident/cmskdzykh00dq1arpievylbbl</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    Affected Components: Web interace, API, Customer portals
    Jun 9, 09:48:26 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Jun 9, 09:41:07 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>09:48:26</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>09:41:07</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 9 Jun 2026 09:41:07 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmq6g9jop047rqna7fx5vtdtd</link>
  <guid>https://jobstaq.instatus.com/incident/cmq6g9jop047rqna7fx5vtdtd</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Web interace, API, Customer portals
    May 3, 14:06:03 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. May 3, 14:01:53 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:06:03</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:01:53</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 3 May 2026 14:01:53 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmopuadtk057c7m2zp1tbt20z</link>
  <guid>https://jobstaq.instatus.com/incident/cmopuadtk057c7m2zp1tbt20z</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: Web interace, API, Customer portals
    Apr 13, 19:40:45 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Apr 13, 19:38:06 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </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>Apr <var data-var='date'> 13</var>, <var data-var='time'>19:40:45</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>19:38:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 13 Apr 2026 19:38:06 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmnxlhq6a058hez38zyz8cs7l</link>
  <guid>https://jobstaq.instatus.com/incident/cmnxlhq6a058hez38zyz8cs7l</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 22 minutes

    Affected Components: Web interace, API, Customer portals
    Apr 9, 15:17:44 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Apr 9, 14:56:08 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>15:17:44</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>14:56:08</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 9 Apr 2026 14:56:08 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmnrlnpib006urphbxyo07p7l</link>
  <guid>https://jobstaq.instatus.com/incident/cmnrlnpib006urphbxyo07p7l</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Web interace, API, Customer portals
    Mar 30, 19:35:29 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Mar 30, 19:25:53 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>19:35:29</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>19:25:53</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 30 Mar 2026 19:25:53 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmndkw2zt01mqar2u0m8twy80</link>
  <guid>https://jobstaq.instatus.com/incident/cmndkw2zt01mqar2u0m8twy80</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 5 minutes

    Affected Components: Web interace, API, Customer portals
    Feb 15, 11:40:31 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Feb 15, 11:35:07 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 15</var>, <var data-var='time'>11:40:31</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Feb <var data-var='date'> 15</var>, <var data-var='time'>11:35:07</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 15 Feb 2026 11:35:07 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmlno51c40rqbp2a9hafiyau6</link>
  <guid>https://jobstaq.instatus.com/incident/cmlno51c40rqbp2a9hafiyau6</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 13 minutes

    Affected Components: Web interace, API, Customer portals
    Jan 25, 20:43:45 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Jan 25, 20:30:51 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>20:43:45</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>20:30:51</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 25 Jan 2026 20:30:51 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmku7143x00kfeam82xidgf8q</link>
  <guid>https://jobstaq.instatus.com/incident/cmku7143x00kfeam82xidgf8q</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Web interace, API, Customer portals
    Jan 17, 20:20:25 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Jan 17, 20:14:06 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>20:20:25</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>20:14:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 17 Jan 2026 20:14:06 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmkiqwrkj054vvckgcr34zuix</link>
  <guid>https://jobstaq.instatus.com/incident/cmkiqwrkj054vvckgcr34zuix</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: Web interace, API, Customer portals
    Jan 7, 21:38:26 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Jan 7, 21:37:06 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>21:38:26</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>21:37:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 7 Jan 2026 21:37:06 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmk4jgzf002ysbhchapclgkrz</link>
  <guid>https://jobstaq.instatus.com/incident/cmk4jgzf002ysbhchapclgkrz</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Web interace, API, Customer portals
    Nov 29, 22:45:30 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Nov 29, 22:41:05 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>22:45:30</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>22:41:05</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 29 Nov 2025 22:41:05 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmikvl1ud07yrdviaxhtoaqyb</link>
  <guid>https://jobstaq.instatus.com/incident/cmikvl1ud07yrdviaxhtoaqyb</guid>
</item>

<item>
  <title>Web interfaces inaccessible</title>
  <description>
    Type: Incident
    Duration: 3 hours and 12 minutes

    Affected Components: Web interace, Customer portals
    Nov 18, 14:42:00 GMT+0 - Resolved - Cloudflare is reporting this incident is now resolved, and we expect that access to the web interface and customer portals should be back to normal now. We are continuing to monitor the situation, and work on post-incident remediation tasks to minimise the impact of a similar incident in future. Nov 18, 14:26:58 GMT+0 - Monitoring - We&#039;ve updated the error page being returned to users due to this incident to provide more details, and link to a temporary alternative interface we&#039;ve setup that does not rely on Cloudflare, at &lt;https://jobstaq-web-v2.netlify.app/&gt;

We are experiencing intermittent issues updating this status page, as the provider also relies on Cloudflare for some services, so updates may be delayed.

Work has begun to setup a fallback for the web interface when Cloudflare is offline, to reduce the impact of future outages of this kind, to essential functionality. Nov 18, 13:00:00 GMT+0 - Identified - Issues have continued after a short period of functionality. Nov 18, 12:21:00 GMT+0 - Resolved - This incident has been resolved. Nov 18, 11:30:00 GMT+0 - Investigating - Cloudflare, one of our hosting providers, is currently experiencing issues with their network, causing issues loading the JobStaq web interface and customer portals.

&lt;https://www.cloudflarestatus.com/&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:42:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Cloudflare is reporting this incident is now resolved, and we expect that access to the web interface and customer portals should be back to normal now. We are continuing to monitor the situation, and work on post-incident remediation tasks to minimise the impact of a similar incident in future..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:26:58</var> GMT+0</small><br><strong>Monitoring</strong> -
  We&#039;ve updated the error page being returned to users due to this incident to provide more details, and link to a temporary alternative interface we&#039;ve setup that does not rely on Cloudflare, at &lt;https://jobstaq-web-v2.netlify.app/&gt;

We are experiencing intermittent issues updating this status page, as the provider also relies on Cloudflare for some services, so updates may be delayed.

Work has begun to setup a fallback for the web interface when Cloudflare is offline, to reduce the impact of future outages of this kind, to essential functionality..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Issues have continued after a short period of functionality..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:21:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  Cloudflare, one of our hosting providers, is currently experiencing issues with their network, causing issues loading the JobStaq web interface and customer portals.

&lt;https://www.cloudflarestatus.com/&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 11:30:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmi4k4q5x008hr0kg4a9pr29k</link>
  <guid>https://jobstaq.instatus.com/incident/cmi4k4q5x008hr0kg4a9pr29k</guid>
</item>

<item>
  <title>Background processing issues</title>
  <description>
    Type: Incident
    Duration: 16 hours and 11 minutes

    Affected Components: Letter Sending, Web interace, API, Email Sending, SMS Sending
    Oct 24, 23:11:25 GMT+0 - Resolved - All background jobs have been processed. We are working on improving monitoring &amp; alerting around background jobs to ensure this does not happen again. Oct 24, 23:06:55 GMT+0 - Monitoring - The backlog of queued background messages is currently recovering, and should catch up shortly. Oct 24, 07:00:00 GMT+0 - Investigating - Background jobs are failing to execute in a timely manner. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>23:11:25</var> GMT+0</small><br><strong>Resolved</strong> -
  All background jobs have been processed. We are working on improving monitoring &amp; alerting around background jobs to ensure this does not happen again..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>23:06:55</var> GMT+0</small><br><strong>Monitoring</strong> -
  The backlog of queued background messages is currently recovering, and should catch up shortly..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  Background jobs are failing to execute in a timely manner..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 24 Oct 2025 07:00:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmh5fzxag07v2edxh99i5mni9</link>
  <guid>https://jobstaq.instatus.com/incident/cmh5fzxag07v2edxh99i5mni9</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: Customer portals, Web interace, API
    Sep 27, 19:37:37 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Sep 27, 19:37:06 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>19:37:37</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>19:37:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 27 Sep 2025 19:37:06 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmg2o9rkg03aq11p2wgjdcjbm</link>
  <guid>https://jobstaq.instatus.com/incident/cmg2o9rkg03aq11p2wgjdcjbm</guid>
</item>

<item>
  <title>System outage</title>
  <description>
    Type: Incident
    

    Affected Components: Customer portals, Web interace, API
    Jun 30, 21:39:30 GMT+0 - Resolved - Our automated monitoring has detected this outage is now resolved. Jun 30, 21:39:08 GMT+0 - Investigating - Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>21:39:30</var> GMT+0</small><br><strong>Resolved</strong> -
  Our automated monitoring has detected this outage is now resolved..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>21:39:08</var> GMT+0</small><br><strong>Investigating</strong> -
  Our automatic monitoring has detected a full outage affecting our API, web interface and customer portals. Our technical team have been notified and will investigate promptly and post updates here as appropriate.

Our mobile app will continue to function, and syncing will resume once this issue is resolved..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 30 Jun 2025 21:39:08 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmcjmfw1702d3129jgbjmctsh</link>
  <guid>https://jobstaq.instatus.com/incident/cmcjmfw1702d3129jgbjmctsh</guid>
</item>

<item>
  <title>Automatic Scheduling</title>
  <description>
    Type: Incident
    Duration: 12 minutes

    Affected Components: Customer portals, Web interace, API
    Jun 1, 20:57:00 GMT+0 - Resolved - This incident has been resolved.

During the release of a change intended to enhance resilience of our scheduling system and update our routing database (which previously had a single point of failure on one server), a configuration error was made which resulted in auto-scheduling functionality to become unavailable. This error has now been corrected, and as a result of the changes that were deployed, should be significantly less likely to occur again in the future. Jun 1, 20:45:00 GMT+0 - Investigating - We&#039;re aware of an issue impacting automatic scheduling, and working on a fix. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>20:57:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved.

During the release of a change intended to enhance resilience of our scheduling system and update our routing database (which previously had a single point of failure on one server), a configuration error was made which resulted in auto-scheduling functionality to become unavailable. This error has now been corrected, and as a result of the changes that were deployed, should be significantly less likely to occur again in the future..</p>
<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>20:45:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re aware of an issue impacting automatic scheduling, and working on a fix..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 1 Jun 2025 20:45:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmbe5ijdb005olh48ixqgsp8q</link>
  <guid>https://jobstaq.instatus.com/incident/cmbe5ijdb005olh48ixqgsp8q</guid>
</item>

<item>
  <title>Database Unavailable</title>
  <description>
    Type: Incident
    Duration: 42 minutes

    Affected Components: Web interace, API
    May 19, 09:49:27 GMT+0 - Resolved - This incident has been resolved. May 19, 09:19:00 GMT+0 - Monitoring - A majority of the servers forming our database cluster went offline, forcing the database into read-only mode, and bringing the site offline. The database cluster has now been restored to handle writes, and we&#039;re monitoring to ensure all servers in the database cluster are healthy. May 19, 09:07:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>09:49:27</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>09:19:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  A majority of the servers forming our database cluster went offline, forcing the database into read-only mode, and bringing the site offline. The database cluster has now been restored to handle writes, and we&#039;re monitoring to ensure all servers in the database cluster are healthy..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>09:07:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 19 May 2025 09:07:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cmauv9hqo0001kwn6yiy2qqxm</link>
  <guid>https://jobstaq.instatus.com/incident/cmauv9hqo0001kwn6yiy2qqxm</guid>
</item>

<item>
  <title>SMS Sender Ignored</title>
  <description>
    Type: Incident
    Duration: 23 hours and 39 minutes

    Affected Components: SMS Sending
    May 5, 17:56:51 GMT+0 - Resolved - An update is currently being released which fixes sender IDs for users who are using their mobile number as the sender.

We apologies for any issues this issue has caused. As a result of this incident, JobStaq is now much more fault tolerant to SMS provider issues, and we&#039;ve got several options to quickly switch to if any issues are identified going forwards. May 5, 13:53:54 GMT+0 - Identified - An update is currently rolling out to transition messages sent from alpha-numeric sender IDs to a new provider, which should be complete in the next few minutes.

Messages configured to be delivered with a mobile number a sender will continue to be sent from a pool of random numbers until a replacement provider has been identified. May 5, 10:50:39 GMT+0 - Identified - We&#039;ve identified an alternative messaging provider to support alphanumeric sender IDs, and will begin working to transition SMSs from these senders over to their platform. We&#039;re still figuring out the best path forwards for users who have the SMS sender as their mobile number. May 4, 18:18:08 GMT+0 - Investigating - Our SMS provider has made changes to their sending interface without any notification to us, which has resulted in all messages being sent from a shared pool of random UK mobile numbers, rather than the configured sender name or mobile number.

It appears this issue started on April 1st, 2025\. We&#039;re investigating the best steps forwards from here to get SMS messages back to being sent from the intended senders. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>17:56:51</var> GMT+0</small><br><strong>Resolved</strong> -
  An update is currently being released which fixes sender IDs for users who are using their mobile number as the sender.

We apologies for any issues this issue has caused. As a result of this incident, JobStaq is now much more fault tolerant to SMS provider issues, and we&#039;ve got several options to quickly switch to if any issues are identified going forwards..</p>
<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>13:53:54</var> GMT+0</small><br><strong>Identified</strong> -
  An update is currently rolling out to transition messages sent from alpha-numeric sender IDs to a new provider, which should be complete in the next few minutes.

Messages configured to be delivered with a mobile number a sender will continue to be sent from a pool of random numbers until a replacement provider has been identified..</p>
<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>10:50:39</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;ve identified an alternative messaging provider to support alphanumeric sender IDs, and will begin working to transition SMSs from these senders over to their platform. We&#039;re still figuring out the best path forwards for users who have the SMS sender as their mobile number..</p>
<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>18:18:08</var> GMT+0</small><br><strong>Investigating</strong> -
  Our SMS provider has made changes to their sending interface without any notification to us, which has resulted in all messages being sent from a shared pool of random UK mobile numbers, rather than the configured sender name or mobile number.

It appears this issue started on April 1st, 2025\. We&#039;re investigating the best steps forwards from here to get SMS messages back to being sent from the intended senders..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 4 May 2025 18:18:08 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cma9z5v7e000zz6wkwilzhkkk</link>
  <guid>https://jobstaq.instatus.com/incident/cma9z5v7e000zz6wkwilzhkkk</guid>
</item>

<item>
  <title>JobStaq offline</title>
  <description>
    Type: Incident
    Duration: 18 hours and 34 minutes

    Affected Components: Customer portals, Web interace, API
    May 1, 20:25:29 GMT+0 - Resolved - All systems are back to regular operations.

Root cause:

A scheduled automated task to apply the latest TLS security certificates to our load balancer began at 2:45AM. At 2:51AM, the changes were applied to the load balancer, however, failed to save correctly, which resulted in all HTTPS traffic failing to be served. Automatic alerts did not reach an engineer due to iOS sleep mode being incorrectly configured to silence these notifications, resulting in a delay to notice the issue.

On discovering the issue, traffic was immediately redirected away from the load balancer to a single backend server, to reduce user-facing impact of this issue. As of 8:55AM, all user requests were being served as usual. We encountered some delays in getting services fully restored, due to lacking error messaging from our infrastructure provider&#039;s interface. The load balancer HTTPS components were deleted and re-deployed from scratch, which remedied the issue. May 1, 07:55:26 GMT+0 - Identified - A temporary fix has been put in place to bring things online while we identify the root cause of the problem. At this stage, all user-facing impact should be resolved, although the affected components are under &quot;degraded performance&quot; as our automatic fault tolerance is no longer in effect, until the load balancer is healthy again. May 1, 01:51:00 GMT+0 - Investigating - HTTPS traffic towards our API, web interface, and customer portals is currently not being served. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>20:25:29</var> GMT+0</small><br><strong>Resolved</strong> -
  All systems are back to regular operations.

Root cause:

A scheduled automated task to apply the latest TLS security certificates to our load balancer began at 2:45AM. At 2:51AM, the changes were applied to the load balancer, however, failed to save correctly, which resulted in all HTTPS traffic failing to be served. Automatic alerts did not reach an engineer due to iOS sleep mode being incorrectly configured to silence these notifications, resulting in a delay to notice the issue.

On discovering the issue, traffic was immediately redirected away from the load balancer to a single backend server, to reduce user-facing impact of this issue. As of 8:55AM, all user requests were being served as usual. We encountered some delays in getting services fully restored, due to lacking error messaging from our infrastructure provider&#039;s interface. The load balancer HTTPS components were deleted and re-deployed from scratch, which remedied the issue..</p>
<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>07:55:26</var> GMT+0</small><br><strong>Identified</strong> -
  A temporary fix has been put in place to bring things online while we identify the root cause of the problem. At this stage, all user-facing impact should be resolved, although the affected components are under &quot;degraded performance&quot; as our automatic fault tolerance is no longer in effect, until the load balancer is healthy again..</p>
<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>01:51:00</var> GMT+0</small><br><strong>Investigating</strong> -
  HTTPS traffic towards our API, web interface, and customer portals is currently not being served..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 1 May 2025 01:51:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cma5208e00002e4je0w0c19y3</link>
  <guid>https://jobstaq.instatus.com/incident/cma5208e00002e4je0w0c19y3</guid>
</item>

<item>
  <title>Server upgrades</title>
  <description>
    Type: Maintenance
    Duration: 22 minutes

    Affected Components: Customer portals, API, Web interace
    Oct 14, 16:51:59 GMT+0 - Completed - Maintenance has completed successfully. Oct 14, 16:30:00 GMT+0 - Identified - In response to today&#039;s outage, we&#039;re performing maintenance on our servers this evening to increase resource allocations to avoid a repeat of the cause of today&#039;s issue. If all goes to plan, you shouldn&#039;t notice any major disruption to your usage of JobStaq. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>16:51:59</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  In response to today&#039;s outage, we&#039;re performing maintenance on our servers this evening to increase resource allocations to avoid a repeat of the cause of today&#039;s issue. If all goes to plan, you shouldn&#039;t notice any major disruption to your usage of JobStaq..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 14 Oct 2024 16:30:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/maintenance/cm2989bzf000ek1ori8vzcrpi</link>
  <guid>https://jobstaq.instatus.com/maintenance/cm2989bzf000ek1ori8vzcrpi</guid>
</item>

<item>
  <title>Infrastructure upgrades</title>
  <description>
    Type: Maintenance
    Duration: 1 day, 22 hours and 12 minutes

    Affected Components: Customer portals, Web interace, API
    Mar 4, 22:11:53 GMT+0 - Completed - Over the course of today, we&#039;ve gradually transitioned services over to the new cluster of servers, and as of writing, the old server has been turned off, soon to be decomissioned once we are confident there are no issues with the new setup. There were a couple of minor outages lasting a few minutes over the course of today - apologies for any inconvenience, though going forwards, the new setup should increase reliability and allow us to perform maintenance on systems without any noticable impact to users. Mar 3, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 3, 00:00:00 GMT+0 - Identified - In response to recent performance and reliability issues, we&#039;re making some large changes to our infrastructure to improve the speed and reliability of the software going forwards. During this maintenance window, access to the JobStaq web interface, customer portals, and API may be unavailable. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 22 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>22:11:53</var> GMT+0</small><br><strong>Completed</strong> -
  Over the course of today, we&#039;ve gradually transitioned services over to the new cluster of servers, and as of writing, the old server has been turned off, soon to be decomissioned once we are confident there are no issues with the new setup. There were a couple of minor outages lasting a few minutes over the course of today - apologies for any inconvenience, though going forwards, the new setup should increase reliability and allow us to perform maintenance on systems without any noticable impact to users..</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  In response to recent performance and reliability issues, we&#039;re making some large changes to our infrastructure to improve the speed and reliability of the software going forwards. During this maintenance window, access to the JobStaq web interface, customer portals, and API may be unavailable..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 3 Mar 2024 00:00:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/maintenance/clt9uwyjl114129b2lm0h07gjfw</link>
  <guid>https://jobstaq.instatus.com/maintenance/clt9uwyjl114129b2lm0h07gjfw</guid>
</item>

<item>
  <title>Database upgrades</title>
  <description>
    Type: Maintenance
    Duration: 55 minutes

    Affected Components: Web interace, API
    Feb 18, 16:22:23 GMT+0 - Completed - Everything is operating again, and the maintenance window has finished. Thanks for your patience, we&#039;ll continue to monitor things to make sure everything continues working as intended. Feb 18, 15:27:00 GMT+0 - Identified - We&#039;ve put the API and server into maintenance mode while we work on creating backups and migrating data over to the new database. Feb 18, 12:00:00 GMT+0 - Identified - We&#039;re making changes to our database infrastructure to increase resilience, in response to the brief outage experienced earlier this week. As a result, our API and web interface will be offline for a short period of time during this upgrade. The mobile apps will continue to work, though syncing will be unavailable until this upgrade has completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 55 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>16:22:23</var> GMT+0</small><br><strong>Completed</strong> -
  Everything is operating again, and the maintenance window has finished. Thanks for your patience, we&#039;ll continue to monitor things to make sure everything continues working as intended..</p>
<p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>15:27:00</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;ve put the API and server into maintenance mode while we work on creating backups and migrating data over to the new database..</p>
<p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re making changes to our database infrastructure to increase resilience, in response to the brief outage experienced earlier this week. As a result, our API and web interface will be offline for a short period of time during this upgrade. The mobile apps will continue to work, though syncing will be unavailable until this upgrade has completed..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 18 Feb 2024 12:00:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/maintenance/clsrel1xj513268balh96hkjdrr</link>
  <guid>https://jobstaq.instatus.com/maintenance/clsrel1xj513268balh96hkjdrr</guid>
</item>

  </channel>
  </rss>