Is Tonkean down?

We discovered an error with Sharepoint data sources breaking due to an invalid key error. We found the root cause and are working on a fix.

A fix was implemented and we are currently monitoring the situation.

We are continuing to monitor for any further issues.

This incident has been resolved.

We experienced a disruption to its SharePoint integration between May 14–15, 2026, caused by the expiration of authentication credentials used to connect to Microsoft SharePoint services. The issue affected customers using our shared SharePoint integration, causing failed SharePoint actions during the outage window. The first authentication failures were logged on May 14 at approximately 19:37 UTC. The incident was formally reported on May 15 at 17:28 UTC following the identification of multiple customer issues. Investigation began at 17:45 UTC, and expired Azure AD client secrets were identified as the root cause. Updated credentials were generated and deployed beginning at 18:01 UTC. Additional remediation steps and environment restarts were completed between 18:05 and 18:10 UTC to ensure the updated credentials were fully applied. Customers confirmed successful reconnection to SharePoint integrations following the fix. To reduce the likelihood of recurrence, we are enhancing our monitoring and alerting for credential expiration, expanding audits of integration authentication across environments, refining credential rotation procedures, and continuing efforts to further automate integration credential management workflows.

We're investigating a slowness in processing of Tonkean items, actions and interfaces

This incident has been resolved.

On April 15, 2026 at 19:00 \(UTC\+3\), a configuration issue triggered a loop within an automation module, causing repeated item creation and excessive system activity. This led to a significant increase in load and degraded platform performance. Customers experienced elevated latency, including slower interface loading, delays when progressing through processes, and slower execution of automated actions. No data loss occurred. The issue was identified within approximately one hour. Mitigation actions included stopping the loop and clearing overloaded processing queues. Full service was restored for all customers by April 16 at 12:23 \(UTC\+3\). The root cause was a trigger configuration that continuously re-executed under certain conditions, resulting in unbounded item creation and system load. To prevent recurrence, we are implementing safeguards including rate limits on actions and item creation, defined execution quotas at the module and solution level, and automatic halting of processes when limits are exceeded with visibility in execution history.

We've seen slowness in processing of Tonkean items. We're investigating the root cause and a possible fix.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

On April 15, 2026 at 19:00 \(UTC\+3\), a configuration issue triggered a loop within an automation module, causing repeated item creation and excessive system activity. This led to a significant increase in load and degraded platform performance. Customers experienced elevated latency, including slower interface loading, delays when progressing through processes, and slower execution of automated actions. No data loss occurred. The issue was identified within approximately one hour. Mitigation actions included stopping the loop and clearing overloaded processing queues. Full service was restored for all customers by April 16 at 12:23 \(UTC\+3\). The root cause was a trigger configuration that continuously re-executed under certain conditions, resulting in unbounded item creation and system load. To prevent recurrence, we are implementing safeguards including rate limits on actions and item creation, defined execution quotas at the module and solution level, and automatic halting of processes when limits are exceeded with visibility in execution history.