<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.tebi.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.tebi.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.tebi.com/history.atom"/>
  <title>Tebi Status - Incident history</title>
  <updated>2026-09-06T10:38:05.890+00:00</updated>
  <author>
    <name>Tebi</name>
  </author>
  
<entry>
  <id>tag:status.tebi.com,2005:Incident/cmtpohnda0l4a1nqw838hrgwt</id>
  <published>2026-09-06T10:38:05.890+00:00</published>
  <updated>2026-09-06T10:38:05.890+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmtpohnda0l4a1nqw838hrgwt"/>
  <title>Day Overview Report</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Backoffice (Reservations, Insights, Acct. Mgmt.)</p>
    <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>10:38:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have identified an issue which is causing a discrepancy in our card reporting, affecting the day overview. You will see a negative balance for Saturday (05/09) and a positive balance for Sunday (06/09), which should zero out.  
  
There&#039;s no in-person card payments missing, so you don&#039;t have to worry about that. The issue has been resolved, and everything is now functioning properly..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmtpkywdj0k991nqw1mhaayrs</id>
  <published>2026-09-05T20:00:00.000+00:00</published>
  <updated>2026-09-06T09:49:29.401+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmtpkywdj0k991nqw1mhaayrs"/>
  <title>Payments Reporting, QR Ordering, and Online Payments.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> Payment processing, Backoffice (Reservations, Insights, Acct. Mgmt.)</p>
    <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>09:49:29</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmspt9rxt00db10p266ryn6tt</id>
  <published>2026-08-12T08:12:14.533+00:00</published>
  <updated>2026-08-14T07:17:20.082+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmspt9rxt00db10p266ryn6tt"/>
  <title>&quot;Reserve with Google&quot; has been disabled</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 23 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> Integrations - Third Party</p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>07:17:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>08:12:14</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Google Reservations/&quot;Reserve with Google&quot; is currently disabled. We are working directly with Google to resolve this.

**All other reservation functionality within Tebi is unaffected, and operating normally as expected**. This means guests can still make reservations through the widget, or other links provided to them..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmsms6gqe0hw50krp50ihzll8</id>
  <published>2026-08-10T05:18:21.888+00:00</published>
  <updated>2026-08-10T05:37:20.451+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmsms6gqe0hw50krp50ihzll8"/>
  <title>Issues affecting Tebi services </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> Payment processing, App (POS, KDS, Reservations) , Backoffice (Reservations, Insights, Acct. Mgmt.)</p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>05:37:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>05:31:46</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'> 10</var>, <var data-var='time'>05:18:21</var> GMT+0</small><br /><strong>Investigating</strong> -
  Some accounts are experiencing issues accessing and using Tebi products including the POS, and reservations. We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmqql0i3n09oq2omkh0nv8i6j</id>
  <published>2026-06-23T10:30:08.887+00:00</published>
  <updated>2026-06-23T10:30:09.887+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmqql0i3n09oq2omkh0nv8i6j"/>
  <title>Negative amounts shown for payments on the day overview</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Backoffice (Reservations, Insights, Acct. Mgmt.), App (POS, KDS, Reservations) </p>
    <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>10:30:09</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>10:30:08</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmpsiuk3g0aw5nplszvzvv69b</id>
  <published>2026-05-30T14:00:00.000+00:00</published>
  <updated>2026-05-30T17:20:48.363+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmpsiuk3g0aw5nplszvzvv69b"/>
  <title>Issues impacting device connection, prep orders, and QR</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> Payment processing, Backoffice (Reservations, Insights, Acct. Mgmt.), App (POS, KDS, Reservations) </p>
    <p><small>May <var data-var='date'> 30</var>, <var data-var='time'>17:20:48</var> GMT+0</small><br /><strong>Resolved</strong> -
  This issue has been resolved. All systems back to normal..</p>
<p><small>May <var data-var='date'> 30</var>, <var data-var='time'>17:00:52</var> GMT+0</small><br /><strong>Identified</strong> -
  We are seeing an increase in device loading issues again - we are continuing to work on a fix for this incident..</p>
<p><small>May <var data-var='date'> 30</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 30</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We identified an issue affecting a subset of devices from connecting to Tebi. Additionally, this caused some delays with QR ordering and prep stations..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmp5hpgvd038hqjjtvnr7aqop</id>
  <published>2026-05-14T12:54:00.791+00:00</published>
  <updated>2026-05-14T13:55:58.192+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmp5hpgvd038hqjjtvnr7aqop"/>
  <title>Issues impacting connection between Tebi devices</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 2 minutes</p>
    <p><strong>Affected Components:</strong> App (POS, KDS, Reservations) </p>
    <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>13:55:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>13:04:53</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'> 14</var>, <var data-var='time'>12:54:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified an issue affecting some devices. Affected devices are not able to connect fully with Tebi services and may have issues with sending payments from a POS device to a payment terminal or with printing or showing kitchen tickets. We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmncyxojq08lcj3xdmj76tmgm</id>
  <published>2026-03-30T09:11:16.034+00:00</published>
  <updated>2026-03-31T06:57:36.526+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmncyxojq08lcj3xdmj76tmgm"/>
  <title>Data temporarily unavailable in the Back Office Dashboard for 29 March</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> Backoffice (Reservations, Insights, Acct. Mgmt.)</p>
    <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>06:57:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>09:11:16</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are working on a fix for this incident. You can view all data in the App Dashboard while we work on a fix. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmn4fhzl307vn8le6rrl8cp17</id>
  <published>2026-03-24T09:45:01.689+00:00</published>
  <updated>2026-03-24T10:18:44.284+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmn4fhzl307vn8le6rrl8cp17"/>
  <title>QR orders not being closed or sent to the prep stations &amp; pre-payments for reservations not being processed.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> App (POS, KDS, Reservations) </p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>10:18:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  The technical issue affecting QR ordering &amp; reservations with prepayments has been fully resolved.

* New orders placed via QR code will now automatically send to your prep stations and kitchens as usual.
* Reservations involving prepayments are now confirming correctly. Any reservations impacted over the last hour are currently being updated to &quot;Confirmed&quot; status. Around 50 reservations with prepayment that were placed between 0930 to 1000 (CET) were not confirmed. Guests have been refunded and email to let them know that the reservation was not confirmed.
* **What was affected:** This issue was strictly limited to orders placed by **guests on their own devices**. Any orders your staff entered directly into the POS were **not** affected and processed normally..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>10:06:17</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>09:45:01</var> GMT+0</small><br /><strong>Identified</strong> -
  We are experiencing a technical glitch where QR orders are processing payments but failing to send to the kitchen. We are working on a resolution now.  
  
We are working on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.tebi.com,2005:Incident/cmmt4w0tp022s14pi6plk9fuk</id>
  <published>2026-02-06T16:30:00.000+00:00</published>
  <updated>2026-02-06T19:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.tebi.com/incident/cmmt4w0tp022s14pi6plk9fuk"/>
  <title>Tebi app</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days and 12 hours</p>
    <p><strong>Affected Components:</strong> App (POS, KDS, Reservations) </p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  | At 17:30, the loading time of our app increased significantly, and some merchants couldn&#039;t access this. We quickly found the root cause but it took our system much longer than expected to recuperate with the busy load of a Friday night. At 20:30, our systems fully recovered. The root cause:At 6:00 on Friday the 6th, some of our team performed a data migration that had a critical human error.With little system activity at the start of the day, we did not notice the heavy load this brought. It was only until later in the afternoon when business became busy that we noticed the strain on the Tebi system.This was a rare domino effect caused by errors, communication, and system capacity. We are now dedicating our teams to put in safeguards to avoid this in the future. |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |.</p>

        ]]>
  </content>
</entry>

</feed>