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 |
|---|---|---|---|
apac-9* |
Azure Environment Network Update | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 14-Mar-2026 10:00 PM SGT (Asia/Singapore) → 15-Mar-2026 2:00 AM SGT (Asia/Singapore) |
apac-9*, apac-19* |
Kubernetes version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 14-Mar-2026 10:00 PM SGT (Asia/Singapore) → 15-Mar-2026 2:00 AM SGT (Asia/Singapore) |
apac-9*, apac-30* |
Config reload for pgbouncer | Low - No observable impact on service availability | 14-Mar-2026 10:00 PM SGT (Asia/Singapore) → 15-Mar-2026 2:00 AM SGT (Asia/Singapore) |
eu-7* |
Azure Environment Network Update | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 21-Mar-2026 10:00 PM CET (Europe/Berlin) → 22-Mar-2026 2:00 AM CET (Europe/Berlin) |
eu-27* |
Kubernetes version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 21-Mar-2026 10:00 PM CET (Europe/Berlin) → 22-Mar-2026 2:00 AM CET (Europe/Berlin) |
eu-7*, eu-27* |
Config reload for pgbouncer | Low - No observable impact on service availability | 21-Mar-2026 10:00 PM CET (Europe/Berlin) → 22-Mar-2026 2:00 AM CET (Europe/Berlin) |
us-15* |
Kubernetes cluster migration | High - Loss of service (10+ minutes) or significant performance degradation (30+ minutes) | 28-Mar-2026 10:00 PM EST (America/New_York) → 29-Mar-2026 02:00 AM EDT (America/New_York) |
us-14*, us-28* |
Config reload for pgbouncer | Low - No observable impact on service availability | 28-Mar-2026 10:00 PM EST (America/New_York) → 29-Mar-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 at Tulip Cloud deployment networking requirements.
- An Azure network update will be made to improve scalability for Azure-based gardens by modifying egress settings.
- 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.
- One of the infrastructure backend services, pgbouncer, requires a configuration reload. We don’t expect any customer-visible impact.
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