OnceHub Outage History

Started Jun 12, 2025, 09:38 PM UTC· resolved Jun 12, 2025, 09:38 PM UTC

1. postmortem Jun 12, 2025, 09:38 PM UTC

   INCIDENT REPORT : At approximately 18:08 UTC, we began receiving reports of Google Meet issues. Further investigation revealed a broader outage, caused by simultaneous upstream issues with Cloudflare, Microsoft Azure, and AWS—that also impacted booking creation, image loading on Booking calendars, Zapier automations, and our status page updates. During the incident: Booking Creation: Attempts to schedule new meetings sometimes failed or returned errors. Calendar Images: Booking calendar thumbnails did not render on customer-facing pages. Zapier Automations: Workflows triggered by our Zapier integration experienced timeouts or errors. Status Page: Real-time incident notifications were delayed. Our team closely monitored the service provider status feeds and system logs throughout. The incident was resolved at 21:05 UTC and we can confirm that booking creation, calendar images, automations, and status page updates are now working normally. If you continue to experience any issues, please contact us at [email protected].

Read the full incident report →

Started May 30, 2025, 11:48 AM UTC· resolved Jun 16, 2025, 06:16 PM UTC

1. investigating May 30, 2025, 11:48 AM UTC

   ISSUE DETECTED: We've identified a Microsoft-side issue preventing some Users from connecting or reconnecting their Microsoft 365 calendar to OnceHub. In some cases, Users have worked around this issue by connecting via a private browser window. We're working with Microsoft to resolve this urgently.

2. monitoring May 30, 2025, 04:06 PM UTC

   ISSUE UPDATE: We're continuing to work closely with Microsoft to resolve an issue on their side that's affecting some users' ability to connect or reconnect their Microsoft 365 calendars to OnceHub. We'll share further updates as soon as they become available.

3. monitoring May 30, 2025, 08:17 PM UTC

   ISSUE UPDATE: We’re still working in close collaboration with Microsoft to resolve the ongoing issue on their end that is affecting some users’ ability to connect or reconnect their Microsoft 365 calendars to OnceHub. We appreciate your patience and will share additional updates as soon as they are available.

4. monitoring May 31, 2025, 12:32 AM UTC

   ISSUE UPDATE: We're still actively working with Microsoft to resolve the ongoing issue on their end that’s affecting some user's ability to connect or reconnect their Microsoft 365 calendars to OnceHub. We’ll continue to post updates as soon as more information becomes available.

5. monitoring May 31, 2025, 06:30 AM UTC

   ISSUE UPDATE: The Microsoft-side issue affecting some users' ability to connect or reconnect Microsoft 365 calendars to OnceHub is still ongoing. We're continuing to work closely with Microsoft and will share further updates as soon as they become available.

6. monitoring May 31, 2025, 10:51 AM UTC

   ISSUE UPDATE: We're still working with Microsoft to resolve the issue affecting some users' ability to connect/reconnect their Microsoft 365 calendars to OnceHub. We appreciate your patience and we will share further updates as soon as they become available.

7. monitoring May 31, 2025, 03:00 PM UTC

   ISSUE UPDATE: The Microsoft issue preventing some Users from connecting or reconnecting their Microsoft 365 calendar is ongoing. We're continuing to investigate this with Microsoft and will provide updates as they become available.

8. monitoring May 31, 2025, 07:01 PM UTC

   ISSUE UPDATE: We're continuing to work closely with Microsoft to resolve an issue on their side that's affecting some users' ability to connect or reconnect their Microsoft 365 calendars to OnceHub. We'll share further updates as soon as they become available.

9. monitoring Jun 01, 2025, 11:37 AM UTC

   ISSUE UPDATE: We are still working with Microsoft to investigate and identify the root cause of the issue preventing some Users from connecting and reconnecting their Microsoft 365 calendars. We'll post further updates as they become available.

10. monitoring Jun 01, 2025, 03:54 PM UTC

    ISSUE UPDATE: We are continuing to work with Microsoft to investigate and determine the root cause of the issue affecting some users who are unable to connect or reconnect their Microsoft 365 calendars. We will share further updates as soon as they become available.

11. monitoring Jun 01, 2025, 09:09 PM UTC

    ISSUE UPDATE: We are actively working with Microsoft to investigate and identify the root cause of the issue impacting some users who are unable to connect or reconnect their Microsoft 365 calendars. We will provide additional updates as soon as new information is available.

12. monitoring Jun 02, 2025, 03:30 AM UTC

    ISSUE UPDATE: We are actively working with Microsoft to investigate and identify the root cause of the issue impacting some users who are unable to connect or reconnect their Microsoft 365 calendars. We will provide additional updates as soon as new information is available.

13. monitoring Jun 02, 2025, 08:40 AM UTC

    ISSUE UPDATE: Our team continues to work closely with Microsoft to investigate the root cause of the issue preventing some users from connecting or reconnecting their Microsoft 365 calendars. We will provide additional updates as soon as new information becomes available.

14. monitoring Jun 02, 2025, 08:40 AM UTC

    ISSUE UPDATE: Our team continues to work closely with Microsoft to investigate the root cause of the issue preventing some users from connecting or reconnecting their Microsoft 365 calendars. We will provide additional updates as soon as new information becomes available.

15. monitoring Jun 02, 2025, 12:40 PM UTC

    ISSUE UPDATE: We are actively working with Microsoft to investigate and identify the root cause of the issue impacting some users who are unable to connect or reconnect their Microsoft 365 calendars. We will provide additional updates as soon as new information is available.

16. monitoring Jun 02, 2025, 07:40 PM UTC

    ISSUE UPDATE: We are actively monitoring the issue preventing some users from connecting or reconnecting to Microsoft 365 after reporting it to Microsoft. We will provide additional updates as soon as new information is available.

17. monitoring Jun 03, 2025, 04:28 AM UTC

    ISSUE UPDATE: Our Development team is actively monitoring the issue preventing some Users from connecting or reconnecting to Microsoft 365 after reporting it to Microsoft. We will provide additional updates as soon as new information is available.

18. monitoring Jun 03, 2025, 11:28 AM UTC

    ISSUE UPDATE: We have identified a possible workaround for the issue preventing some Users connecting or reconnecting their Microsoft 365 calendars. We are working on implementing this workaround and will provide updates as they become available.

19. monitoring Jun 03, 2025, 06:29 PM UTC

    ISSUE UPDATE: We are still working on implementing a workaround for the issue preventing some Users connecting or reconnecting their Microsoft 365 calendars. We will share further updates as they become available.

20. monitoring Jun 04, 2025, 07:43 AM UTC

    ISSUE UPDATE: In continuation to our prevoius update, we are still working on implementing a workaround for the issue preventing some Users connecting or reconnecting their Microsoft 365 calendars. We will share further updates as they become available.

21. monitoring Jun 04, 2025, 02:54 PM UTC

    ISSUE UPDATE: We are making progress on the workaround for the issue preventing some Users connecting or reconnecting their Microsoft 365 calendars. We hope to release it soon. We will provide more updates as they become available.

22. monitoring Jun 05, 2025, 12:00 AM UTC

    ISSUE UPDATE: We’re continuing to make good progress on the workaround for the issue affecting some Users when connecting or reconnecting their Microsoft 365 calendars. Our team is actively testing the solution to ensure it resolves the problem reliably. We’re aiming to release the fix shortly and will share another update as soon as it becomes available. Thank you for your continued patience — we really appreciate it!

23. monitoring Jun 05, 2025, 08:58 AM UTC

    ISSUE UPDATE: The Microsoft issue where Users could not connect or reconnect their Microsoft 365 calendar is now resolved. However, users who have connected their Microsoft 365 calendar with OnceHub may experience issues with Microsoft Teams not functioning correctly due to a known issue on Microsoft's end. Our development team is actively working on a workaround. We'll provide further updates as they become available.

24. monitoring Jun 05, 2025, 06:01 PM UTC

    ISSUE UPDATE: Users who use our Microsoft Teams integration may experience an issue where their Teams license is not recognized due to an error on Microsoft’s side. Our development team is actively working on a workaround for this issue. We will provide further updates as they become available.

25. monitoring Jun 05, 2025, 11:42 PM UTC

    ISSUE UPDATE: We're continuing to work on a workaround for the issue where Microsoft Teams licenses are not being recognized due to an error on Microsoft’s end. Our development team is actively testing a solution to ensure stability before release. We appreciate your patience and will provide further updates as they become available.

26. monitoring Jun 06, 2025, 11:15 AM UTC

    ISSUE UPDATE: We’re actively working on a workaround for the issue where Microsoft Teams licenses aren’t being recognized, caused by an error on Microsoft’s side. Our development team is currently testing a potential solution to ensure it’s stable before rollout. We appreciate your continued patience and will share more updates as they become available.

27. monitoring Jun 06, 2025, 07:03 PM UTC

    ISSUE UPDATE: We are still experiencing an issue recognizing Microsoft Teams licenses in some cases due to an error on Microsoft's side. Our development team is still testing a potential fix to ensure its stability before deployment. We appreciate your ongoing patience and will provide further updates as soon as they become available.

28. monitoring Jun 07, 2025, 02:02 AM UTC

    ISSUE UPDATE: We’re continuing to experience an issue where Microsoft Teams licenses may not be recognized due to an error on Microsoft’s side. Our development team is actively working on a stable workaround and we'll share further updates as they become available.

29. monitoring Jun 07, 2025, 09:06 AM UTC

    ISSUE UPDATE: The issue where Microsoft Teams licenses may not be recognized due to an error on Microsoft’s side is ongoing. Our development team is actively testing a potential workaround and we'll provide further updates as they become available.

30. monitoring Jun 07, 2025, 11:43 PM UTC

    ISSUE UPDATE: We're continuing to address the Microsoft Teams license recognition issue caused by an error on Microsoft’s side. Our development team is actively working on a stable workaround and we’ll share further updates as they become available.

31. monitoring Jun 08, 2025, 08:00 AM UTC

    ISSUE UPDATE: We're still working on a workaround for the Microsoft Teams license issue caused by an error on Microsoft’s side. Our team is actively testing a solution to ensure stability before release. We'll share further updates as they become available.

32. monitoring Jun 08, 2025, 03:16 PM UTC

    ISSUE UPDATE: We are still experiencing an issue recognizing Microsoft Teams licenses due to an error on Microsoft's side. Our development team is continuing to test a fix to ensure its stability before deployment. We will provide further updates as they are available.

33. monitoring Jun 08, 2025, 10:07 PM UTC

    ISSUE UPDATE: We're still experiencing an issue where Microsoft Teams licenses may not be recognized due to a Microsoft-side error. Our development team is actively testing a possible solution. We will continue to provide further updates as they are available.

34. monitoring Jun 09, 2025, 07:01 AM UTC

    ISSUE UPDATE: We're still experiencing an issue where Microsoft Teams licenses may not be recognized due to a Microsoft-side error. Our development team is actively testing a possible solution. We will continue to provide further updates as they are available.

35. monitoring Jun 09, 2025, 02:55 PM UTC

    ISSUE UPDATE: We are still experiencing an issue recognizing Microsoft Teams licenses due to an error on Microsoft's side. Our development team is continuing to work on a possible solution. We'll provide further updates as they are available.

36. monitoring Jun 10, 2025, 03:03 PM UTC

    ISSUE UPDATE: We're still experiencing an issue recognizing Microsoft Teams licenses due to an error on Microsoft's side. Our development team is continuing to work on a possible solution. We will share further updates as they are available.

37. monitoring Jun 11, 2025, 03:02 PM UTC

    ISSUE UPDATE: We are continuing to experience an issue with recognizing Microsoft Teams licenses due to an error on Microsoft's side. Our development team is still working on a possible solution. We will share further updates as they are available.

38. monitoring Jun 12, 2025, 02:59 PM UTC

    ISSUE UPDATE: We are still encountering an issue with detecting Microsoft Teams licenses, due to an error on Microsoft's end. Our development team is actively working on a potential solution, and we will provide further updates as they become available.

39. resolved Jun 16, 2025, 06:16 PM UTC

    ISSUE RESOLVED: The multi-provider outage affecting Google, Zapier, and other services has been fully resolved. We have monitored the situation and confirmed that there has been no further impact of the outage after it was resolved. If you continue to experience any issues, please contact our support team at [email protected].

Read the full incident report →

Started May 23, 2025, 11:00 AM UTC· resolved May 23, 2025, 11:15 AM UTC

1. investigating May 23, 2025, 11:00 AM UTC

   ISSUE DETECTED: We’re currently seeing an issue where Zapier's Find/Search actions are not showing expected fields in the Editor, which may affect creating new Zaps. Existing Zaps continue to work but creating new Zaps may fail due to missing fields. We are actively monitoring the situation and will share updates as they become available. For real-time updates, please visit: https://status.zapier.com/

2. resolved May 23, 2025, 11:15 AM UTC

   ISSUE RESOLVED: Zapier has resolved the issue affecting the Find/Search actions in the Editor. All Zaps are now working as expected, and you should be able to create new Zaps without any issues. If you continue to experience problems or need assistance, feel free to contact us at [email protected].

Read the full incident report →

Started May 13, 2025, 06:16 PM UTC· resolved May 13, 2025, 10:06 PM UTC

1. investigating May 13, 2025, 06:16 PM UTC

   INCIDENT DETECTED: We have detected an issue where users may intermittently see a “Page not found” error when accessing Booking Hub links. Refreshing the page may allow it to load correctly. Our development team is investigating the root cause and working on a fix. We are monitoring the situation closely and will provide updates here as soon as we have more information.

2. monitoring May 13, 2025, 07:30 PM UTC

   INCIDENT UPDATE: We are still working on a fix for the intermittent “Page not found” error when accessing Booking Hub links with the relevant service provider. Through our investigation, we discovered that this issue also impacts Booking Calendars. In the meantime, we recommend working around this issue by replacing "https://oncehub.com/" with "https://page.oncehub.com/" for any Booking Hub or Booking Calendar links.

3. resolved May 13, 2025, 10:06 PM UTC

   ISSUE RESOLVED : The intermittent “Page not found” error affecting Booking Hub and Booking Calendars links has been resolved by our relevant service provider. All links are now working as expected. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started May 10, 2025, 04:58 AM UTC· resolved May 10, 2025, 05:14 AM UTC

1. investigating May 10, 2025, 04:58 AM UTC

   SCHEDULED MAINTENANCE: OnceHub platform will undergo scheduled infrastructure updates starting at 1:00 AM US EST on Saturday, May 10th, 2025. User side may experience brief intermittent issues (about 5 minutes), but there will be no impact on customers side.

2. resolved May 10, 2025, 05:14 AM UTC

   SCHEDULED MAINTENANCE COMPLETE: 1:13 AM US EST, Saturday, May 10th, 2025. The update is now complete and the OnceHub platform is working as expected. If you continue to experience any issues, please report them to [email protected].

Read the full incident report →

Started May 07, 2025, 05:21 AM UTC· resolved May 07, 2025, 05:21 AM UTC

1. resolved May 07, 2025, 05:21 AM UTC

   INCIDENT RESOLVED — 12:52 AM to 1:02 AM Wednesday, Eastern Time: We experienced a brief issue where messages were intermittently failing to send on the Chatbots, and some Users may have been unable to proceed beyond the initial interaction. Our team quickly investigated and resolved the problem. The disruption lasted for approximately 10 minutes, and all systems are now functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started May 07, 2025, 05:21 AM UTC· resolved May 07, 2025, 05:21 AM UTC

1. resolved May 07, 2025, 05:21 AM UTC

   INCIDENT UPDATE — 12:52 AM to 1:02 AM Wednesday, Eastern Time: We experienced a brief issue where messages were intermittently failing to send on the Chatbots, and some Users may have been unable to proceed beyond the initial interaction. Our team quickly investigated and resolved the problem. The disruption lasted for approximately 10 minutes, and all systems are now functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started Apr 16, 2025, 07:41 PM UTC· resolved Apr 16, 2025, 09:49 PM UTC

1. investigating Apr 16, 2025, 07:41 PM UTC

   ISSUE DETECTED: Users have reported issues when trying to schedule Zoom meetings through OnceHub or trying to connect/reconnect Zoom. This is caused by an outage on Zoom's side, which they have posted about here: https://status.zoom.us/. We will post further updates as they become available. In the meantime, as our Zoom integration will not work as expected, we recommend using a static Zoom link or a different conferencing service.

2. resolved Apr 16, 2025, 09:49 PM UTC

   ISSUE RESOLVED : The Zoom outage that was preventing meeting scheduling and Zoom connection in OnceHub has been resolved. Users can now schedule Zoom meetings and connect or reconnect their Zoom account without issue. If you encountered errors earlier, please reconnect Zoom in your OnceHub settings. If you continue to experience problems, don’t hesitate to contact us at [email protected].

Read the full incident report →

Started Apr 14, 2025, 07:37 AM UTC· resolved Apr 14, 2025, 07:42 AM UTC

1. investigating Apr 14, 2025, 07:37 AM UTC

   SCHEDULED MAINTENANCE: OnceHub platform will undergo a planned backend upgrade starting at 3:35 AM US Eastern Time, Monday, April 15th, 2025. The maintenance is expected to cause a brief interruption—approximately 2 minutes—in access to all customer-facing booking pages, chatbots, and forms. We will provide updates as they become available. Thank you for your understanding and patience.

2. resolved Apr 14, 2025, 07:42 AM UTC

   MAINTENANCE COMPLETED: The scheduled maintenance on the OnceHub platform has been successfully completed. The maintenance lasted approximately 2 minutes. The OnceHub platform, including customer-facing booking links, chatbots, and routing forms, is now fully operational.If you continue to experience any issues, please report them to [email protected]. Thank you for your patience.

Read the full incident report →

Started Apr 04, 2025, 06:32 PM UTC· resolved Apr 04, 2025, 08:58 PM UTC

1. investigating Apr 04, 2025, 06:32 PM UTC

   ISSUE DETECTED: Users who use our legacy Salesforce integration for Booking Pages may experience issues when scheduling meetings. To resolve this, Users will need to map the OnceHub 'Duration' field to the Salesforce 'Duration in Minutes' field on the Salesforce Event object and map the OnceHub 'Starting Date and Time in Owner's Time Zone' field to the Salesforce 'ActivityDateTime' field on the Salesforce Event object. Please reach out to us at [email protected] if you need assistance with these steps. For more information, please refer to this article: https://help.oncehub.com/help/mapping-scheduleonce-fields-to-non-mandatory-salesforce-fields We are investigating to determine if any changes in OnceHub caused this issue. We will continue to provide updates as they become available.

2. monitoring Apr 04, 2025, 07:34 PM UTC

   ISSUE UPDATE: Our developers have identified the root cause of the issue with our legacy Salesforce integration for Booking Pages and are working on a fix. Please do not make any of the previously suggested changes to the Salesforce mapping. We will post an update as soon as this fix is implemented.

3. resolved Apr 04, 2025, 08:58 PM UTC

   ISSUE RESOLVED: Our development team has fixed the issue with the legacy Salesforce integration for Booking Pages. Please remove any fields which were manually added as part of the previous workaround. Incase of any queries, please reach out to us at [email protected]

Read the full incident report →

Started Apr 03, 2025, 08:24 PM UTC· resolved Apr 03, 2025, 09:34 PM UTC

1. investigating Apr 03, 2025, 08:24 PM UTC

   Issue Detected: We have identified an issue affecting overall platform performance. Users may experience difficulties while scheduling meetings, loading the platform, receiving notifications, and retrieving data via API calls. Our team is actively investigating the root cause and working on a resolution. We will post further updates as they become available.

2. resolved Apr 03, 2025, 09:34 PM UTC

   ISSUE RESOLVED: The issue impacting platform performance has been resolved. Users should no longer face any difficulties while scheduling meetings or using any other functionalities. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Apr 03, 2025, 07:34 PM UTC· resolved Apr 03, 2025, 09:33 PM UTC

1. investigating Apr 03, 2025, 07:34 PM UTC

   ISSUE DETECTED: We have identified an issue which may cause slow loading times or a temporary connection error when meetings are being scheduled. Our development team is actively investigating the root cause and working on a resolution.

2. monitoring Apr 03, 2025, 08:23 PM UTC

   ISSUE UPDATE: The ongoing issue appears to be affecting overall platform performance. Users may experience difficulties while scheduling meetings, loading the platform, receiving notifications, and retrieving data via API calls. Our team is actively investigating the root cause and working on a resolution. We will post further updates as they become available.

3. resolved Apr 03, 2025, 09:33 PM UTC

   ISSUE RESOLVED: The issue impacting platform performance has been resolved. Users should no longer face any difficulties while scheduling meetings or using any other functionalities. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Mar 24, 2025, 02:03 PM UTC· resolved Mar 24, 2025, 02:22 PM UTC

1. investigating Mar 24, 2025, 02:03 PM UTC

   ISSUE DETECTED: The OnceHub Developer Center (https://developers.oncehub.com/) is currently inaccessible due to an unexpected issue. Our team is actively investigating this with the highest priority and we will provide an update as soon as possible.

2. resolved Mar 24, 2025, 02:22 PM UTC

   ISSUE RESOLVED: The issue with the OnceHub Developer Center (https://developers.oncehub.com/) has been resolved. Please reach out to us at [email protected] if you face any further issues.

Read the full incident report →

Started Mar 21, 2025, 05:33 AM UTC· resolved Mar 21, 2025, 05:33 AM UTC

1. postmortem Mar 21, 2025, 05:33 AM UTC

   ISSUE UPDATE: We're still actively working on the Office 365 integration issues impacting MS Teams links and Skype events. Our team is making progress towards a resolution. We will continue to provide updates as we have more information.

Read the full incident report →

Started Mar 20, 2025, 01:49 PM UTC· resolved Mar 21, 2025, 11:37 AM UTC

1. investigating Mar 20, 2025, 01:49 PM UTC

   ISSUE DETECTED: We identified an issue affecting Office 365 accounts where Teams links may be missing from meetings created via Bookings calendars, and Skype-enabled meetings may result in the creation of temporary meetings. We are working on a fix & will provide updates shortly.

2. monitoring Mar 20, 2025, 03:35 PM UTC

   ISSUE UPDATE : We are still experiencing the issue affecting Office 365 accounts, where Teams links may be missing from meetings created via Bookings calendars, and Skype-enabled meetings may generate temporary calendar events. Our team is actively working on a resolution, and we will share updates as they become available.

3. monitoring Mar 20, 2025, 09:40 PM UTC

   ISSUE UPDATE : We are actively investigating the issue affecting Office 365 accounts, where video conferencing links for MS Teams may be missing, and Skype enabled meetings may generate temporary calendar events. Our team is working on a resolution, and we will provide updates as soon as they become available.

4. resolved Mar 21, 2025, 11:37 AM UTC

   ISSUE RESOLVED: The issue with Booking Calendars that was preventing Teams meetings from being created properly and causing Skype meetings to create temporary calendar events has been resolved. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Mar 19, 2025, 06:44 PM UTC· resolved Mar 19, 2025, 09:32 PM UTC

1. investigating Mar 19, 2025, 06:44 PM UTC

   ISSUE DETECTED: We have identified an issue where webhooks are not being processed immediately. Our team is actively working on resolving this. We will provide updates as they become available.

2. resolved Mar 19, 2025, 09:32 PM UTC

   ISSUE RESOLVED : The issue causing delays in webhook processing has been resolved. Our team implemented the necessary fixes and monitored the system to ensure stability. Webhooks are now processing as expected. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Mar 19, 2025, 04:41 PM UTC· resolved Mar 19, 2025, 04:41 PM UTC

1. resolved Mar 19, 2025, 04:41 PM UTC

   ISSUE RESOLVED: We identified an issue where webhooks to Make.com were not being processed. We have resolved the issue and all pending webhooks have been processed. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Mar 07, 2025, 06:50 PM UTC· resolved Mar 07, 2025, 07:12 PM UTC

1. investigating Mar 07, 2025, 06:50 PM UTC

   ISSUE DETECTED: We have received reports of webhooks to make.com not being triggered. We are looking into this issue to find the cause and implement a fix. We will post further updates as soon as possible. For any questions about this issue, please reach out to us at [email protected]

2. resolved Mar 07, 2025, 07:12 PM UTC

   ISSUE RESOLVED: The issue affecting webhooks to Make.com has been successfully resolved and all pending webhooks have now been processed. We appreciate your patience while we worked on this. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Feb 20, 2025, 05:54 AM UTC· resolved Feb 20, 2025, 08:14 AM UTC

1. investigating Feb 20, 2025, 05:54 AM UTC

   ISSUE DETECTED: Our Developer Center (https://developers.oncehub.com/) is currently unavailable due to an unexpected issue. Our team is actively investigating this with the highest priority. We will provide further updates here as soon as possible. Thank you for your patience.

2. resolved Feb 20, 2025, 08:14 AM UTC

   ISSUE RESOLVED: The issue affecting our Developer Center (https://developers.oncehub.com) has been resolved, and the site is now fully accessible. If you experience any further issues, please contact us at [email protected].

Read the full incident report →

Started Feb 19, 2025, 12:33 AM UTC· resolved Feb 19, 2025, 01:21 AM UTC

1. investigating Feb 19, 2025, 12:33 AM UTC

   ISSUE DETECTED: Our developer center (https://developers.oncehub.com/) is currently unavailable due to an issue with the ReadMe.com server. We are actively investigating this with the highest priority and will post further updates here. You may check: https://www.readmestatus.com

2. resolved Feb 19, 2025, 01:21 AM UTC

   ISSUE RESOLVED: The issue that caused our Developer Center (https://developers.oncehub.com/) to be unavailable due to a problem with the ReadMe.com server has now been resolved. The site is fully accessible again. If you experience any further issues, please reach out to our support team at [email protected].

Read the full incident report →

Started Feb 15, 2025, 07:26 AM UTC· resolved Feb 16, 2025, 06:01 AM UTC

1. investigating Feb 15, 2025, 07:26 AM UTC

   ISSUE DETECTED: We’re aware that some users are unable to establish new connections to the OnceHub Infusionsoft integration or that existing Users of this integration are unable to accept bookings. Our team is actively investigating this and we’ll provide updates as soon as we have more information. We appreciate your patience and understanding.

2. monitoring Feb 15, 2025, 07:48 AM UTC

   ISSUE UPDATE: We are investigating an issue preventing some users from connecting to Infusionsoft in OnceHub, which may also affect bookings through Infusionsoft-connected Booking pages. As a workaround, we recommend disconnecting Infusionsoft in OnceHub to allow bookings. We'll post further updates as they become available.

3. monitoring Feb 15, 2025, 02:54 PM UTC

   ISSUE UPDATE: We are working with Keap to determine the root cause of the Infusionsoft integration connection issue. As a workaround for Users previously connected, we recommend disconnecting Infusionsoft in OnceHub to allow bookings. We'll post further updates as they become available.

4. monitoring Feb 16, 2025, 03:00 AM UTC

   ISSUE UPDATE: We have raised a support ticket with Infusionsoft (Keap) and are actively working with their team to resolve the connection issue affecting OnceHub users. As a workaround, we recommend disconnecting Infusionsoft in OnceHub to allow bookings. We’ll share further updates as they become available.

5. resolved Feb 16, 2025, 06:01 AM UTC

   ISSUE RESOLVED: The Infusionsoft (Keap) connection issue in OnceHub has been fixed. Affected users in an error state have been reconnected from the backend and bookings should now work as expected. If you still any face issues, please contact us at [email protected].

Read the full incident report →

Started Feb 13, 2025, 08:07 AM UTC· resolved Feb 13, 2025, 08:07 AM UTC

1. resolved Feb 13, 2025, 08:07 AM UTC

   ISSUE RESOLVED: The issue affecting webhooks to Make.com has been successfully resolved and all pending webhooks have now been triggered. We appreciate your patience while we worked on this. If you experience any further issues, please reach out to us at [email protected].

Read the full incident report →

Started Feb 08, 2025, 11:03 AM UTC· resolved Feb 08, 2025, 03:20 PM UTC

1. investigating Feb 08, 2025, 11:03 AM UTC

   ISSUE DETECTED: We've found an issue preventing some Users from performing any actions in their accounts after logging in via mobile. As a temporary workaround, impacted Users can access OnceHub on desktop. Our team is actively working to resolve this and we will share updates as soon as more information becomes available. Thank you for your patience.

2. monitoring Feb 08, 2025, 12:19 PM UTC

   ISSUE UPDATE: We're continuing to investigate the issue preventing some Users from performing actions in their accounts after logging in via mobile. A fix is in progress. In the meantime, affected Users can access their accounts on desktop as a workaround. Updates to follow.

3. resolved Feb 08, 2025, 03:20 PM UTC

   ISSUE RESOLVED: The issue preventing some Users from performing actions in their OnceHub accounts after logging in via mobile has now been resolved. If you continue to experience any issues, please contact us at [email protected] for further assistance.

Read the full incident report →

Started Feb 02, 2025, 11:42 PM UTC· resolved Feb 02, 2025, 11:54 PM UTC

1. investigating Feb 02, 2025, 11:42 PM UTC

   INCIDENT DETECTED: We have identified an issue preventing the Chatbots and Routing Form from loading beyond the initial interaction. Our team is actively working to resolve this, and we will provide updates as soon as more information becomes available. Thank you for your patience.

2. resolved Feb 02, 2025, 11:54 PM UTC

   ISSUE RESOLVED: The issue preventing Chatbots and the Routing Form from loading beyond the initial interaction has been resolved. Full functionality has been restored. Thank you for your patience.

Read the full incident report →

Started Jan 28, 2025, 06:59 PM UTC· resolved Jan 29, 2025, 07:55 AM UTC

1. investigating Jan 28, 2025, 06:59 PM UTC

   ISSUE DETECTED: We’ve received reports of users encountering a 404 error when trying to access the 'User Notifications' section in their User profile. If you see this error, this section is not relevant to your account and all User notifications settings for your account are set on your Booking pages. We are currently working on a fix for this issue. For any questions about this issue, please reach out to us at [email protected]

2. monitoring Jan 28, 2025, 11:41 PM UTC

   ISSUE UPDATE: We're continuing to investigate the issue causing a 404 error when accessing the 'User Notifications' section in User profiles. Please note that this section is not relevant to your account, as all User notification settings are managed on your individual Booking pages. Our team is actively working on a resolution, and we will post updates as soon as they are available. For any questions, feel free to contact us at [email protected]

3. monitoring Jan 29, 2025, 05:46 AM UTC

   ISSUE UPDATE: We are continuing to investigate the 404 error affecting access to the 'User Notifications' section in User profiles. This section is not applicable to your account, as all User notification settings are managed on your Booking pages. Our team is working on a fix, and we will share updates as soon as they are available. If you have any questions, please reach out to us at [email protected]

4. resolved Jan 29, 2025, 07:55 AM UTC

   ISSUE RESOLVED: The issue causing the 404 error when accessing the "User Notifications" section in User profiles has now been resolved. If you continue to face any issues, please contact us at [email protected] for further assistance.

Read the full incident report →