Tulip Interfaces Outage History

21 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Tulip Interfaces Incident

Tulip Interfaces incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 29, 2026Backend infrastructure upgrade (us-142, us-158, us-332, us-347)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-schedule2h 0mScheduled
Nov 22, 2026Backend infrastructure upgrade (eu-32, eu-70, eu-276)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-schedule2h 0mScheduled
Nov 15, 2026Backend infrastructure upgrade (apac-94, apac-194, apac-256, apac-307, apac-351, cn-219)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-schedule2h 0mScheduled
Nov 8, 2026Backend infrastructure upgrade (us-gov-227)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-schedule2h 0mScheduled
Oct 29, 2026Errors when creating or deleting triggers and widgetsThis 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…2h 29mResolved
Aug 23, 2026Database upsizing (us-158)Scheduled maintenance is complete. All affected components are now fully operational.2h 0mScheduled
Aug 23, 2026Database version upgrade (us-347)The scheduled maintenance has been completed.2h 0mScheduled
Aug 23, 2026Database Layer Connection Update (us-347)The scheduled maintenance has been completed.2h 0mScheduled
Aug 14, 2026G15 Performance IssueThis incident has been resolved as monitoring over the weekend determined performance for the garden remained stable after mitigating actions were taken on Friday.67h 16mResolved
Aug 8, 2026Database version upgrade (cn-219)The scheduled maintenance has been completed.30 minScheduled
Aug 2, 2026Database version upgrade (usgov-227)Scheduled maintenance is complete. All affected components are now fully operational.30 minScheduled
Jul 13, 2026Investigating CSV Import Issues for Tables in usgov-227This incident has been resolved. Users in usgov-227 experienced errors when importing CSV files to Tables. Full functionality has been restored.2h 37mResolved
Jun 30, 2026Degraded performance for some customersThis incident has been resolved as of 13:55 UTC. We identified a resource imbalance affecting a subset of customers' requests and have since rebalanced resources to restore normal performance.4h 41mResolved
May 31, 2026Investigating: Connector Function Editor Unavailable**Resolved** — The Connector Function Editor is fully operational. On May 30, 2026, we identified an issue where the Connector Function Editor was failing to load for some customers. The issue was resolved at 02:27 UTC…19h 28mResolved
May 2, 2026Partial outage in us-142After further monitoring, we have determined that the issue is resolved. Further details will be available in a postmortem. The partial outage in us-142 occurred around 22:55 UTC on May 1 and was contained around 00:05…11h 54mResolved
Apr 27, 2026Partial outage in eu-276After further monitoring, we have determined that the issue is resolved. Further details will be available in a postmortem, to conclude the incident. The partial outage occurred around 11:00 AM UTC, affecting multiple…4h 28mResolved
Mar 4, 2026Intermittent Microsoft Entra ID SAML Login IssuesThis incident has been resolved.213h 3mResolved
Feb 23, 2026Increased Latency in Garden eu-32Earlier today, customers hosted in Garden eu-32 experienced degraded performance in the app editor, tulip tables, and the connectors status page. Performance has returned to normal levels as of 03:52 UTC, and we will…1h 17mResolved
Feb 20, 2026Intermittent Page Load SlownessValidation and monitoring have verified the mitigating actions were effective and as such we’re marking this issue as resolved. As mentioned previously we’ll be performing a full root cause analysis per our quality…103h 24mResolved
Jan 26, 2026Table CSV Importer Down in Garden US-142This incident has been resolved.48 minResolved
Jan 7, 2026Connector timeouts in us-158 gardenWe investigated and confirmed the slow or stuck connector function behavior reported by several customers in the us-158 Garden. Affected users experienced sporadic connector timeouts, resulting in stalled app triggers…-13019 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Tulip Interfaces incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Tulip Interfaces Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Tulip Interfaces acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Tulip Interfaces outage in this window ran 8d 21h, against a mean recovery of 22h 19m. If you depend on Tulip Interfaces in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.