Is Tonkean down?

We are seeing higher error rates and slow workflow execution times in production. We are investigating the root cause.

All workflows and interfaces are back to normal.

On June 24–25, 2026, between approximately 22:00 UTC on June 24 and 19:37 UTC on June 25, users experienced slowness and failures when opening certain views that rely on connected data sources. Fields linked to those data sources did not populate, and in some cases, views failed to load. We recognize the disruption this caused and appreciate your patience. The issue was first reported at 23:10 UTC on June 24. By 23:14 UTC, our engineering team had identified the cause: a separate project was generating an unusually large number of slow-running background queries that overwhelmed our shared search service, causing failures across connected data source fields. Service was confirmed restored by 19:37 UTC on June 25. No data was lost. The primary driver was a configuration error in a separate project. A connected data source had grown significantly, and due to the misconfiguration, every record in that source was treated as newly changed on every sync — causing the same data to be re-processed continuously and flooding the shared service. An existing safeguard that would have limited the impact had also been removed the prior day due to an unrelated bug. We corrected the misconfiguration to stop the excessive re-processing, and we are restoring the removed safeguard. Going forward, we are adding monitoring to detect and alert on this type of overload early, improving how we handle large data-source syncs so they do not flood shared services, and reviewing configuration defaults to prevent similar errors. We remain committed to the reliability of the Tonkean platform and to ensuring this type of incident does not recur.

We're seeing an issue with agents not responding at all at the moment. We've identified the root cause, and are working on a fix.

Incident is resolve, AI Agents are back working and responding.

On 19 June 2026, between 08:30 and 09:08 UTC, all AI agents were unavailable across Tonkean’s production environments for approximately 38 minutes. Agents did not respond to requests during this window, interrupting active work and demonstrations. We recognize the significance of this disruption and appreciate your patience. The outage was caused by Tonkean’s AI provider account reaching its usage and spending limits, which resulted in every agent request being rejected. Two factors extended the impact: the account’s quota had been consumed more quickly than anticipated, and an outstanding account balance had to be cleared before the quota could be restored — even after we had raised the limit. An automated alert had fired the previous afternoon, warning of the approaching limit, but it posted silently and was not acted on. Service was restored at 09:08 UTC after the balance was cleared and the limit raised. No data was lost. To prevent recurrence, we are wiring the existing alert to actively page the on-call team and billing account owners rather than posting silently, and adding a proactive alert at roughly 90% of the spend limit. We remain committed to the reliability of the Tonkean platform and to ensuring the gaps identified here are fully closed.

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.