Is Trybe down?

Status: Investigating We're investigating reports of Trybe not loading. Apologies for any inconvenience, we will keep you updated once we hear back Affected components Platform (Degraded performance)

Status: Monitoring A fix has been released and we’re monitoring the platform stability closely before confirming this is fully resolved. Thanks for your patience. Affected components Platform (Degraded performance)

Status: Resolved After monitoring the fix, we can confirm the issue has been resolved. We apologise for the disruption caused. Affected components Platform (Operational)

Status: Resolved Summary On 27 August 2026,  the Trybe platform experienced an outage lasting approximately 19 minutes where around 75% of traffic was unable to access Trybe. No guest, booking, or other customer data was accessed, altered, or lost at any point during the incident. Impact Area What operators experienced Platform access Unable to log in to Trybe Calendars & bookings Unable to view or manage bookings Booking engine Unable to view or book offerings Timeline (BST) Time Event 16:57 Issue detected; investigation begins 16:59 Incident declared; status page updated 17:03 Root cause identified: issue was introduced in recent deployment 17:03 - 17:15 Engineers work on rolling back deployment 17:16 Service recovered; incident moved to monitoring 17:51 Incident closed Root Cause As part of a new feature being developed, a code change was introduced which performed an inefficient database query. Once deployed, it forced the database to search through a very large volume of records for each request, making every request far slower than normal. Our application servers were left waiting on those slow requests. The backlog of requests grew, and each stuck request was holding open a connection to a separate database - which eventually hit its connection limit and stopped responding entirely. The result was a full outage of the platform. Resolution Once the cause was identified, our team worked quickly to isolate the pipeline and decouple the recovery process from the affected database service. We then safely completed the rollback and stabilised the platform. We are currently performing deeper code analysis and testing a permanent resolution prior to re-deploying the feature. Preventive Measures Following this incident, we have reviewed the process that led to it and have made changes to reduce the likelihood of this happening again. The steps we have taken are: •      Our engineers’ development environments now have strict policies on queries that can be executed to help discover these issues before they reach the review stage. •      Our code review process now ensures any database queries added or modified are scrutinised specifically for performance. •      Our deployment process is no longer be dependent on a database connection. •      We are making changes so that a problem in one part of the platform cannot exhaust the resources other parts rely on. If you would like more information on the steps we're taking, please contact your account manager or [email protected]: mailto:[email protected] and we're happy to discuss this with you directly. Closing We recognise the disruption this caused to your operations and your guests, and we apologise for the inconvenience. If you have questions about this incident or its impact on your property, please contact our support team. Affected components Platform (Operational)

Status: Investigating We're investigating reports of properties being unable to access their Trybe platform which is affecting viewing and managing bookings. Our technical team are already investigating the causes of this issue to ensure access to the platform is brought back. Affected components Platform (Degraded performance) Trybe Pay (Degraded performance) API (Degraded performance)

Status: Identified We've identified the cause of the issue accessing to Trybe and are working on releasing a fix as soon as possible. Affected components Platform (Degraded performance) Trybe Pay (Degraded performance) API (Degraded performance)

Status: Identified We've identified the cause of accessing Trybe and are aware there is an issue with our hosting provider, we are working on resolving this and will release a fix as soon as possible. Affected components Platform (Partial outage) Trybe Pay (Partial outage) API (Partial outage)

Status: Identified We've identified the cause of not being able to access Trybe and are aware there is an issue with our hosting provider, we are working on resolving this and will release a fix as soon as possible. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. Affected components Platform (Partial outage) Trybe Pay (Partial outage) API (Partial outage)

Status: Identified We've identified the cause of not being able to access Trybe and are aware there is an issue with our hosting provider, we are working on resolving this and will release a fix as soon as possible. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be: http://try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. If you are experiencing issues with Gantner gates due to this issue we recommend manually setting these to open until this issue is resolved. Affected components Trybe Pay (Partial outage) API (Partial outage) Platform (Partial outage)

Status: Identified We apologise for the continued inability to access Trybe. We've identified the cause of not being able to access Trybe and are aware there is a critical issue with our hosting provider, we are working on resolving this and will release a fix as soon as possible. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be: http://try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. If you are experiencing issues with Gantner gates due to this issue we recommend manually setting these to open until this issue is resolved. Affected components Platform (Partial outage) Trybe Pay (Partial outage) API (Partial outage)

Status: Identified We apologise for the continued inability to access Trybe. Our team have identified a resolution that they are currently working on implementing as soon as possible. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be: http://try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. If you are experiencing issues with Gantner gates due to this issue we recommend manually setting these to open until this issue is resolved. Affected components Platform (Partial outage) Trybe Pay (Partial outage) API (Partial outage)

Status: Identified We apologise for the continued inability to access Trybe. Our team have identified a resolution that they are currently working on implementing as soon as possible. We are know seeing some properties regain access to the platform and we will continue implementing necessary updates to ensure this is fully resolved. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be: http://try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. If you are experiencing issues with Gantner gates due to this issue we recommend manually setting these to open until this issue is resolved. Affected components Platform (Partial outage) Trybe Pay (Partial outage) API (Partial outage)

Status: Identified We apologise for the continued inability to access Trybe. Our team have identified a resolution that they are currently working on implementing as soon as possible. We are now seeing some properties regain access to the platform and we will continue implementing necessary updates to ensure this is fully resolved. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be: http://try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. If you are experiencing issues with Gantner gates due to this issue we recommend manually setting these to open until this issue is resolved. Affected components Platform (Partial outage) Trybe Pay (Partial outage) API (Partial outage)

Status: Monitoring A fix has been released. We’re monitoring the platform stability closely. Some users may still experience inability to access Trybe while backlogs clear. We are continuing to work closely with our hosting provider to resolve the issue. Please note this may be affecting our try.be: http://try.be inbox and therefore we may not be receiving all emails sent to us. We will continue to keep you continuously updated here. If you are experiencing issues with Gantner gates due to this issue we recommend manually setting these to open until this issue is resolved. Affected components Platform (Degraded performance) Trybe Pay (Degraded performance) API (Degraded performance)

Status: Monitoring A fix has been released. We’re monitoring the platform stability closely and our latest figures indicate that the issue should be resolved, we will of course continue to monitor this before resolving this update. Affected components Platform (Degraded performance) Trybe Pay (Degraded performance) API (Degraded performance)

Status: Resolved A fix has now been released for the issue of accessing the Trybe platform, our team will continue to monitor the platform stability. We apologise for the inconvenience caused here, we will continue investigating the causes and resolutions to prevent this from occurring in the future. Affected components Platform (Operational) Trybe Pay (Operational) API (Operational)

Status: Resolved TRYBE · POST-INCIDENT REPORT Trybe Service Disruption Published: 26 August 2026 STATUS  Resolved DURATION  Approximately 4 hours (11:40–15:42 BST) IMPACT  Platform access, booking management, email delivery, and access-gate integration at a subset of properties Summary On 19 August 2026, a subset of Trybe properties experienced a service disruption lasting approximately four hours. The disruption was caused by an issue with the DNS configuration of the try.be: http://try.be domain, rather than any fault within the Trybe application or its underlying infrastructure. Access was fully restored the same day. No guest, booking, or other customer data was accessed, altered, or lost at any point during the incident. Impact Area: What operators experienced Platform access Unable to log in to Trybe Calendars & bookings Unable to view or manage bookings Email Inbound and outbound email via try.be: http://try.be addresses were delayed Recovery was staggered across properties. This is expected behaviour for a DNS-related issue: once a fix is applied, individual networks refresh their cached DNS records at different times, so some operators regained access sooner than others. Timeline (BST) Time Event 11:40 Issue detected; investigation begins 11:44 Incident declared; status page updated ~12:10 Root cause identified: DNS delegation for try.be: http://try.be had been suspended 13:59 DNS delegation restored; fix deployed 14:27 Service confirmed recovered; team moves to monitoring 15:42 Incident closed Root Cause As part of routine compliance checks, domain registries periodically verify that registrant contact details are accurate and up to date. In this case, a contact-verification check failed because the registrant details had not been kept current by our registrant, and the registry suspended DNS delegation for try.be: http://try.be as a result. Resolution Once the cause was identified, our team worked directly with our domain registrar to verify the correct contact information and restore DNS delegation. A fix was deployed the same day, and normal service resumed for affected properties, with full recovery confirmed through monitoring shortly after. Preventive Measures Following this incident, we have reviewed the process that led to it and have made changes so this specific issue cannot recur. We continue to invest in the monitoring, resilience and operational practices that keep Trybe reliable, and this incident has directly informed that ongoing work.  If you would like more information on the steps we're taking, please contact your account manager or [email protected]: mailto:[email protected] and we're happy to discuss this with you directly. Closing We recognise the disruption this caused to your operations and your guests, and we apologise for the inconvenience. If you have questions about this incident or its impact on your property, please contact our support team.

Status: Investigating We're investigating reports of "This order contains future items." error message popping up when it shouldn't be which is preventing check out.

Status: Identified We've identified the cause of "This order contains future items." popping up when it shouldn't be which is preventing check out. This will only pop up for bookings that haven't passed their end time yet as soon as the end time is passed you'll be able to check out. We'll keep you updated once the fix is released so that you can check out the order as soon as the item has started.

Status: Identified We've released an initial fix for order checkout: • :white_check_mark: You can now check out an order if all items in it have started. • :warning: If any item hasn't started yet (based on its scheduled time), checkout will still be blocked. Coming next: The team is working on a further update to restore checkout based on the date of the last order item, regardless of time. We'll post another update once this is live.

Status: Resolved The issue has been resolved. The tech team have now released a fix so now you'll be able to checkout the order based on the date of the last order item in the order, regardless of time (whether the item has started or not yet). We apologise for the disruption caused.

Status: Investigating We're investigating reports of issues accessing Trybe and server errors. This seems to also be affecting the shop front. Apologies for any inconvenience. We'll keep you updated. Affected components Platform (Partial outage)

Status: Identified We've identified the cause of the issue and will release a fix as soon as possible. Affected components Platform (Partial outage)

Status: Resolved The issue has been resolved. We apologise for the disruption caused. Please refresh your page or log out and back in to ensure you're on the newest version of the app. Affected components Platform (Operational)