<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:orkestro.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://orkestro.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://orkestro.instatus.com/history.atom"/>
  <title>Orkestro Status - Incident history</title>
  <updated>2026-06-09T09:00:31.906+00:00</updated>
  <author>
    <name>Orkestro</name>
  </author>
  
<entry>
  <id>tag:orkestro.instatus.com,2005:Incident/cmq6etcy706efqmmorncwpp1b</id>
  <published>2026-06-09T09:00:31.906+00:00</published>
  <updated>2026-06-09T09:00:32.906+00:00</updated>
  <link rel="alternate" type="text/html" href="https://orkestro.instatus.com/incident/cmq6etcy706efqmmorncwpp1b"/>
  <title>Specific orders not loading in the Portal</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Portal</p>
    <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>09:00:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  This temporarily affected a small number of orders for a specific merchant, with no data loss..</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>09:00:31</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:orkestro.instatus.com,2005:Incident/cmpgpiv7s0a9tnih8ysonfeme</id>
  <published>2026-05-22T09:18:17.589+00:00</published>
  <updated>2026-05-22T09:18:17.589+00:00</updated>
  <link rel="alternate" type="text/html" href="https://orkestro.instatus.com/incident/cmpgpiv7s0a9tnih8ysonfeme"/>
  <title>Portal and APIs are not responding</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> Third Party: Fleet Provider, Portal, Partner API, Fleet API</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>09:18:17</var> GMT+0</small><br /><strong>Investigating</strong> -
  One of the third-party providers that we run on is experiencing a major outage. We&#039;ll continue investigating and working with them and keep you posted. .</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>09:24:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  The third-party provider is back up and running. We&#039;ll liaise with them to get an update and share it with you in due course..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:22:47</var> GMT+0</small><br /><strong>Postmortem</strong> -
  There was a complete outage in a European data centre, which is where a key third-party provider of ours runs their software. This caused their platform to go down, causing an impact on ours as well. We&#039;ll review this provider and assess different options internally. Sorry for the problems this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:orkestro.instatus.com,2005:Incident/cmp2h1ros0fubugtte3quw2xn</id>
  <published>2026-05-12T09:38:00.000+00:00</published>
  <updated>2026-05-12T09:38:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://orkestro.instatus.com/incident/cmp2h1ros0fubugtte3quw2xn"/>
  <title>Booking creation failure</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Portal, Partner API</p>
    <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>09:38:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Users are experiencing issues when booking a fleet and getting updates from existing bookings. We&#039;re investigating and will provide updates here..</p>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved, and the service is back online. The team will continue to analyse what happened and do a post-mortem. .</p>

        ]]>
  </content>
</entry>

</feed>