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-25* |
Database version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 13-Jun-2026 10:00 PM SGT (Asia/Singapore) → 14-Jun-2026 2:00 AM SGT (Asia/Singapore) |
apac-30* |
Database version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 13-Jun-2026 10:00 PM SGT (Asia/Singapore) → 14-Jun-2026 2:00 AM SGT (Asia/Singapore) |
eu-3* |
Database version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 20-Jun-2026 10:00 PM CEST (Europe/Berlin) → 21-Jun-2026 2:00 AM CEST (Europe/Berlin) |
us-11* |
Network layout reorganization | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 27-Jun-2026 10:00 PM EDT (America/New_York) → 28-Jun-2026 02:00 AM EDT (America/New_York) |
us-11* |
Database version upgrade | High - Loss of service (10+ minutes) or significant performance degradation (30+ minutes) | 27-Jun-2026 10:00 PM EDT (America/New_York) → 28-Jun-2026 02:00 AM EDT (America/New_York) |
us-15* |
Database version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 27-Jun-2026 10:00 PM EDT (America/New_York) → 28-Jun-2026 02:00 AM EDT (America/New_York) |
us-33* |
Database version upgrade | Medium - Brief loss of service (<10 minutes) or significant performance degradation (<30 minutes) | 27-Jun-2026 10:00 PM EDT (America/New_York) → 28-Jun-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 https://support.tulip.co/docs/tulip-cloud-deployment-networking-requirements#allowlist.
- Some of the database servers require a version upgrade that involves a restart of the backend system.
- To prevent IP Exhaustion within our internal private network, in
us-11*we need to roll out new infrastructure nodes which affect all our services.
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