<?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>Tue, 18 Nov 2025 11:30:00 +0000</pubDate>
    
<item>
  <title>Web interfaces inaccessible</title>
  <description>
    Type: Incident
    Duration: 3 hours and 12 minutes

    Affected Components: Web interace, Customer portals
    Nov 18, 13:00:00 GMT+0 - Identified - Issues have continued after a short period of functionality. 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, 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, 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; Nov 18, 12:21:00 GMT+0 - Resolved - This incident has been resolved. 
  </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>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Issues have continued after a short period of functionality..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:26:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:42:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:21:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 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, 07:00:00 GMT+0 - Investigating - Background jobs are failing to execute in a timely manner. Oct 24, 23:06:55 GMT+0 - Monitoring - The backlog of queued background messages is currently recovering, and should catch up shortly. 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. 
  </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>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Background jobs are failing to execute in a timely manner..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:06:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The backlog of queued background messages is currently recovering, and should catch up shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:11:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  All background jobs have been processed. We are working on improving monitoring &amp; alerting around background jobs to ensure this does not happen again..&lt;/p&gt;
]]>
  </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>Automatic Scheduling</title>
  <description>
    Type: Incident
    Duration: 12 minutes

    Affected Components: Customer portals, Web interace, API
    Jun 1, 20:45:00 GMT+0 - Investigating - We&#039;re aware of an issue impacting automatic scheduling, and working on a fix. 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;re aware of an issue impacting automatic scheduling, and working on a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:57:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:49:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:19:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:07:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
]]>
  </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 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. 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 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, 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. 
  </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>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:18:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:50:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:53:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:56:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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, 01:51:00 GMT+0 - Investigating - HTTPS traffic towards our API, web interface, and customer portals is currently not being served. 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, 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. 
  </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>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:51:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  HTTPS traffic towards our API, web interface, and customer portals is currently not being served..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:55:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:25:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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>PDF generation errors</title>
  <description>
    Type: Incident
    Duration: 5 minutes

    Affected Components: Customer portals, API, Web interace
    Mar 20, 14:38:00 GMT+0 - Resolved - This incident has been resolved.

This impacted anyone with a logo configured in their company&#039;s account which is included on the PDFs. The cause of this issue was due to recent changes to our infrastructure security configuration to prevent malicious bots causing impact on services was preventing our PDF generation system from loading logo images to include on PDFs.  Mar 20, 14:33:00 GMT+0 - Investigating - PDF generation for quotes, invoices and forms are currently failing. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.

This impacted anyone with a logo configured in their company&#039;s account which is included on the PDFs. The cause of this issue was due to recent changes to our infrastructure security configuration to prevent malicious bots causing impact on services was preventing our PDF generation system from loading logo images to include on PDFs. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:33:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  PDF generation for quotes, invoices and forms are currently failing..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 20 Mar 2025 14:33:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cm8hgpbur000u13hmysyohq72</link>
  <guid>https://jobstaq.instatus.com/incident/cm8hgpbur000u13hmysyohq72</guid>
</item>

<item>
  <title>File storage offline</title>
  <description>
    Type: Incident
    Duration: 1 hour and 16 minutes

    Affected Components: Customer portals, API, Web interace
    Mar 12, 18:58:00 GMT+0 - Identified - Our hosting provider&#039;s storage system is currently experiencing an outage, causing issues for any JobStaq requests that need to read or write from stored files. We are monitoring for status updates to determine our best course of action.  Mar 12, 20:14:21 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 16 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our hosting provider&#039;s storage system is currently experiencing an outage, causing issues for any JobStaq requests that need to read or write from stored files. We are monitoring for status updates to determine our best course of action. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:14:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Mar 2025 18:58:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cm86b2w41002rrlefffi2mqhu</link>
  <guid>https://jobstaq.instatus.com/incident/cm86b2w41002rrlefffi2mqhu</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>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:51:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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>System outage</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: Customer portals, API, Web interace
    Oct 14, 11:15:56 GMT+0 - Monitoring - The database has been brought back online, we&#039;re continuing to investigate what happened to ensure the issue is resolved and prevent this occurring again. Oct 14, 10:51:00 GMT+0 - Investigating - We&#039;ve run into an issue with our database. This is being actively investigated, and updates will be provided as we know more about the issue. Oct 14, 11:30:19 GMT+0 - Resolved - The cause of this outage has been identified, and is due to database instances having crashed due to insufficient resources.

JobStaq is served from a database setup consisting of 3 servers, and the system continues to operate without issues if one server crashes. At 2024-10-14T10:50:35.559404Z, server 3 of our UK cluster crashed due to insufficient resources, and at 2024-10-14T10:50:35.566518Z this was identified, with server 2 taking over responsibility of the primary (leader) database server. However, shortly after at 2024-10-14T10:51:51.217720Z, this server went offline before server 3 was able to recover - again due to running out of resources, which caused the database to be in a state where manual input is required to bring the system back online.

We&#039;ll be performing upgrades on all database servers this evening to increase the resources avaialble, to ensure this doesn&#039;t occur again. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:15:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The database has been brought back online, we&#039;re continuing to investigate what happened to ensure the issue is resolved and prevent this occurring again..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:51:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;ve run into an issue with our database. This is being actively investigated, and updates will be provided as we know more about the issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The cause of this outage has been identified, and is due to database instances having crashed due to insufficient resources.

JobStaq is served from a database setup consisting of 3 servers, and the system continues to operate without issues if one server crashes. At 2024-10-14T10:50:35.559404Z, server 3 of our UK cluster crashed due to insufficient resources, and at 2024-10-14T10:50:35.566518Z this was identified, with server 2 taking over responsibility of the primary (leader) database server. However, shortly after at 2024-10-14T10:51:51.217720Z, this server went offline before server 3 was able to recover - again due to running out of resources, which caused the database to be in a state where manual input is required to bring the system back online.

We&#039;ll be performing upgrades on all database servers this evening to increase the resources avaialble, to ensure this doesn&#039;t occur again..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 14 Oct 2024 10:51:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/cm28wol8a001bwels7su3jzzh</link>
  <guid>https://jobstaq.instatus.com/incident/cm28wol8a001bwels7su3jzzh</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 3, 00:00:01 GMT+0 - Identified - Maintenance is now in progress 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: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>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:11:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:22:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:27:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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>

<item>
  <title>Server offline</title>
  <description>
    Type: Incident
    Duration: 1 hour and 36 minutes

    Affected Components: Web interace, API, Vehicle Tracking
    Feb 14, 16:00:00 GMT+0 - Resolved -  Feb 14, 14:24:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 14, 14:51:00 GMT+0 - Monitoring -  Feb 14, 14:34:35 GMT+0 - Identified - Our cloud provider appears to be experiencing network issues. We are working with them to identify and resolve these issues as soon as possible.  Feb 14, 14:34:00 GMT+0 - Resolved - This incident has been resolved, and all services have returned to normal operation.  Feb 14, 14:38:00 GMT+0 - Identified - Issues appear to have re-appeared so we will continue monitoring the incident.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 36 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:24:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:51:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:34:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our cloud provider appears to be experiencing network issues. We are working with them to identify and resolve these issues as soon as possible. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:34:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved, and all services have returned to normal operation. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Issues appear to have re-appeared so we will continue monitoring the incident. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 14 Feb 2024 14:24:00 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/clslw39o915444baot3qq0uu5u</link>
  <guid>https://jobstaq.instatus.com/incident/clslw39o915444baot3qq0uu5u</guid>
</item>

<item>
  <title>Servers Offline</title>
  <description>
    Type: Incident
    Duration: 40 minutes

    Affected Components: Web interace, Vehicle Tracking, API
    Oct 13, 08:01:34 GMT+0 - Identified - Update from our hosting provider: https://twitter.com/olesovhcom/status/1448196879020433409

&gt; Following a human error during the reconfiguration of the network on our DC to VH (US-EST), we have a problem on the whole backbone. We are going to isolate the DC VH then fix the conf. Oct 13, 08:20:07 GMT+0 - Resolved - The datacentres of the provider which we use are now operating correctly again. Oct 13, 07:40:10 GMT+0 - Investigating - Our primary hosting provider is experiencing a global outage, resulting in JobStaq being offline.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:01:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Update from our hosting provider: https://twitter.com/olesovhcom/status/1448196879020433409

&gt; Following a human error during the reconfiguration of the network on our DC to VH (US-EST), we have a problem on the whole backbone. We are going to isolate the DC VH then fix the conf..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:20:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The datacentres of the provider which we use are now operating correctly again..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:40:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Our primary hosting provider is experiencing a global outage, resulting in JobStaq being offline. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 13 Oct 2021 07:40:10 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/ckup7f4mt120992gjo3t4lwkr38</link>
  <guid>https://jobstaq.instatus.com/incident/ckup7f4mt120992gjo3t4lwkr38</guid>
</item>

<item>
  <title>SMS Status Updates</title>
  <description>
    Type: Incident
    Duration: 4 days, 20 hours and 35 minutes

    Affected Components: SMS Sending
    Oct 6, 14:25:49 GMT+0 - Identified - Our SMS provider is no longering sending messages to our servers to notify us when SMSs have been delivered / received / failed.

We&#039;ve reached out to them with information on the problem and are waiting to hear back so that we can work with them to resolve this issue. Oct 11, 11:01:16 GMT+0 - Resolved -  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 20 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:25:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our SMS provider is no longering sending messages to our servers to notify us when SMSs have been delivered / received / failed.

We&#039;ve reached out to them with information on the problem and are waiting to hear back so that we can work with them to resolve this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:01:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 6 Oct 2021 14:25:49 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/ckufluco2713774mo9z4n8e7vt</link>
  <guid>https://jobstaq.instatus.com/incident/ckufluco2713774mo9z4n8e7vt</guid>
</item>

<item>
  <title>SMS Departure Triggers</title>
  <description>
    Type: Incident
    Duration: 4 days, 1 hour and 49 minutes

    Affected Components: API, Web interace
    Apr 8, 12:47:11 GMT+0 - Investigating - An issue has been reported which is causing triggers for event departures to not automatically send departure messages. Apr 8, 14:25:00 GMT+0 - Resolved -  Apr 8, 13:13:47 GMT+0 - Monitoring - We believe we have identified the cause of the issue, and are monitoring the systems to ensure the changes made have fixed the issue. Apr 8, 13:01:47 GMT+0 - Identified - Logs from the impacted server seem to reveal the cause of the problem, and we will now begin making the required changes to fix this. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 1 hour and 49 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:47:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  An issue has been reported which is causing triggers for event departures to not automatically send departure messages..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:13:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We believe we have identified the cause of the issue, and are monitoring the systems to ensure the changes made have fixed the issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:01:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Logs from the impacted server seem to reveal the cause of the problem, and we will now begin making the required changes to fix this..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 8 Apr 2021 12:47:11 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/ckn8vlmaz893670ckotdxgb3yje</link>
  <guid>https://jobstaq.instatus.com/incident/ckn8vlmaz893670ckotdxgb3yje</guid>
</item>

<item>
  <title>Web interace is inaccessible at the moment (automated)</title>
  <description>
    Type: Incident
    Duration: 10 hours and 3 minutes

    Affected Components: Web interace
    Mar 28, 15:44:43 GMT+0 - Resolved - Web interace is now operational! This update was created by an automated monitoring service. Mar 28, 15:34:40 GMT+0 - Identified - Web interace cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:44:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Web interace is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:34:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Web interace cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 28 Mar 2021 15:34:40 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/ckmtbpkap106476c6ndzxp9py6h</link>
  <guid>https://jobstaq.instatus.com/incident/ckmtbpkap106476c6ndzxp9py6h</guid>
</item>

<item>
  <title>Web interace is inaccessible at the moment (automated)</title>
  <description>
    Type: Incident
    Duration: 1 hour and 2 minutes

    Affected Components: Web interace
    Feb 3, 13:41:32 GMT+0 - Identified - Web interace cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 3, 13:42:34 GMT+0 - Resolved - Web interace is now operational! This update was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:41:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Web interace cannot be accessed at the moment. This incident was created by an automated monitoring service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:42:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Web interace is now operational! This update was created by an automated monitoring service..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Feb 2021 13:41:32 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/ckkphbx2f1843791lvfch2oj6pz</link>
  <guid>https://jobstaq.instatus.com/incident/ckkphbx2f1843791lvfch2oj6pz</guid>
</item>

<item>
  <title>Gas safe certificate PDF generation</title>
  <description>
    Type: Incident
    Duration: 2 days, 4 hours and 21 minutes

    Affected Components: Web interace, API
    Jan 15, 17:38:26 GMT+0 - Identified - This issue appears to be caused by some recent changes to how backend tasks are performed, and as a result, a large amount of required data was not loaded from the database. This is now being corrected so that certificates are genereated correctly. Jan 15, 16:48:22 GMT+0 - Investigating - We have noticed issues where company details and branding aren&#039;t being applied to gas safety certificates issued from the app.

This issue is under investigation, and details as to the cause will be provided here once the cause has been found. Jan 15, 17:40:43 GMT+0 - Resolved - This issue has now been resolved, and all affected certificates should now have been regenerated to include all of the required information in the correct styling.

If you notice any issues related to this incident, please contact our support team so we can help resolve these issues. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 4 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:38:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  This issue appears to be caused by some recent changes to how backend tasks are performed, and as a result, a large amount of required data was not loaded from the database. This is now being corrected so that certificates are genereated correctly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:48:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have noticed issues where company details and branding aren&#039;t being applied to gas safety certificates issued from the app.

This issue is under investigation, and details as to the cause will be provided here once the cause has been found..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:40:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This issue has now been resolved, and all affected certificates should now have been regenerated to include all of the required information in the correct styling.

If you notice any issues related to this incident, please contact our support team so we can help resolve these issues..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 15 Jan 2021 16:48:22 +0000</pubDate>
  <link>https://jobstaq.instatus.com/incident/ckjyiocdbslvt0742jakgrn3n</link>
  <guid>https://jobstaq.instatus.com/incident/ckjyiocdbslvt0742jakgrn3n</guid>
</item>

  </channel>
  </rss>