Coconut Software had 21 outages in the last 2 years totaling 1001h 38m of downtime — averaging 0.9 incidents per month.
There were 21 Coconut Software outages since August 9, 2024 totaling 1001h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
Help Center links populated through the Coconut Support messaging widget may intermittently show an error when clicked. If this occurs, clicking Help Information, and then through to the Help Center will resolve the error. Our team is investigating a resolution.
This incident has been resolved.
On April 27, 2026, some customers using the Microsoft Teams integration experienced failures when creating or updating Teams meeting links from Coconut. A recent configuration change to the integration caused Microsoft to report missing administrator consent, which prevented new Teams links from being generated. Once identified, we reverted the change and backfilled affected appointments with valid Teams links, fully restoring service.
Our ticketing system, Intercom, is experiencing a period of latency following a cloud service provider outage earlier today. This is affecting our ability to recieve tickets, both via email and messenger, and our response times. We will post more updates as they become available.
The latency affecting our ticketing system (Intercom) following a cloud service provider outage earlier today has now been resolved. Ticket delivery via email and messenger has returned to normal, and response times are no longer impacted. Thank you for your patience.
We are currently investigating intermittent errors affecting our application. Our team is actively working to identify and resolve the root cause. We’ll update you here as soon as we have more information.
A fix has been implemented. Our engineering team is currently monitoring the recent changes and we will continue to provide updates through this page.
Although a fix has been implemented, users may still experience brief service interruptions while our team continues to monitor changes. We'll provide updates here as soon as more information becomes available.
We're continuing to monitor the situation, but users should no longer be experiencing errors or latency.
A fix has been implemented and performance should continue to improve. We are actively monitoring to ensure stability.
This incident has been resolved.
We are currently experiencing delays in email notifications being sent to clients. Our team is actively investigating the cause and working to restore normal delivery times. We will provide updates as soon as more information becomes available.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Our team identified a potential issue impacting the creation of member records and has implemented a fix. Systems are now operating normally, and we are actively monitoring to maintain stability. Additionally, the Client Match V2 feature has been temporarily disabled, resulting in a delay in its release. If you experience any further issues, please feel free to contact our support team. We will continue to provide updates as necessary.
We’re confident that all systems are running smoothly, and we’re now closing this incident. We appreciate your patience!
We’ve encountered an issue affecting the Staff tab, and our teams are opening an investigation. We’ll update this space with new information as it becomes available, and every hour.
Our teams have identified the cause of the issue, and are currently working toward a resolution. Thanks for your patience. We’ll continue to update this space hourly and as needed as work progresses.
Our team has implemented a fix and all systems have returned to normal function. We’re continuing to monitor to ensure stability. We’ll update this space if the situation changes.
We’re confident that all systems are running smoothly, and we’re now closing this incident. We appreciate your patience!
Some users may be experiencing intermittent 502 errors in the core application, and our team is actively investigating. We'll update this space with more information whenever it's available.
Error rates have returned to normal and all systems are running as expected. Our teams are continuing to monitor for any changes.
The team has mitigated the issue, and the 502 intermittent errors no longer occuring. This incident is now resolved.
We're aware of an issue with Google Cloud Services that may be intermittently impacting Google services within Coconut, including SSO and GSuite services. We're closely monitoring the issue and will update this space as more information becomes available.
Google services continue to be impacted - users may intermittently see font or other visual changes in Client View, and video links may not populate in Coconut Connect. We are continuing to monitor the situation and any impacts to Coconut services.
This incident has been resolved.
Multiple Zoom integration features are being affected by a Zoom outage. Coconut Connect and other video integrations are working as expected. We're monitoring the situation, and will provide updates here as they become available. Further information may be available on Zoom's status page: https://status.zoom.us.
Zoom services have recovered, and all Zoom integration features are now working as expected. Thanks for your patience!
Joining Coconut Connect meetings by phone is currently unavailable for customers who have been recently migrated to the updated version of Coconut Connect. It is still possible to join Coconut Connect meetings over video in your browser. Our dial-in provider is experiencing an outage, and is working to remediate it.
This incident has been resolved.
Our engineering team has identified an issue causing intermittent unavailability with our Advanced Analytics and Insights features. As we work towards a solution, users may at times be unable to access analytics dashboards through the Advanced Analytics and Insights tabs.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're seeing intermittent latency within the Coconut application, and are actively investigating. We'll update this space as more information becomes available.
Latency has recovered to expected levels, and our team is monitoring the situation to ensure stability.
No further latency has been observed, and we're marking this issue as stable.
We are aware of latency being experienced by some customers using Coconut Calendar. We are investigating presently.
Our team has implemented a fix and all systems have returned to normal function. We’re continuing to monitor to ensure stability.
We’re confident that all systems are running smoothly, and we’re now closing this incident. We appreciate your patience!
Coconut Calendar is experiencing some elevated response times on the dashboard view and our teams are opening an investigation. We’ll update this space with new information as it becomes available
Our team has implemented a fix and all systems have returned to normal function. We’re continuing to monitor to ensure stability.
We’re confident that all systems are running smoothly, and we’re now closing this incident. We appreciate your patience!
We're experiencing an issue with platform analytics. Data will be unavailable for approximately two hours while our team implements a fix. Once the fix has been implemented, data will become available again. No data will be lost during this time. We will provide an update if this timeline changes.
This incident has been resolved. All data is now up to date.
We are currently investigating this issue and will provide an update shortly.
A fix has been implemented, and system is now stable. Our team is monitoring.
This incident has been resolved.
We’re aware of a behaviour where appointments may not be created correctly when using the Schedule View. Other areas of the system are unaffected. Our team is actively working on a resolution, and we’ll update this space as more information becomes available
A fix has been implemented and we are monitoring the results.
Our team has implemented a fix and all systems have returned to normal function. We’re continuing to monitor to ensure stability.
This incident has been resolved.
Some of our customers experienced a recent delay with Microsoft Graph migration. These delays impacted the synchronization of your data. We have identified and resolved the underlying issue, and our systems are now actively catching up on any pending synchronization tasks. During this catch-up period, you may observe some delays in data updates. Important: To ensure the sync completes as quickly as possible, please avoid initiating any manual resyncs within your applications. Doing so may further slow down the overall process.
We're marking this incident resolved as data sync has caught up and all systems are running as expected.
Coconuts API is currently sending customers duplicate notifications. For the time being, the API for the notification_logs table will be out of date. We are currently investigating and hope to have an update soon.
The Notification Logs API is now operational again, and Notifications are now sending correctly. Our notification logs will appear to have some missing data for the next few days while we work on backfilling the data. We are continuing to monitor the situation over the coming hours/days to ensure there are no more disruptions.
We are continuing the work to backfill any missing logs. While this backfill work continues for the next few days, please reach out to Coconut Support with any questions.
The backfill work has been completed. the notification_logs table now contains the past 30 days of data and can be pulled from at any time. For any data older than thirty days, please reach out to [email protected] and they will facilitate this request.
We’re currently investigating reports of login failures.
We have mitigated the problem and we are now monitoring closely.
The issue has been resolved and the service is operating normally.