Maintenance event schedule

Maintenance event schedule

Maintenance events

As part of Tulip's ongoing commitment to deliver a reliable and secure cloud platform, there is an occasional need to perform necessary system maintenance. We understand the impact these events have on our customers' operations and want to provide as much forward notice as possible to minimize disruptions.

What are maintenance events?

Maintenance events are an essential part of our infrastructure's lifecycle. They ensure that our platform runs efficiently, with up-to-date security measures and an improved user experience. Activities performed during these windows may include upgrading core system components, applying patches, or version updates.

Schedule overview

Tulip schedules planned maintenance using quarterly downtime windows. The remaining months of the year are reserved for low-impact activities only.

• Quarterly downtime windows (Feb, May, Aug, Nov)
• 2-hour windows (12 AM – 2 AM, regional time)
• Formal process for emergency maintenance
• Maintenance announcements on status.tulip.co

Downtime months

Maintenance events that may involve a service interruption occur during the second month of each calendar quarter:

• February
• May
• August
• November

These windows are scheduled between 12 AM and 2 AM based on the hosting location's time zone (see Regional timezones below) and your environment's assigned weekend of the month.

Weekend-of-month assignments

Within a downtime month, each region has a fixed weekend on which its maintenance is performed. This rolling schedule lets each region complete maintenance independently and gives customers a predictable cadence.

For example, in an August downtime month: GovCloud is maintained on the first weekend of August, APAC/CN on the second, EU on the third, and US on the fourth — all within the regional 12 AM – 2 AM window.

Standard (non-downtime) months

During the remaining eight months of the year, Tulip may perform routine infrastructure maintenance, such as component upgrades or configuration changes. These activities are limited to those assessed as Low impact: no loss of service or significant performance degradation. Because these activities have no customer-visible impact, they are not announced in advance.

Impact categories

Each maintenance event is assessed and communicated in advance using the following impact categories:

High and Medium impact events occur only during quarterly downtime months. Standard months are limited to Low impact activities only.

Scope

This maintenance process applies to production cloud environments. Other environments (e.g., trial or candidate instances) follow a separate maintenance approach.

Emergency maintenance

In rare circumstances, unplanned maintenance outside of the quarterly window may be required to prevent an imminent service disruption. In these cases, Tulip will communicate proactively via the Tulip Status Page and/or direct outreach from your Customer Success Manager.

Regional timezones

Window times are based on the timezone of your environment's hosting location:

• US — Eastern Time (EST/EDT)
• EU — Central European Time (CET/CEST)
• APAC/CN — Japan Standard Time (JST)
• GovCloud/FedRAMP — Eastern Time (EST/EDT)

To find the region your environment is hosted in, reference the version information at the bottom left of Account Settings. (Available for customers on LTS12 or r275 and later.)

Stay informed

At least one month before each scheduled quarterly window, Tulip will update this page and post an assessment on status.tulip.co with a go/no-go decision and impact evaluation.

Tulip recommends subscribing to status.tulip.co to receive alerts for any new maintenance announcements and related updates.

2026 Schedule

2025 Schedule

2024 Schedule