Trybe Outage History

Started Oct 21, 2026, 01:51 PM UTC· resolved Oct 21, 2026, 03:05 PM UTC

1. identified Oct 21, 2026, 01:51 PM UTC

   Our engineering team was made aware of the PHP CVEs last night and has been in close contact with our infrastructure provider since then. Here is where things stand: • Patch: Our infrastructure provider will apply the security patch automatically as soon as it is released. The release is expected at 3pm UK time today (14:00 UTC). • Interim protection: The Trybe application sits behind Cloudflare. Cloudflare has deployed emergency Web Application Firewall (WAF) rules for this vulnerability, which protect us until the patch is applied. NCSC acknowledgement: https://www.ncsc.gov.uk/news/critical-security-issue-affecting-php

2. monitoring Oct 21, 2026, 03:00 PM UTC

   The security patch for the PHP vulnerability has been released and applied. All Trybe services are now running the patched version of PHP. Before the patch was released, the Trybe application was protected by emergency Web Application Firewall (WAF) rules that Cloudflare deployed for this vulnerability. We’ll keep monitoring and will mark this incident as resolved shortly. You don’t need to do anything.

3. resolved Oct 21, 2026, 03:05 PM UTC

   This has now been resolved.

4. resolved Oct 21, 2026, 03:05 PM UTC

   This has now been resolved.

Read the full incident report →

Started Oct 07, 2026, 04:01 PM UTC· resolved Oct 07, 2026, 04:31 PM UTC

1. investigating Oct 07, 2026, 04:01 PM UTC

   We're investigating reports of slower loading times in some areas of the system. We'll keep you updated.

2. identified Oct 07, 2026, 04:07 PM UTC

   We've identified the cause of slower loading times in some areas of the system and will release a fix as soon as possible.

3. monitoring Oct 07, 2026, 04:24 PM UTC

   A fix has been released. We’re monitoring the platform stability closely.

4. resolved Oct 07, 2026, 04:31 PM UTC

   The issue has been resolved. We apologise for the disruption caused.

5. resolved Oct 07, 2026, 04:31 PM UTC

   The issue has been resolved. We apologise for the disruption caused.

Read the full incident report →

Started Oct 01, 2026, 08:55 AM UTC· resolved Oct 01, 2026, 10:09 AM UTC

1. investigating Oct 01, 2026, 08:55 AM UTC

   We're investigating reports of membership payments not being triggered for this month. We will keep you updated.

2. identified Oct 01, 2026, 09:40 AM UTC

   We've identified the cause of membership payments not being triggered and will release a fix as soon as possible.

3. resolved Oct 01, 2026, 10:09 AM UTC

   The issue has been resolved. All membership payments due to be triggered today have now been triggered so the changes will be processing as usual. We apologise for the disruption caused whilst this occurred.

4. resolved Oct 01, 2026, 10:09 AM UTC

   The issue has been resolved. All membership payments due to be triggered today have now been triggered so the changes will be processing as usual. We apologise for the disruption caused whilst this occurred.

Read the full incident report →

Started Sep 30, 2026, 08:29 AM UTC· resolved Sep 30, 2026, 09:24 AM UTC

1. investigating Sep 30, 2026, 08:29 AM UTC

   We're investigating reports of incorrect booking times shown on calendar hover. Please note this is just a display issue, the booking still appears on the calendar as the correct time, it is just when hovering over the booking it shows a different time.

2. identified Sep 30, 2026, 08:41 AM UTC

   We've identified the cause and will release a fix as soon as possible.

3. monitoring Sep 30, 2026, 08:53 AM UTC

   A fix has been released on our testing environments. We’re monitoring this to ensure all is working on our testing environments before releasing across the live systems. We'll keep you updated.

4. resolved Sep 30, 2026, 09:24 AM UTC

   The issue has been resolved. Please refresh your page or log out to ensure you're on the latest version of the app. We apologise for the disruption caused.

5. resolved Sep 30, 2026, 09:24 AM UTC

   The issue has been resolved. Please refresh your page or log out to ensure you're on the latest version of the app. We apologise for the disruption caused.

Read the full incident report →

Started Sep 28, 2026, 04:01 PM UTC· resolved Sep 28, 2026, 04:09 PM UTC

1. investigating Sep 28, 2026, 04:01 PM UTC

   We're investigating some reports of Trybe not loading. We'll keep you updated.

2. identified Sep 28, 2026, 04:05 PM UTC

   We've identified the cause of Trybe not loading and will release a fix as soon as possible.

3. resolved Sep 28, 2026, 04:09 PM UTC

   The issue has been resolved, Trybe is now loading. We apologise for the disruption caused.

4. resolved Sep 28, 2026, 04:09 PM UTC

   The issue has been resolved, Trybe is now loading. We apologise for the disruption caused.

Read the full incident report →

Started Aug 27, 2026, 04:03 PM UTC· resolved Aug 28, 2026, 01:36 PM UTC

1. investigating Aug 27, 2026, 04:03 PM UTC

   We're investigating reports of Trybe not loading. Apologies for any inconvenience, we will keep you updated once we hear back

2. monitoring Aug 27, 2026, 04:16 PM UTC

   A fix has been released and we’re monitoring the platform stability closely before confirming this is fully resolved. Thanks for your patience.

3. resolved Aug 27, 2026, 04:52 PM UTC

   After monitoring the fix, we can confirm the issue has been resolved. We apologise for the disruption caused.

4. resolved Aug 28, 2026, 01:36 PM UTC

   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.

5. resolved Aug 28, 2026, 01:36 PM UTC

   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.

Read the full incident report →

Started Aug 19, 2026, 10:44 AM UTC· resolved Aug 19, 2026, 01:51 PM UTC

1. investigating Aug 19, 2026, 10:44 AM UTC

   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.

2. identified Aug 19, 2026, 11:12 AM UTC

   We've identified the cause of the issue accessing to Trybe and are working on releasing a fix as soon as possible.

3. identified Aug 19, 2026, 11:19 AM UTC

   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.

4. identified Aug 19, 2026, 11:27 AM UTC

   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.

5. identified Aug 19, 2026, 11:42 AM UTC

   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.

6. identified Aug 19, 2026, 12:19 PM UTC

   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.

7. identified Aug 19, 2026, 01:03 PM UTC

   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.

8. identified Aug 19, 2026, 01:08 PM UTC

   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.

9. identified Aug 19, 2026, 01:08 PM UTC

   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.

10. monitoring Aug 19, 2026, 01:12 PM UTC

    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.

11. monitoring Aug 19, 2026, 01:27 PM UTC

    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.

12. resolved Aug 19, 2026, 01:51 PM UTC

    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.

13. resolved Aug 19, 2026, 01:51 PM UTC

    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.

Read the full incident report →

Started Aug 19, 2026, 10:40 AM UTC· resolved Aug 19, 2026, 10:40 AM UTC

1. resolved Aug 19, 2026, 10:40 AM UTC

   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.

2. resolved Aug 19, 2026, 10:40 AM UTC

   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.

Read the full incident report →

Started Jul 07, 2026, 08:55 AM UTC· resolved Jul 08, 2026, 09:51 AM UTC

1. investigating Jul 07, 2026, 08:55 AM UTC

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

2. identified Jul 07, 2026, 09:26 AM UTC

   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.

3. identified Jul 07, 2026, 10:36 AM UTC

   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.

4. resolved Jul 08, 2026, 09:51 AM UTC

   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.

Read the full incident report →

Started Jul 02, 2026, 02:47 PM UTC· resolved Jul 02, 2026, 02:54 PM UTC

1. investigating Jul 02, 2026, 02:47 PM UTC

   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.

2. identified Jul 02, 2026, 02:52 PM UTC

   We've identified the cause of the issue and will release a fix as soon as possible.

3. resolved Jul 02, 2026, 02:54 PM UTC

   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.

Read the full incident report →

Started Jun 24, 2026, 09:36 AM UTC· resolved Jun 24, 2026, 10:00 AM UTC

1. investigating Jun 24, 2026, 09:36 AM UTC

   We're investigating reports of not being able to do the following... • Add retail products as upsells to website orders • Add retail products/ courses/ vouchers to website orders that drop into Trybe internally. We will keep you updated as soon as this is resolved. Apologies for any inconvenience.

2. identified Jun 24, 2026, 09:43 AM UTC

   We've identified the cause of the issue and will release a fix as soon as possible.

3. resolved Jun 24, 2026, 10:00 AM UTC

   The issue has been resolved. We apologise for the disruption caused.

Read the full incident report →

Started Jun 23, 2026, 12:28 PM UTC· resolved Jun 23, 2026, 01:00 PM UTC

1. investigating Jun 23, 2026, 12:28 PM UTC

   We're investigating reports of the calendar not showing any bookings for sites that are behind UTC timezone. In the meantime you can access your bookings via the Orders page and filter by item date. Apologies for any inconvenience caused.

2. identified Jun 23, 2026, 12:53 PM UTC

   We've identified the cause of the issue and will release a fix as soon as possible.

3. resolved Jun 23, 2026, 01:00 PM UTC

   The issue has been resolved. We apologise for the disruption caused. You will need to select the "Update now" button at the bottom of your screen for the fix to be released. If you have any queries please reach out to Support.

Read the full incident report →

Started May 20, 2026, 03:31 PM UTC· resolved May 20, 2026, 03:34 PM UTC

1. investigating May 20, 2026, 03:31 PM UTC

   We're investigating reports of issues logging into Trybe

2. resolved May 20, 2026, 03:34 PM UTC

   The issue has been resolved. We apologise for the disruption caused.

Read the full incident report →

Started Apr 13, 2026, 11:57 AM UTC· resolved Apr 13, 2026, 12:23 PM UTC

1. investigating Apr 13, 2026, 11:57 AM UTC

   Some users have reported that when attempting to take payment for a retail product order, an error is displayed: "Something went wrong!". This is only affecting Orders for Retail Products only. These payments are still being recorded in Trybe, but an error is being displayed. We are currently investigating this issue and apologise for any inconvenience caused.

2. resolved Apr 13, 2026, 12:23 PM UTC

   This issue has been resolved. Payments are now successfully processing again for retail product orders. We apologise for the disruption caused.

Read the full incident report →

Started Apr 10, 2026, 02:21 PM UTC· resolved Apr 10, 2026, 02:31 PM UTC

1. investigating Apr 10, 2026, 02:21 PM UTC

   We’re investigating reports of some Gantner Access Control devices not responding.

2. identified Apr 10, 2026, 02:23 PM UTC

   We’ve identified the cause of the issue and a fix is being deployed.

3. resolved Apr 10, 2026, 02:31 PM UTC

   The issue has been resolved. We apologise for the disruption caused. Gantner devices will automatically reconnect. It your Gantner device hasn't already automatically reconnected, this should happen in the next few minutes. Please reach out to our support team should you have any concerns.

Read the full incident report →

Started Apr 07, 2026, 11:20 AM UTC· resolved Apr 07, 2026, 11:54 AM UTC

1. investigating Apr 07, 2026, 11:20 AM UTC

   We're investigating reports of some April membership payments stuck in "Preparing". We'll keep you updated on this.

2. resolved Apr 07, 2026, 11:54 AM UTC

   The issue has been resolved, all April payments that were stuck in "Preparing" have now updated to "Succeeded" or "Failed" (if there was something preventing the payment being taken i.e. lack of funds).

Read the full incident report →

Started Apr 01, 2026, 02:03 PM UTC· resolved Apr 01, 2026, 04:30 PM UTC

1. investigating Apr 01, 2026, 02:03 PM UTC

   We're investigating reports of an error when making an online booking that requires no payment. The booking will still drop into your system, but the customer is not receiving the confirmation email. Apologies for any inconvenience.

2. identified Apr 01, 2026, 02:21 PM UTC

   We've identified the cause of the issue where an error is appearing when making an online booking that requires no payment. The booking will still drop into your system, but the customer is not receiving the confirmation email. We will release a fix as soon as possible. Apologies for any inconvenience.

3. investigating Apr 01, 2026, 03:30 PM UTC

   We're still investigating this with high priority. Thanks for your patience here.

4. resolved Apr 01, 2026, 04:30 PM UTC

   The issue has been resolved. We apologise for the disruption caused.

Read the full incident report →

Started Mar 24, 2026, 10:04 AM UTC· resolved Mar 24, 2026, 10:36 AM UTC

1. investigating Mar 24, 2026, 10:04 AM UTC

   We're investigating reports of no bookings appearing on the calendar if "All" is selected as the zone. If you filter by a different zone you will see your bookings. We'll keep you updated once we have any news apologies for the inconvenience.

2. identified Mar 24, 2026, 10:31 AM UTC

   We've identified the cause of the issue where no bookings are appearing on the calendar if "All" is selected as the zone. We'll let you know once this fix is released.

3. resolved Mar 24, 2026, 10:36 AM UTC

   The issue has been resolved. We apologise for the disruption caused.

Read the full incident report →

Started Mar 09, 2026, 05:24 PM UTC· resolved Mar 09, 2026, 05:46 PM UTC

1. investigating Mar 09, 2026, 05:24 PM UTC

   We're investigating reports of Trybe running slow with issues creating order, creating clients, searching and loading pages. This is raised with the tech team and we will keep you updated as soon as we have any news.

2. identified Mar 09, 2026, 05:44 PM UTC

   We've identified the cause of Trybe running slow with issues creating order, creating clients, searching and loading pages. We will let you know as soon as this is resolved.

3. resolved Mar 09, 2026, 05:46 PM UTC

   The issue has been resolved where Trybe was running slow with issues creating order, creating clients, searching and loading pages is fixed. We apologise for the disruption caused.

Read the full incident report →

Started Mar 03, 2026, 03:27 PM UTC· resolved Mar 03, 2026, 03:30 PM UTC

1. monitoring Mar 03, 2026, 03:27 PM UTC

   There were reports of customers receiving errors when making an online payment at the Shop Checkout. Our Payment provider Adyen were experiencing intermittent issues - https://status.adyen.com/ - that have since been resolved. We will be monitoring our Payment Provider until the issue has been fully resolved.

2. resolved Mar 03, 2026, 03:30 PM UTC

   The issue has been resolved as of 16:14 CET. All payment should now be going through successfully. We will continue monitoring the platform. Should you have any questions, please contact our support team.

Read the full incident report →

Started Feb 11, 2026, 09:13 AM UTC· resolved Feb 11, 2026, 09:54 AM UTC

1. investigating Feb 11, 2026, 09:13 AM UTC

   We're investigating reports of not being able to purchase a membership online. We will keep you updated when we have any news. Apologies for any inconvenience.

2. identified Feb 11, 2026, 09:29 AM UTC

   We've identified the cause of the issue where you cannot purchase a membership online and the tech team are actively working on a fix. We'll keep you updated.

3. resolved Feb 11, 2026, 09:54 AM UTC

   The issue has been resolved. Your clients will now be able to sign up to memberships online. We apologise for any disruption caused.

Read the full incident report →

Started Feb 02, 2026, 10:24 AM UTC· resolved Feb 02, 2026, 02:49 PM UTC

1. investigating Feb 02, 2026, 10:24 AM UTC

   We're investigating reports of some memberships being marked as "payment outstanding" although payment has successfully been taken. We are currently investigating this and will keep you updated once we have any news. Apologies for any inconvenience.

2. identified Feb 02, 2026, 12:10 PM UTC

   We've identified the cause of the issue where some memberships are stuck in "payment outstanding" despite payment being successfully taken. We'll let you know once this has been resolved.

3. resolved Feb 02, 2026, 02:49 PM UTC

   The issue has been resolved. We apologise for the disruption caused. Any memberships that were stuck in "payment outstanding" when payment was successfully taken have now be updated to "Active".

Read the full incident report →

Started Jan 28, 2026, 03:22 PM UTC· resolved Jan 28, 2026, 03:35 PM UTC

1. investigating Jan 28, 2026, 03:22 PM UTC

   We're investigating some reports of bookings not appearing on the calendar for some dates. This is being investigated by our tech team in the meantime please head to the Orders tab to view your orders if they are not visible on the calendar. Apologies for any inconvenience.

2. identified Jan 28, 2026, 03:27 PM UTC

   We've identified the cause of this issue and will keep you updated once this is resolved.

3. resolved Jan 28, 2026, 03:35 PM UTC

   The issue has been resolved, your bookings will now be appearing on the calendar. We apologies for the disruption caused.

Read the full incident report →

Started Jan 28, 2026, 03:00 PM UTC· resolved Jan 28, 2026, 03:29 PM UTC

1. investigating Jan 28, 2026, 03:00 PM UTC

   We're investigating reports {{symptom}} aftecting {{scope}}.

2. identified Jan 28, 2026, 03:03 PM UTC

   We've identified a fix for the error message popping up when you go to manage passes on a client profile. We will keep you updated once this is resolved.

3. resolved Jan 28, 2026, 03:29 PM UTC

   The issue has been resolved. We apologies for the disruption caused. You will now be able to head to "Manage passes" without any error.

Read the full incident report →

Started Jan 05, 2026, 02:46 PM UTC· resolved Jan 05, 2026, 03:14 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →