As part of Tulip’s policy for maintenance events, we plan to post announcements in advance to Community.
What work is being performed?
The following regions/gardens will undergo the following work:
| Garden | Description | Impact | When |
|---|---|---|---|
usgov-* |
Database version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 02-May-2026 10:00 PM EDT (America/New_York) → 03-May-2026 02:00 AM EDT (America/New_York) |
cn-* |
Kubernetes cluster migration | High - Loss of service (10+ minutes) or significant performance degradation (30+ minutes) | 09-May-2026 10:00 PM SGT (Asia/Singapore) → 10-May-2026 2:00 AM SGT (Asia/Singapore) |
us-14* |
Kubernetes version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 23-May-2026 10:00 PM EDT (America/New_York) → 24-May-2026 02:00 AM EDT (America/New_York |
Regarding maintenance activities:
- We are performing a required infrastructure migration as part of the Tulip lifecycle, which involves moving Tulip services to a new Kubernetes cluster. This migration will require downtime and will involve redeploying the existing Tulip version to every instance in the region. As part of this activity, services will fail over to a different set of ingress IPs within the IP ranges already communicated in our Knowledge Base at https://support.tulip.co/docs/tulip-cloud-deployment-networking-requirements#allowlist.
- One of the database servers requires a version upgrade involving a restart of the backend system.
- Kubernetes upgrade involves upgrading the version of the infrastructure component. Existing Kubernetes nodes will be replaced with new ones, requiring a brief downtime for Tulip customers.
Please refer to our Maintenance Event Schedule for further information regarding the date and times for regional maintenance windows.
If you have any questions about the maintenance windows please reach out to your Customer Success Manager or the Tulip Support Team