Is Tulip Interfaces Down?

This situation has been resolved as of 16:41 UTC . A database operation resulted in a spike in messages that needed to be processed by a backend service that powers live updates. The guardrail for the database operation that prevents the flood of messages had failed. --- [2026-10-29T18:00:46.917Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-29T16:18:28.668Z] (investigating) We are continuing to investigate errors when creating or deleting triggers and widgets in the App Editor. If you see an error, the change may still have been saved. Before trying again, do a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) or log out and back in. --- [2026-10-29T16:07:42.787Z] (investigating) We are investigating reports of errors when creating or deleting triggers and widgets in the App Editor.

This incident has been resolved as monitoring over the weekend determined performance for the garden remained stable after mitigating actions were taken on Friday. --- [2026-08-17T19:44:39.811Z] (monitoring) We have completed additional mitigating steps for the performance issue affecting the us-158 garden. Performance remains at normal operations, and we are continuing to monitor the garden in the interim --- [2026-08-17T19:44:15.363Z] (identified) Performance for the us-158 garden remains at normal operations. We continue to monitor and are working on additional steps to prevent this issue from recurring. --- [2026-08-17T19:44:11.734Z] (identified) Performance in the us-158 garden remains at stable following the mitigating action taken earlier today. Our team continues working to prevent a recurrence of this issue. --- [2026-08-17T19:43:11.277Z] (identified) We have isolated the root cause of degraded performance affecting the us-158 garden. Customers should expect to see improved performance in the interim. We are continuing to monitor and are working to prevent a recurrence --- [2026-08-14T21:05:59.789Z] (investigating) We continue to investigate the ongoing performance issue in Garden us-158. A root cause has not yet been identified. We will share updates as soon as we have more information. --- [2026-08-14T19:03:41.435Z] (monitoring) We are investigating further reports of performance issues in Garden us-158. We will share updates as soon as we have more information. --- [2026-08-14T18:34:32.384Z] (monitoring) We are continuing to monitor us-158 for any further issues --- [2026-08-14T17:38:47.358Z] (monitoring) We have made a configuration change to address the potential performance issue and are actively monitoring garden us-158 for improvement. --- [2026-08-14T17:14:28.264Z] (investigating) We are investigating a potential performance degradation issue affecting customers in the us-158 garden

The date for this maintenance has been updated to a week in the future reflect the schedule posted on the Tulip Knowledge Base here: https://support.tulip.co/docs/maintenance-event-schedule --- [2026-10-16T17:37:48.706Z] (scheduled) We are upgrading Tulip's backend infrastructure. During the maintenance window, Tulip instances may be unavailable or noticeably slower at times, and this may happen more than once.

The date for this maintenance has been updated to a week in the future reflect the schedule posted on the Tulip Knowledge Base here: https://support.tulip.co/docs/maintenance-event-schedule --- [2026-10-16T17:39:20.926Z] (scheduled) We are upgrading Tulip's backend infrastructure. During the maintenance window, Tulip instances may be unavailable or noticeably slower at times, and this may happen more than once.