New Multi-region uptime checks and custom-domain status pages

Tulip Interfaces Outage History

Daily provider-status observations and published incident history for Tulip Interfaces.

Operational

Tulip Interfaces is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Tulip Interfaces for future changes.

100% of 37 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

6 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
G15 Performance Issue
major Source not attested
Last archived state: resolved
View archived record details
Analytics App Editor App Execution Authentication Automations Completions Connectors Edge Devices Functions Tables Tulip AI Vision
monitoring
We have implemented a fix for the performance issue affecting the us-158 garden. Performance has been observed to return to normal for impacted customers. We will continue to monitor the garden in the interim
identified
Our team continues to address root cause of the performance degradation affecting the us-158 garden. Customers may notice improved performance in the meantime as mitigations take effect. We will continue to provide updates as we progress toward full resolution.
identified
We are continuing to work on resolving the performance issue in Garden us-158. Our team remains actively engaged and we will share updates as soon as we have more information.
identified
We have isolated the root cause and are working to resolve the issue. Customers may see improved performance in the interim. We are continuing to monitor us-158 and provide updates as we have them.
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.
monitoring
We are investigating further reports of performance issues in Garden us-158. We will share updates as soon as we have more information.
monitoring
We are continuing to monitor us-158 for any further issues
monitoring
We have made a configuration change to address the potential performance issue and are actively monitoring garden us-158 for improvement.
investigating
We are investigating a potential performance degradation issue affecting customers in the us-158 garden
July 2026
Investigating CSV Import Issues for Tables in usgov-227
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a fix and CSV imports to Tables in usgov-227 should now work as expected. We are monitoring to confirm the issue is fully resolved
investigating
We are investigating errors affecting CSV imports to Tables for instances in usgov-227. Affected users may see a "Firewall Issues" error when importing a CSV file to a Table.
June 2026
Degraded performance for some customers
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We have increased resources to mitigate the issue and are working to identify the cause.
investigating
We are investigating reports of slower-than-usual performance affecting a subset of customers across multiple versions. Some users may experience delays or timeouts when loading and using Tulip. We will provide an update shortly.
May 2026
Investigating: Connector Function Editor Unavailable
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the cause of this issue as a network routing component update that was rolled out earlier today. We have rolled back to the previous version and the Connector Function Editor is now accessible. We are monitoring the platform to confirm full stability. We will provide a final update once we have verified the issue is resolved.
investigating
We continue to investigate an issue where the Connector Function Editor is not loading for some customers. Our team is actively working to restore full functionality. We will provide another update within 60 minutes.
investigating
We are investigating an issue where the Connector Function Editor is not loading for some customers. Affected users will see a blank editor when attempting to access connector functions in the App Editor with the message: "Something went wrong. An unexpected error occurred and this page could not be shown. Please contact support@tulip.co." Our team is actively working to restore full functionality. We will provide an update within 60 minutes.
Partial outage in us-142
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Services appear to be recovering for affected customers in garden us-142. We are continuing to monitor.
identified
We have identified an issue with our upstream cloud database provider (Azure) causing service unavailability for customers hosted in garden us-142. The provider has acknowledged the issue and escalated it to their internal team. We do not have an ETA for resolution at this time. We will continue to monitor and provide updates at least hourly.
April 2026
Partial outage in eu-276
Source not attested
Last archived state: resolved
View archived record details
monitoring
We are still monitoring the issue, however, all functions remain unaffected since the containment actions.
monitoring
After identifying the source of the partial outage, we have taken containment actions at approximately 1:30 PM CEST. We expect all functionality to be back to normal.
identified
Our TechOps team has identified the source of the partial outage which started around 1 PM CEST, and are taking containment actions.
investigating
We are currently experiencing a partial outage in eu-276
Get alerts for Tulip Interfaces Subscribe to the provider incident feed Browse all services