<?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>Tebi Status - Incident history</title>
    <link>https://status.tebi.com</link>
    <description>Tebi</description>
    <pubDate>Sun, 6 Sep 2026 10:38:05 +0000</pubDate>
    
<item>
  <title>Day Overview Report</title>
  <description>
    Type: Incident
    

    Affected Components: Backoffice (Reservations, Insights, Acct. Mgmt.)
    Sep 6, 10:38:05 GMT+0 - Resolved - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Sun, 6 Sep 2026 10:38:05 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmtpohnda0l4a1nqw838hrgwt</link>
  <guid>https://status.tebi.com/incident/cmtpohnda0l4a1nqw838hrgwt</guid>
</item>

<item>
  <title>Payments Reporting, QR Ordering, and Online Payments.</title>
  <description>
    Type: Incident
    Duration: 13 hours and 49 minutes

    Affected Components: Payment processing, Backoffice (Reservations, Insights, Acct. Mgmt.)
    Sep 6, 09:49:29 GMT+0 - Resolved - This incident has been resolved. Sep 5, 20:00:00 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> 13 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> , </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:encoded>
  <pubDate>Sat, 5 Sep 2026 20:00:00 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmtpkywdj0k991nqw1mhaayrs</link>
  <guid>https://status.tebi.com/incident/cmtpkywdj0k991nqw1mhaayrs</guid>
</item>

<item>
  <title>&quot;Reserve with Google&quot; has been disabled</title>
  <description>
    Type: Incident
    Duration: 1 day, 23 hours and 5 minutes

    Affected Components: Integrations - Third Party
    Aug 14, 07:17:20 GMT+0 - Resolved - This incident has been resolved. Aug 12, 08:12:14 GMT+0 - Monitoring - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 23 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Wed, 12 Aug 2026 08:12:14 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmspt9rxt00db10p266ryn6tt</link>
  <guid>https://status.tebi.com/incident/cmspt9rxt00db10p266ryn6tt</guid>
</item>

<item>
  <title>Issues affecting Tebi services </title>
  <description>
    Type: Incident
    Duration: 19 minutes

    Affected Components: Payment processing, App (POS, KDS, Reservations) , Backoffice (Reservations, Insights, Acct. Mgmt.)
    Aug 10, 05:37:20 GMT+0 - Resolved - This incident has been resolved. Aug 10, 05:31:46 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 10, 05:18:21 GMT+0 - Investigating - Some accounts are experiencing issues accessing and using Tebi products including the POS, and reservations. We are currently investigating this incident. 
  </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>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:encoded>
  <pubDate>Mon, 10 Aug 2026 05:18:21 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmsms6gqe0hw50krp50ihzll8</link>
  <guid>https://status.tebi.com/incident/cmsms6gqe0hw50krp50ihzll8</guid>
</item>

<item>
  <title>Negative amounts shown for payments on the day overview</title>
  <description>
    Type: Incident
    

    Affected Components: Backoffice (Reservations, Insights, Acct. Mgmt.), App (POS, KDS, Reservations) 
    Jun 23, 10:30:09 GMT+0 - Resolved - This incident has been resolved. Jun 23, 10:30:08 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>Affected Components:</strong> , </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:encoded>
  <pubDate>Tue, 23 Jun 2026 10:30:08 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmqql0i3n09oq2omkh0nv8i6j</link>
  <guid>https://status.tebi.com/incident/cmqql0i3n09oq2omkh0nv8i6j</guid>
</item>

<item>
  <title>Issues impacting device connection, prep orders, and QR</title>
  <description>
    Type: Incident
    Duration: 3 hours and 21 minutes

    Affected Components: Payment processing, Backoffice (Reservations, Insights, Acct. Mgmt.), App (POS, KDS, Reservations) 
    May 30, 17:20:48 GMT+0 - Resolved - This issue has been resolved. All systems back to normal. May 30, 17:00:52 GMT+0 - Identified - We are seeing an increase in device loading issues again - we are continuing to work on a fix for this incident. May 30, 15:15:00 GMT+0 - Resolved - This incident has been resolved. May 30, 14:00:00 GMT+0 - Resolved - We identified an issue affecting a subset of devices from connecting to Tebi. Additionally, this caused some delays with QR ordering and prep stations. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> , , </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:encoded>
  <pubDate>Sat, 30 May 2026 14:00:00 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmpsiuk3g0aw5nplszvzvv69b</link>
  <guid>https://status.tebi.com/incident/cmpsiuk3g0aw5nplszvzvv69b</guid>
</item>

<item>
  <title>Issues impacting connection between Tebi devices</title>
  <description>
    Type: Incident
    Duration: 1 hour and 2 minutes

    Affected Components: App (POS, KDS, Reservations) 
    May 14, 13:55:58 GMT+0 - Resolved - This incident has been resolved. May 14, 13:04:53 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 14, 12:54:00 GMT+0 - Investigating - 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. 
  </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>
    <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:encoded>
  <pubDate>Thu, 14 May 2026 12:54:00 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmp5hpgvd038hqjjtvnr7aqop</link>
  <guid>https://status.tebi.com/incident/cmp5hpgvd038hqjjtvnr7aqop</guid>
</item>

<item>
  <title>Data temporarily unavailable in the Back Office Dashboard for 29 March</title>
  <description>
    Type: Incident
    Duration: 21 hours and 46 minutes

    Affected Components: Backoffice (Reservations, Insights, Acct. Mgmt.)
    Mar 31, 06:57:36 GMT+0 - Resolved - This incident has been resolved. Mar 30, 09:11:16 GMT+0 - Identified - 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.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Mon, 30 Mar 2026 09:11:16 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmncyxojq08lcj3xdmj76tmgm</link>
  <guid>https://status.tebi.com/incident/cmncyxojq08lcj3xdmj76tmgm</guid>
</item>

<item>
  <title>QR orders not being closed or sent to the prep stations &amp; pre-payments for reservations not being processed.</title>
  <description>
    Type: Incident
    Duration: 34 minutes

    Affected Components: App (POS, KDS, Reservations) 
    Mar 24, 10:18:44 GMT+0 - Resolved - 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. Mar 24, 10:06:17 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 24, 09:45:01 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Tue, 24 Mar 2026 09:45:01 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmn4fhzl307vn8le6rrl8cp17</link>
  <guid>https://status.tebi.com/incident/cmn4fhzl307vn8le6rrl8cp17</guid>
</item>

<item>
  <title>Tebi app</title>
  <description>
    Type: Incident
    Duration: 7 days and 12 hours

    Affected Components: App (POS, KDS, Reservations) 
    Feb 6, 19:30:00 GMT+0 - Resolved - This incident has been resolved. Feb 6, 16:30:00 GMT+0 - Identified - | 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. |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days and 12 hours</p>
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Fri, 6 Feb 2026 16:30:00 +0000</pubDate>
  <link>https://status.tebi.com/incident/cmmt4w0tp022s14pi6plk9fuk</link>
  <guid>https://status.tebi.com/incident/cmmt4w0tp022s14pi6plk9fuk</guid>
</item>

  </channel>
  </rss>