Tebi Status - Incident history https://status.tebi.com Tebi Tue, 23 Jun 2026 10:30:08 +0000 Negative amounts shown for payments on the day overview Type: Incident Affected Components: Backoffice (Reservations, Insights, Acct. Mgmt.), App (POS, KDS, Reservations) Jun 23, 10:30:08 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 23, 10:30:09 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components: ,

<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> <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> ]]> Tue, 23 Jun 2026 10:30:08 +0000 https://status.tebi.com/incident/cmqql0i3n09oq2omkh0nv8i6j https://status.tebi.com/incident/cmqql0i3n09oq2omkh0nv8i6j Issues impacting device connection, prep orders, and QR Type: Incident Duration: 3 hours and 21 minutes Affected Components: Payment processing, Backoffice (Reservations, Insights, Acct. Mgmt.), App (POS, KDS, Reservations) 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. May 30, 15:15:00 GMT+0 - Resolved - This incident has been resolved. 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, 17:20:48 GMT+0 - Resolved - This issue has been resolved. All systems back to normal. Type: Incident

Duration: 3 hours and 21 minutes

Affected Components: , ,

<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> <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'>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'>17:20:48</var> GMT+0</small><br><strong>Resolved</strong> - This issue has been resolved. All systems back to normal..</p> ]]> Sat, 30 May 2026 14:00:00 +0000 https://status.tebi.com/incident/cmpsiuk3g0aw5nplszvzvv69b https://status.tebi.com/incident/cmpsiuk3g0aw5nplszvzvv69b Issues impacting connection between Tebi devices Type: Incident Duration: 1 hour and 2 minutes Affected Components: App (POS, KDS, Reservations) 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. May 14, 13:04:53 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 14, 13:55:58 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components:

<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> <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'>13:55:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 14 May 2026 12:54:00 +0000 https://status.tebi.com/incident/cmp5hpgvd038hqjjtvnr7aqop https://status.tebi.com/incident/cmp5hpgvd038hqjjtvnr7aqop Data temporarily unavailable in the Back Office Dashboard for 29 March Type: Incident Duration: 21 hours and 46 minutes Affected Components: Backoffice (Reservations, Insights, Acct. Mgmt.) 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. Mar 31, 06:57:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 21 hours and 46 minutes

Affected Components:

<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> <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> ]]> Mon, 30 Mar 2026 09:11:16 +0000 https://status.tebi.com/incident/cmncyxojq08lcj3xdmj76tmgm https://status.tebi.com/incident/cmncyxojq08lcj3xdmj76tmgm QR orders not being closed or sent to the prep stations & pre-payments for reservations not being processed. Type: Incident Duration: 34 minutes Affected Components: App (POS, KDS, Reservations) 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. Mar 24, 10:06:17 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 24, 10:18:44 GMT+0 - Resolved - The technical issue affecting QR ordering & 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 "Confirmed" 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. Type: Incident

Duration: 34 minutes

Affected Components:

<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> <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'>10:18:44</var> GMT+0</small><br><strong>Resolved</strong> - The technical issue affecting QR ordering & 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 "Confirmed" 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> ]]> Tue, 24 Mar 2026 09:45:01 +0000 https://status.tebi.com/incident/cmn4fhzl307vn8le6rrl8cp17 https://status.tebi.com/incident/cmn4fhzl307vn8le6rrl8cp17 Tebi app 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'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. | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Type: Incident

Duration: 7 days and 12 hours

Affected Components:

<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'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> ]]> Fri, 6 Feb 2026 16:30:00 +0000 https://status.tebi.com/incident/cmmt4w0tp022s14pi6plk9fuk https://status.tebi.com/incident/cmmt4w0tp022s14pi6plk9fuk