<?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>ParkIT Status - Incident history</title>
    <link>https://status.parkit.cloud</link>
    <description>ParkIT</description>
    <pubDate>Tue, 18 Aug 2026 11:00:00 +0000</pubDate>
    
<item>
  <title>Planned maintenance – Tuesday 18 August 2026</title>
  <description>
    Type: Maintenance
    Duration: 8 minutes

    Affected Components: Portal App, Booking Ingestion, Portal Services API, ParkIT Mobile, Self Service Kiosks, Self Service Lockers
    Aug 18, 11:08:24 GMT+0 - Completed - Maintenance has completed successfully. Any issues please email help@parkit.cloud. Thank you for your patience. Aug 18, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 18, 11:00:00 GMT+0 - Identified - Maintenance is now in progress. Aug 3, 12:34:31 GMT+0 - Identified - We’ll be carrying out essential platform maintenance on **Tuesday 18 August 2026**.

**Expected duration:** Up to 15 minutes.

During this time, ParkIT services will be temporarily unavailable and you’ll see a maintenance page instead of the application.

Please avoid starting new check-ins, check-outs or other time-sensitive tasks in the few minutes before maintenance begins. Anything already in progress will be allowed to complete safely.

No functionality changes are expected. Once maintenance is complete, you can continue using ParkIT as normal.

**Live updates:** [status.parkit.cloud](http://status.parkit.cloud)

For support, contact [**help@parkit.cloud**](mailto:help@parkit.cloud). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    <p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>11:08:24</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully. Any issues please email help@parkit.cloud. Thank you for your patience..</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>12:34:31</var> GMT+0</small><br><strong>Identified</strong> -
  We’ll be carrying out essential platform maintenance on **Tuesday 18 August 2026**.

**Expected duration:** Up to 15 minutes.

During this time, ParkIT services will be temporarily unavailable and you’ll see a maintenance page instead of the application.

Please avoid starting new check-ins, check-outs or other time-sensitive tasks in the few minutes before maintenance begins. Anything already in progress will be allowed to complete safely.

No functionality changes are expected. Once maintenance is complete, you can continue using ParkIT as normal.

**Live updates:** [status.parkit.cloud](http://status.parkit.cloud)

For support, contact [**help@parkit.cloud**](mailto:help@parkit.cloud)..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 18 Aug 2026 11:00:00 +0000</pubDate>
  <link>https://status.parkit.cloud/maintenance/cmsd7oeln0amx0kl806zmxoo1</link>
  <guid>https://status.parkit.cloud/maintenance/cmsd7oeln0amx0kl806zmxoo1</guid>
</item>

<item>
  <title>Slow performance of image sync</title>
  <description>
    Type: Incident
    Duration: 1 hour and 29 minutes

    Affected Components: ParkIT Mobile
    Jul 27, 08:51:24 GMT+0 - Resolved - This incident has been resolved. Jul 27, 07:57:07 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 27, 07:22:02 GMT+0 - Investigating - We are aware of an issue causing inspection images to take longer than expected to appear in ParkIT.

Your inspection images have **not** been lost; they are simply delayed while being processed.

Our team is actively working to restore normal performance as quickly as possible. Thank you for your patience and understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>08:51:24</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>07:57:07</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>07:22:02</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of an issue causing inspection images to take longer than expected to appear in ParkIT.

Your inspection images have **not** been lost; they are simply delayed while being processed.

Our team is actively working to restore normal performance as quickly as possible. Thank you for your patience and understanding..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 Jul 2026 07:22:02 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cms2wfmpu0q441amtx29qhe1d</link>
  <guid>https://status.parkit.cloud/incident/cms2wfmpu0q441amtx29qhe1d</guid>
</item>

<item>
  <title>Inspection Image Sync Delays</title>
  <description>
    Type: Incident
    Duration: 2 hours and 44 minutes

    Affected Components: Portal App, Portal Services API, ParkIT Mobile
    Jul 3, 13:14:53 GMT+0 - Resolved - This incident has been resolved. Jul 3, 11:25:14 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 3, 10:30:24 GMT+0 - Investigating - We are currently investigating an issue affecting the synchronisation of inspection images captured from VCC shelters and ParkIT mobile devices.

Based on our current investigations, the issue appears to have started at approximately **09:00 BST**. During this time, newly captured inspection images may not appear in ParkIT as expected.

Our team is actively investigating the cause and will provide a further update as soon as more information is available.

We apologise for any inconvenience caused and appreciate your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>13:14:53</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:25:14</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>10:30:24</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an issue affecting the synchronisation of inspection images captured from VCC shelters and ParkIT mobile devices.

Based on our current investigations, the issue appears to have started at approximately **09:00 BST**. During this time, newly captured inspection images may not appear in ParkIT as expected.

Our team is actively investigating the cause and will provide a further update as soon as more information is available.

We apologise for any inconvenience caused and appreciate your patience..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 3 Jul 2026 10:30:24 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cmr4slegr00me1ao4ncf9mgxr</link>
  <guid>https://status.parkit.cloud/incident/cmr4slegr00me1ao4ncf9mgxr</guid>
</item>

<item>
  <title>Park IT portal slow to respond</title>
  <description>
    Type: Incident
    Duration: 8 hours and 34 minutes

    Affected Components: Self Service Kiosks, Portal App, Portal Services API, Self Service Lockers, ParkIT Mobile
    May 27, 17:55:29 GMT+0 - Resolved - All performance issues, including those affecting check-outs and key lockers, have now been fully tested and resolved. An incident report will be shared tomorrow detailing the cause of the issues. May 27, 16:33:35 GMT+0 - Monitoring - We are still investigating reports of slow performance when bookings are checking out on the Park IT portal and from Key Lockers. We will provide further updates soon. May 27, 15:44:52 GMT+0 - Monitoring - Although performance has improved, we have received reports of issues when attempting to check out bookings. We are currently investigating this. May 27, 15:10:39 GMT+0 - Monitoring - We are continuing to monitor performance across Park IT. Booking Ingestion was temporarily disabled whilst we investigated the performance issues. We will be replaying all queued booking files over the next few hours. May 27, 14:11:53 GMT+0 - Investigating - Performance has improved and we are continuing to monitor May 27, 13:32:10 GMT+0 - Investigating - Performance is improving incrementally, but we’re aware that some customers may still be experiencing delays in transactions across the platform. We are continuing to troubleshoot, and further updates will follow. Thank you for your patience. May 27, 13:03:09 GMT+0 - Investigating - Deployment of the potential fix is complete, and we are monitoring performance. May 27, 12:35:47 GMT+0 - Investigating - The potential fix is deploying into the production environment now. May 27, 11:53:04 GMT+0 - Investigating - The release with the potential fix is still in progress. We will post another update soon. May 27, 11:06:09 GMT+0 - Investigating - We are releasing a potential fix which should help improve the performance of Park IT. We will update you once the release has been completed May 27, 10:22:58 GMT+0 - Investigating - We have identified a potential fix. Further updates will follow May 27, 09:21:22 GMT+0 - Investigating - We are currently investigating this incident of slow performance across Park IT 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>17:55:29</var> GMT+0</small><br><strong>Resolved</strong> -
  All performance issues, including those affecting check-outs and key lockers, have now been fully tested and resolved. An incident report will be shared tomorrow detailing the cause of the issues..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>16:33:35</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are still investigating reports of slow performance when bookings are checking out on the Park IT portal and from Key Lockers. We will provide further updates soon..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>15:44:52</var> GMT+0</small><br><strong>Monitoring</strong> -
  Although performance has improved, we have received reports of issues when attempting to check out bookings. We are currently investigating this..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>15:10:39</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to monitor performance across Park IT. Booking Ingestion was temporarily disabled whilst we investigated the performance issues. We will be replaying all queued booking files over the next few hours..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>14:11:53</var> GMT+0</small><br><strong>Investigating</strong> -
  Performance has improved and we are continuing to monitor.</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:32:10</var> GMT+0</small><br><strong>Investigating</strong> -
  Performance is improving incrementally, but we’re aware that some customers may still be experiencing delays in transactions across the platform. We are continuing to troubleshoot, and further updates will follow. Thank you for your patience..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:03:09</var> GMT+0</small><br><strong>Investigating</strong> -
  Deployment of the potential fix is complete, and we are monitoring performance..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>12:35:47</var> GMT+0</small><br><strong>Investigating</strong> -
  The potential fix is deploying into the production environment now..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>11:53:04</var> GMT+0</small><br><strong>Investigating</strong> -
  The release with the potential fix is still in progress. We will post another update soon..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>11:06:09</var> GMT+0</small><br><strong>Investigating</strong> -
  We are releasing a potential fix which should help improve the performance of Park IT. We will update you once the release has been completed.</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>10:22:58</var> GMT+0</small><br><strong>Investigating</strong> -
  We have identified a potential fix. Further updates will follow.</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>09:21:22</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident of slow performance across Park IT.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 27 May 2026 09:21:22 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cmpnuu35701j3qkm5gmbiimo2</link>
  <guid>https://status.parkit.cloud/incident/cmpnuu35701j3qkm5gmbiimo2</guid>
</item>

<item>
  <title>Devices Manager tab blank</title>
  <description>
    Type: Incident
    Duration: 2 hours and 25 minutes

    Affected Components: ParkIT Mobile
    Nov 20, 11:26:01 GMT+0 - Resolved - This incident has been resolved. Nov 20, 11:01:27 GMT+0 - Identified - We have identified the cause and are rolling out an update to resolve the issue. Nov 20, 09:00:34 GMT+0 - Investigating - We are currently investigating an issue with the Devices Manager tab not displaying activated devices. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>11:26:01</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>11:01:27</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause and are rolling out an update to resolve the issue..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>09:00:34</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an issue with the Devices Manager tab not displaying activated devices..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 20 Nov 2025 09:00:34 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cmi77b6up016n10b76p4m17q9</link>
  <guid>https://status.parkit.cloud/incident/cmi77b6up016n10b76p4m17q9</guid>
</item>

<item>
  <title>Unable to check in or check out</title>
  <description>
    Type: Incident
    Duration: 33 minutes

    Affected Components: Self Service Lockers, Portal App, Portal Services API, Self Service Kiosks, Booking Ingestion
    Aug 5, 14:55:44 GMT+0 - Resolved - This incident has been resolved. Thank you for your patience. If you experience further issues please report them to help@parkit.cloud. Aug 5, 14:37:58 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 5, 14:22:41 GMT+0 - Investigating - We are currently investigating this incident as a priority 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 33 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:55:44</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. Thank you for your patience. If you experience further issues please report them to help@parkit.cloud..</p>
<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:37:58</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:22:41</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident as a priority.</p>
]]>
  </content:encoded>
  <pubDate>Tue, 5 Aug 2025 14:22:41 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cmdympa86002msl4nf4ypj74g</link>
  <guid>https://status.parkit.cloud/incident/cmdympa86002msl4nf4ypj74g</guid>
</item>

<item>
  <title>New bookings may not be processing from booking providers</title>
  <description>
    Type: Incident
    Duration: 1 hour and 19 minutes

    Affected Components: Booking Ingestion
    Feb 26, 19:35:19 GMT+0 - Resolved - This incident has been fully resolved and all queued bookings have now been replayed. Feb 26, 19:19:26 GMT+0 - Monitoring - We have deployed a fix for issues with new bookings.

We have started the process of reprocessing any missed new booking files so that ParkIT is fully up to date.

To reiterate, there will not be any lost bookings as a result of this partial outage. Feb 26, 18:16:03 GMT+0 - Identified - New bookings are currently not processing into ParkIT Cloud. This does not affect cancellations or amendments to bookings.

We have identified the issue and are now working to resolve as soon as possible. All sent bookings have been received and have been queued and will be processed after we roll out a fix.

Please rest assured that no bookings will be lost.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 19 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>19:35:19</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been fully resolved and all queued bookings have now been replayed..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>19:19:26</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have deployed a fix for issues with new bookings.

We have started the process of reprocessing any missed new booking files so that ParkIT is fully up to date.

To reiterate, there will not be any lost bookings as a result of this partial outage..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>18:16:03</var> GMT+0</small><br><strong>Identified</strong> -
  New bookings are currently not processing into ParkIT Cloud. This does not affect cancellations or amendments to bookings.

We have identified the issue and are now working to resolve as soon as possible. All sent bookings have been received and have been queued and will be processed after we roll out a fix.

Please rest assured that no bookings will be lost. .</p>
]]>
  </content:encoded>
  <pubDate>Wed, 26 Feb 2025 18:16:03 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cm7m8l40i000x2atk0451dlgx</link>
  <guid>https://status.parkit.cloud/incident/cm7m8l40i000x2atk0451dlgx</guid>
</item>

<item>
  <title>Planned 30 minute outage midday (UK time) 29th January for essential maintenance</title>
  <description>
    Type: Maintenance
    Duration: 14 minutes

    Affected Components: Self Service Kiosks, Self Service Lockers, Portal App, Portal Services API
    Jan 29, 12:14:14 GMT+0 - Completed - The upgrade has now been completed. Thank you for your patience. Please report any issues to help@parkit.cloud. Jan 29, 12:00:09 GMT+0 - Identified - Downtime has started. Further updates will follow. Jan 29, 12:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 29, 12:00:00 GMT+0 - Identified - **Reminding you of our planned outage this Wednesday**

. To ensure continued reliability and improved performance, we will perform a MySQL upgrade, which requires a brief period of downtime:

## **Date: Wednesday 29th January, 2025Time: Midday UK time (up to 30 minutes)**

PST 04:00:00

CET13:00:00

AEDT 23:00:00

AEST 22:00:00

NZDT 01:00:00 (+1 day)

Impact: During this time, the following services will be unavailable:

* ParkIT platform
* ParkIT mobile app
* Kiosks and lockers

Any pictures captured of vehicles at the VCC booths will not be lost and will catch up after the platform is back online. However, no ANPR lookup will be operational during the outage, so any barriers will have to be raised by intercom.

Why then?

Our analysis indicates that this timing aligns with the period of least activity across our customer base, minimising disruption.

How can I prepare?

We recommend that you print copies of expected arrivals and returns before the outage and that you keep manual records of the following during the maintenance period:

* Check-ins and check-outs
* Key movements
* Vehicle movements

We apologise for any inconvenience this may cause and greatly appreciate your understanding as we work to enhance the performance and reliability of our platform.

If you have any questions or require further assistance, please do not hesitate to contact our support team at [help@parkit.cloud](mailto:help@parkit.cloud). Customers can also subscribe to live notifications on &lt;https://status.parkit.cloud/&gt; Jan 29, 12:00:00 GMT+0 - Identified - We are writing to inform you of an upcoming planned maintenance window for our platform. To ensure continued reliability and improved performance, we will perform a MySQL upgrade, which requires a brief period of downtime.

### Details of the planned outage:

* **Date: Wednesday 29th January, 2025**
* **Time: Midday UK time (up to 30 minutes)**

Impact: During this time, the following services will be unavailable:

* ParkIT platform
* ParkIT mobile app
* Kiosks and lockers

Any pictures captured of vehicles at the VCC booths will not be lost and will catch up after the platform is back online. However, no ANPR lookup will be operational during the outage, so any barriers will have to be raised by intercom.

### 

### Why then?

Our analysis indicates that this timing aligns with the period of least activity across our customer base, minimising disruption.

### How can I prepare?

We recommend that you print copies of expected arrivals and returns before the outage and that you keep manual records of the following during the maintenance period:

* Check-ins and check-outs
* Key movements
* Vehicle movements

We apologise for any inconvenience this may cause and greatly appreciate your understanding as we work to enhance the performance and reliability of our platform.

If you have any questions or require further assistance, please do not hesitate to contact our support team at [help@parkit.cloud](mailto:help@parkit.cloud). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>12:14:14</var> GMT+0</small><br><strong>Completed</strong> -
  The upgrade has now been completed. Thank you for your patience. Please report any issues to help@parkit.cloud..</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>12:00:09</var> GMT+0</small><br><strong>Identified</strong> -
  Downtime has started. Further updates will follow..</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  **Reminding you of our planned outage this Wednesday**

. To ensure continued reliability and improved performance, we will perform a MySQL upgrade, which requires a brief period of downtime:

## **Date: Wednesday 29th January, 2025Time: Midday UK time (up to 30 minutes)**

PST 04:00:00

CET13:00:00

AEDT 23:00:00

AEST 22:00:00

NZDT 01:00:00 (+1 day)

Impact: During this time, the following services will be unavailable:

* ParkIT platform
* ParkIT mobile app
* Kiosks and lockers

Any pictures captured of vehicles at the VCC booths will not be lost and will catch up after the platform is back online. However, no ANPR lookup will be operational during the outage, so any barriers will have to be raised by intercom.

Why then?

Our analysis indicates that this timing aligns with the period of least activity across our customer base, minimising disruption.

How can I prepare?

We recommend that you print copies of expected arrivals and returns before the outage and that you keep manual records of the following during the maintenance period:

* Check-ins and check-outs
* Key movements
* Vehicle movements

We apologise for any inconvenience this may cause and greatly appreciate your understanding as we work to enhance the performance and reliability of our platform.

If you have any questions or require further assistance, please do not hesitate to contact our support team at [help@parkit.cloud](mailto:help@parkit.cloud). Customers can also subscribe to live notifications on &lt;https://status.parkit.cloud/&gt;.</p>
<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are writing to inform you of an upcoming planned maintenance window for our platform. To ensure continued reliability and improved performance, we will perform a MySQL upgrade, which requires a brief period of downtime.

### Details of the planned outage:

* **Date: Wednesday 29th January, 2025**
* **Time: Midday UK time (up to 30 minutes)**

Impact: During this time, the following services will be unavailable:

* ParkIT platform
* ParkIT mobile app
* Kiosks and lockers

Any pictures captured of vehicles at the VCC booths will not be lost and will catch up after the platform is back online. However, no ANPR lookup will be operational during the outage, so any barriers will have to be raised by intercom.

### 

### Why then?

Our analysis indicates that this timing aligns with the period of least activity across our customer base, minimising disruption.

### How can I prepare?

We recommend that you print copies of expected arrivals and returns before the outage and that you keep manual records of the following during the maintenance period:

* Check-ins and check-outs
* Key movements
* Vehicle movements

We apologise for any inconvenience this may cause and greatly appreciate your understanding as we work to enhance the performance and reliability of our platform.

If you have any questions or require further assistance, please do not hesitate to contact our support team at [help@parkit.cloud](mailto:help@parkit.cloud)..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 29 Jan 2025 12:00:00 +0000</pubDate>
  <link>https://status.parkit.cloud/maintenance/cm5v8pf6h003qmgmg18s2x9tn</link>
  <guid>https://status.parkit.cloud/maintenance/cm5v8pf6h003qmgmg18s2x9tn</guid>
</item>

<item>
  <title>Issues checking in bookings on the Portal</title>
  <description>
    Type: Incident
    Duration: 12 hours and 14 minutes

    Affected Components: Portal App, Portal Services API
    Sep 27, 16:50:01 GMT+0 - Resolved -  Sep 27, 07:17:49 GMT+0 - Monitoring - A fix has been applied. Please can you reload your browser to effect the change:

1. Whilst viewing [app.parkit.cloud](http://app.parkit.cloud), and assuming you are using a Chrome browser:
* On Windows machines, Press Ctrl and press F5
* On Mac machines, Press Command and R

This will refresh the currently open page.

Our apologies again for the inconvenience caused by this issue. Sep 27, 06:15:23 GMT+0 - Identified - We are continuing to work on a fix for this incident. A fix is in testing. Our apologies for any inconvenience caused. Sep 27, 05:02:14 GMT+0 - Identified - We have identified the cause and are working on a solution. Sep 27, 04:35:59 GMT+0 - Investigating - We are aware that some customers are experiencing issues checking in customers on the Portal. We are investigating this issue and will post here with further updates. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>16:50:01</var> GMT+0</small><br><strong>Resolved</strong> -
  .</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>07:17:49</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been applied. Please can you reload your browser to effect the change:

1. Whilst viewing [app.parkit.cloud](http://app.parkit.cloud), and assuming you are using a Chrome browser:
* On Windows machines, Press Ctrl and press F5
* On Mac machines, Press Command and R

This will refresh the currently open page.

Our apologies again for the inconvenience caused by this issue..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>06:15:23</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. A fix is in testing. Our apologies for any inconvenience caused..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>05:02:14</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause and are working on a solution..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>04:35:59</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware that some customers are experiencing issues checking in customers on the Portal. We are investigating this issue and will post here with further updates..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 27 Sep 2024 04:35:59 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cm1k8d0wp0001yvg09f0xq8sf</link>
  <guid>https://status.parkit.cloud/incident/cm1k8d0wp0001yvg09f0xq8sf</guid>
</item>

<item>
  <title>Some external services are currently unavailable</title>
  <description>
    Type: Incident
    Duration: 1 hour and 27 minutes

    Affected Components: Self Service Kiosks, Portal Services API
    Sep 17, 13:05:56 GMT+0 - Resolved - This incident has been resolved. Sep 17, 11:57:05 GMT+0 - Monitoring - Services have been resumed, however there may be degraded performance due to external service outages (Google). Sep 17, 11:39:03 GMT+0 - Investigating - We are currently investigating this incident as a matter of priority. Updates will be provided.

**Areas Affected**

DVLA Lookup

Flight Lookup  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 27 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>13:05:56</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>11:57:05</var> GMT+0</small><br><strong>Monitoring</strong> -
  Services have been resumed, however there may be degraded performance due to external service outages (Google)..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>11:39:03</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident as a matter of priority. Updates will be provided.

**Areas Affected**

DVLA Lookup

Flight Lookup .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 17 Sep 2024 11:39:03 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cm16d2kpb0001rzyrxpfjwjhb</link>
  <guid>https://status.parkit.cloud/incident/cm16d2kpb0001rzyrxpfjwjhb</guid>
</item>

<item>
  <title>Performance issues</title>
  <description>
    Type: Incident
    Duration: 19 minutes

    Affected Components: Portal App, Portal Services API
    Jul 18, 16:39:25 GMT+0 - Resolved - This incident has been resolved. Jul 18, 16:20:40 GMT+0 - Identified - We are aware of performance issues with our reports suite. We have pulled the offending report and are in the process of optimising the platform. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>16:39:25</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>16:20:40</var> GMT+0</small><br><strong>Identified</strong> -
  We are aware of performance issues with our reports suite. We have pulled the offending report and are in the process of optimising the platform..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 18 Jul 2024 16:20:40 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clyrh9rfq159377oiofhdg3tk05</link>
  <guid>https://status.parkit.cloud/incident/clyrh9rfq159377oiofhdg3tk05</guid>
</item>

<item>
  <title>ParkIT connection issues</title>
  <description>
    Type: Incident
    Duration: 7 days, 12 hours and 38 minutes

    Affected Components: Self Service Kiosks, Self Service Lockers, Portal App, Portal Services API
    May 8, 08:12:04 GMT+0 - Resolved - On Tuesday, 30th April, our services were temporarily disrupted due to an issue with AWS Global Accelerator services. This affected client traffic originating mainly from the United Kingdom, specifically to the AWS London and Dublin edge locations. Amazon&#039;s hosting services have resolved the problem, and I am pleased to report that our services are fully operational.

After consulting with Amazon, they confirmed that the disruption was an anomaly, a rare fault in their Global Accelerator services. This incident, in fact, stands out as one of the few interruptions we&#039;ve encountered in our three years of operation.

We have also taken proactive steps to include this issue in our risk register, which ensures it is formally tracked and assessed within our risk management framework. This means we actively monitor the situation and promptly investigate and implement appropriate mitigation strategies where applicable. This approach helps us manage and minimise potential disruptions more effectively, safeguarding the reliability of our service. Apr 30, 20:15:21 GMT+0 - Monitoring - ParkIT services should now be resumed. We are actively monitoring and will continue to update Apr 30, 19:59:44 GMT+0 - Identified - This issue appears to be regional. Please contact [help@parkit.cloud](mailto:help@parkit.cloud) for any reports you require to assist you. We&#039;re still working on the resolution. Apr 30, 19:33:35 GMT+0 - Investigating - We are aware of the issue with ParkIT web services. We are currently investigating this incident. Further reports will follow 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 12 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>08:12:04</var> GMT+0</small><br><strong>Resolved</strong> -
  On Tuesday, 30th April, our services were temporarily disrupted due to an issue with AWS Global Accelerator services. This affected client traffic originating mainly from the United Kingdom, specifically to the AWS London and Dublin edge locations. Amazon&#039;s hosting services have resolved the problem, and I am pleased to report that our services are fully operational.

After consulting with Amazon, they confirmed that the disruption was an anomaly, a rare fault in their Global Accelerator services. This incident, in fact, stands out as one of the few interruptions we&#039;ve encountered in our three years of operation.

We have also taken proactive steps to include this issue in our risk register, which ensures it is formally tracked and assessed within our risk management framework. This means we actively monitor the situation and promptly investigate and implement appropriate mitigation strategies where applicable. This approach helps us manage and minimise potential disruptions more effectively, safeguarding the reliability of our service..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>20:15:21</var> GMT+0</small><br><strong>Monitoring</strong> -
  ParkIT services should now be resumed. We are actively monitoring and will continue to update.</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>19:59:44</var> GMT+0</small><br><strong>Identified</strong> -
  This issue appears to be regional. Please contact [help@parkit.cloud](mailto:help@parkit.cloud) for any reports you require to assist you. We&#039;re still working on the resolution..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>19:33:35</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of the issue with ParkIT web services. We are currently investigating this incident. Further reports will follow.</p>
]]>
  </content:encoded>
  <pubDate>Tue, 30 Apr 2024 19:33:35 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clvmsdkpz59669b5n05lj78yzk</link>
  <guid>https://status.parkit.cloud/incident/clvmsdkpz59669b5n05lj78yzk</guid>
</item>

<item>
  <title>Issue with booking asset history</title>
  <description>
    Type: Incident
    Duration: 1 hour and 48 minutes

    Affected Components: Portal App
    Mar 20, 22:56:36 GMT+0 - Resolved - The fix for this release has been successfully deployed. If you do not see an immediate improvement, please reload your browser (In Chrome, go to **View &gt; Reload this Page**).

Thank you for your patience. Mar 20, 22:20:20 GMT+0 - Identified - We are in the process of testing the rectification. More news will follow shortly. Mar 20, 21:08:16 GMT+0 - Identified - We are aware of an issue with the **Assets** section of the **History** panel of a booking misreporting the previous and current vehicle movements. We have identified this is a display issue only, and the current vehicle and key locations are correct. We are implementing a resolution and further updates will follow shortly. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 48 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>22:56:36</var> GMT+0</small><br><strong>Resolved</strong> -
  The fix for this release has been successfully deployed. If you do not see an immediate improvement, please reload your browser (In Chrome, go to **View &gt; Reload this Page**).

Thank you for your patience..</p>
<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>22:20:20</var> GMT+0</small><br><strong>Identified</strong> -
  We are in the process of testing the rectification. More news will follow shortly..</p>
<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>21:08:16</var> GMT+0</small><br><strong>Identified</strong> -
  We are aware of an issue with the **Assets** section of the **History** panel of a booking misreporting the previous and current vehicle movements. We have identified this is a display issue only, and the current vehicle and key locations are correct. We are implementing a resolution and further updates will follow shortly..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 20 Mar 2024 21:08:16 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clu0apeek1576209eoj6owzr163</link>
  <guid>https://status.parkit.cloud/incident/clu0apeek1576209eoj6owzr163</guid>
</item>

<item>
  <title>Important Service Update: Scheduled Downtime on Tuesday February 6th 2024 (UK TIME)</title>
  <description>
    Type: Maintenance
    Duration: 24 minutes

    Affected Components: Self Service Kiosks, Self Service Lockers, Portal App, Portal Services API
    Feb 6, 12:21:41 GMT+0 - Completed - Upgrade works complete. Thank you for your patience. The system was down 19 minutes and completed 12:19 Feb 6, 12:00:00 GMT+0 - Identified - **Date**: February 6th (with the exception of New Zealand which is February 7th)

**Time**:   
12:00 PM to 12:30 PM (UK Time)  
23:00-23:30 (AEDT)  
04:00-04:30 (PST)  
Wednesday 01:00-01:30 (NZDT)

**Impact**: Our services will be completely unavailable for approximately 15 minutes between this time. We have taken steps to ensure this interruption is kept to an absolute minimum.

**Preparation Advice:**  
To ensure minimal disruption to your operations, we strongly recommend creating physical printouts of your arrivals and returns lists before the downtime. These printouts will help you continue to serve your customers effectively during this brief interruption.

We apologise for any inconvenience this may cause and appreciate your understanding and cooperation. Our team is dedicated to making this process as smooth as possible and ensuring a quick return to normal service.

If you have any questions or concerns, please don&#039;t hesitate to contact our support team at help@parkit.cloud. Feb 6, 11:57:36 GMT+0 - Identified - We are about to commence with the upgrade. Further updates will follow 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 24 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>12:21:41</var> GMT+0</small><br><strong>Completed</strong> -
  Upgrade works complete. Thank you for your patience. The system was down 19 minutes and completed 12:19.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  **Date**: February 6th (with the exception of New Zealand which is February 7th)

**Time**:   
12:00 PM to 12:30 PM (UK Time)  
23:00-23:30 (AEDT)  
04:00-04:30 (PST)  
Wednesday 01:00-01:30 (NZDT)

**Impact**: Our services will be completely unavailable for approximately 15 minutes between this time. We have taken steps to ensure this interruption is kept to an absolute minimum.

**Preparation Advice:**  
To ensure minimal disruption to your operations, we strongly recommend creating physical printouts of your arrivals and returns lists before the downtime. These printouts will help you continue to serve your customers effectively during this brief interruption.

We apologise for any inconvenience this may cause and appreciate your understanding and cooperation. Our team is dedicated to making this process as smooth as possible and ensuring a quick return to normal service.

If you have any questions or concerns, please don&#039;t hesitate to contact our support team at help@parkit.cloud..</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>11:57:36</var> GMT+0</small><br><strong>Identified</strong> -
  We are about to commence with the upgrade. Further updates will follow.</p>
]]>
  </content:encoded>
  <pubDate>Tue, 6 Feb 2024 12:00:00 +0000</pubDate>
  <link>https://status.parkit.cloud/maintenance/clrz47wul4777bkofln3qfqbx</link>
  <guid>https://status.parkit.cloud/maintenance/clrz47wul4777bkofln3qfqbx</guid>
</item>

<item>
  <title>Error when searching for flights on the self service kiosks</title>
  <description>
    Type: Incident
    Duration: 1 hour and 39 minutes

    Affected Components: Self Service Kiosks
    Dec 21, 19:16:46 GMT+0 - Resolved - This incident has been resolved.   Thank you for your patience.  If you experience any issues please email help@parkit.cloud Dec 21, 17:37:18 GMT+0 - Investigating - We are aware of the error &quot;Cannot access &#039;results&#039; before initialization&quot; when searching for flights on the self-service kiosks.  This is an intermittent error that goes away after a couple of retries.

We are actively investigating now 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 39 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>19:16:46</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved.   Thank you for your patience.  If you experience any issues please email help@parkit.cloud.</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>17:37:18</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of the error &quot;Cannot access &#039;results&#039; before initialization&quot; when searching for flights on the self-service kiosks.  This is an intermittent error that goes away after a couple of retries.

We are actively investigating now.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 21 Dec 2023 17:37:18 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clqfhjff8591176copks1p4lmg</link>
  <guid>https://status.parkit.cloud/incident/clqfhjff8591176copks1p4lmg</guid>
</item>

<item>
  <title>Some key locations may not allow key movements in certain scenarios</title>
  <description>
    Type: Incident
    Duration: 39 minutes

    Affected Components: Portal App
    Sep 12, 13:14:11 GMT+0 - Resolved - This incident has been resolved. Sep 12, 12:50:10 GMT+0 - Identified - The issue has been identified and we are now deploying a hotfix. Sep 12, 12:35:16 GMT+0 - Investigating - Within today&#039;s release, there may be some instances where certain locations (drivers and key lockers) are not allowed.

We are currently investigating this incident and expect to release a hotfix to remedy it. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 39 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>13:14:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>12:50:10</var> GMT+0</small><br><strong>Identified</strong> -
  The issue has been identified and we are now deploying a hotfix..</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>12:35:16</var> GMT+0</small><br><strong>Investigating</strong> -
  Within today&#039;s release, there may be some instances where certain locations (drivers and key lockers) are not allowed.

We are currently investigating this incident and expect to release a hotfix to remedy it..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 12 Sep 2023 12:35:16 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clmgaptyu115573buo7xfgnbum2</link>
  <guid>https://status.parkit.cloud/incident/clmgaptyu115573buo7xfgnbum2</guid>
</item>

<item>
  <title>System performance degradation on Portal</title>
  <description>
    Type: Incident
    Duration: 6 hours and 50 minutes

    Affected Components: Portal App
    Aug 29, 19:09:38 GMT+0 - Resolved - Today we released a hotfix that should remedy the performance issues that some users may have been experiencing.

We continue with our efforts to optimise and enhance the user experience and will be releasing numerous updates over the coming weeks to further improve performance and experience.  Aug 29, 12:19:17 GMT+0 - Investigating - Some users may be experiencing performance issues with the Portal. We are currently investigating this issue as a high priority.

**Progress Summary:**

- Initial reports of slowness verified.
- Root cause analysis underway.

**Next Steps:**

- Analyse logs and metrics to pinpoint the exact issue.
- Engineering Team to identify possible solutions.
- Hotfix deployment as soon as available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>19:09:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Today we released a hotfix that should remedy the performance issues that some users may have been experiencing.

We continue with our efforts to optimise and enhance the user experience and will be releasing numerous updates over the coming weeks to further improve performance and experience. .</p>
<p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>12:19:17</var> GMT+0</small><br><strong>Investigating</strong> -
  Some users may be experiencing performance issues with the Portal. We are currently investigating this issue as a high priority.

**Progress Summary:**

- Initial reports of slowness verified.
- Root cause analysis underway.

**Next Steps:**

- Analyse logs and metrics to pinpoint the exact issue.
- Engineering Team to identify possible solutions.
- Hotfix deployment as soon as available..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 29 Aug 2023 12:19:17 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cllw9zce612817beomb956ypvs</link>
  <guid>https://status.parkit.cloud/incident/cllw9zce612817beomb956ypvs</guid>
</item>

<item>
  <title>Issues shipping alerts and scheduled reports by email</title>
  <description>
    Type: Incident
    Duration: 2 hours and 12 minutes

    Affected Components: Portal App
    Jun 22, 13:52:02 GMT+0 - Resolved - This incident has been resolved. Jun 22, 11:39:43 GMT+0 - Investigating - Users may not be receiving alerts or reports via email.

We are currently investigating this incident.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>13:52:02</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>11:39:43</var> GMT+0</small><br><strong>Investigating</strong> -
  Users may not be receiving alerts or reports via email.

We are currently investigating this incident. .</p>
]]>
  </content:encoded>
  <pubDate>Thu, 22 Jun 2023 11:39:43 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clj72mj1z396744c9ofy9d45b1o</link>
  <guid>https://status.parkit.cloud/incident/clj72mj1z396744c9ofy9d45b1o</guid>
</item>

<item>
  <title>Performance issues have been reported</title>
  <description>
    Type: Incident
    Duration: 1 hour and 31 minutes

    Affected Components: Portal App
    May 25, 15:52:01 GMT+0 - Resolved - This incident has been resolved. May 25, 14:42:02 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 25, 14:21:04 GMT+0 - Investigating - Some users may be experiencing problems when logging in, or loading functions.

We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>15:52:01</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>14:42:02</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>14:21:04</var> GMT+0</small><br><strong>Investigating</strong> -
  Some users may be experiencing problems when logging in, or loading functions.

We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 25 May 2023 14:21:04 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cli3826bp57546b0n4mibondv4</link>
  <guid>https://status.parkit.cloud/incident/cli3826bp57546b0n4mibondv4</guid>
</item>

<item>
  <title>Key scanning in bulk is currently not performing optimally </title>
  <description>
    Type: Incident
    Duration: 5 hours and 17 minutes

    Affected Components: Portal App
    Apr 24, 18:47:15 GMT+0 - Resolved - This incident has been resolved. Apr 24, 13:51:37 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 24, 13:30:05 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>18:47:15</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>13:51:37</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>13:30:05</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Apr 2023 13:30:05 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clguvl7cd331739violxfo6oedc</link>
  <guid>https://status.parkit.cloud/incident/clguvl7cd331739violxfo6oedc</guid>
</item>

<item>
  <title>Parse Error - Major Incident</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: Portal App, Portal Services API
    Apr 17, 09:41:33 GMT+0 - Resolved - This incident has been resolved. Apr 17, 09:38:12 GMT+0 - Monitoring - We have implemented a fix and are currently monitoring the result. all services should now be performing as expected. Apr 17, 09:15:53 GMT+0 - Identified - We have identified the issue and are currently implementing a patch. Apr 17, 09:14:44 GMT+0 - Investigating - We are currently investigating this incident as a matter of priority.

We expect to have a resolution soon. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:41:33</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:38:12</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented a fix and are currently monitoring the result. all services should now be performing as expected..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:15:53</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue and are currently implementing a patch..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:14:44</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident as a matter of priority.

We expect to have a resolution soon..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 17 Apr 2023 09:14:44 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/clgkmduff1165bvodoqphtf56</link>
  <guid>https://status.parkit.cloud/incident/clgkmduff1165bvodoqphtf56</guid>
</item>

<item>
  <title>Some customers may be experiencing degraded performance on all platforms</title>
  <description>
    Type: Incident
    Duration: 20 minutes

    Affected Components: Portal Services API, Portal App
    Mar 15, 09:37:17 GMT+0 - Resolved - We just resolved the issue! Mar 15, 09:17:43 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>09:37:17</var> GMT+0</small><br><strong>Resolved</strong> -
  We just resolved the issue!.</p>
<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>09:17:43</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 15 Mar 2022 09:17:43 +0000</pubDate>
  <link>https://status.parkit.cloud/incident/cl0rx8nyy170288e4oe4aotuyu0</link>
  <guid>https://status.parkit.cloud/incident/cl0rx8nyy170288e4oe4aotuyu0</guid>
</item>

  </channel>
  </rss>