# Maintenance Event - December 2024

**URL:** <https://community.tulip.co/t/maintenance-event-december-2024/13194>\
**Category:** Announcements\
**Created:** [November 26, 2024, 4:33pm UTC](https://community.tulip.co/t/maintenance-event-december-2024/13194 "2024-11-26T16:33:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Grant](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/grant/32/182_2.png) [@Grant](https://community.tulip.co/u/Grant)\
**Post date:** [November 26, 2024, 4:33pm UTC](https://community.tulip.co/t/maintenance-event-december-2024/13194/1 "2024-11-26T16:33:27Z")

</div>

As part of Tulip’s policy for [maintenance events](https://support.tulip.co/docs/maintenance-event-schedule), we plan to post announcements in advance to Community.

#### What work is being performed?

The following regions/gardens will undergo the following work:

| Garden/Region | Description | Impact | When |
| --- | --- | --- | --- |
| `usgov` | DNS cache improvements,   
Database upgrades | Medium - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes) | 07-Dec-2024 10:00 PM EDT → 08-Dec-2024 02:00 AM EDT |
| `cn-20*` | Database upgrades | Medium - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes) | 14-Dec-2024 10:00 PM SGT → 15-Dec-2024 02:00 AM SGT |
| `apac-9*` | Kubernetes update | Medium - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes) | 14-Dec-2024 10:00 PM SGT → 15-Dec-2024 02:00 AM SGT |
| `eu-7*` | Kubernetes update | Medium - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes) | 21-Dec-2024 10:00 PM CET → 22-Dec-2024 02:00 AM CET |
| `us-14*` | Database upgrades | Medium - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes) | 28-Dec-2024 10:00 PM EST → 29-Dec-2024 02:00 AM EST |

Please refer to our [Maintenance Event Schedule](https://support.tulip.co/docs/en/maintenance-event-schedule) for further information regarding the date and times for regional maintenance windows.

If you have any questions, please reach out to your Customer Success Manager, Account Manager, or [support@tulip.co](mailto:support@tulip.co).

---

<div class="post-metadata">

**Author:** ![klickal](https://avatars.discourse-cdn.com/v4/letter/k/a88e57/32.png) [@klickal](https://community.tulip.co/u/klickal)\
**Post date:** [December 3, 2024, 9:42pm UTC](https://community.tulip.co/t/maintenance-event-december-2024/13194/2 "2024-12-03T21:42:48Z")

</div>

This is great Grant, thanks for sharing!

Would it be possible to post applicable maintenance events directly to a user’s instance? A ticker, banner, notification, etc. It would be a huge benefit to only get info of planned outages that applies to the user rather than search for it and interpret what applies (if it’s not immediately clear).

Let’s use your upcoming events (with a couple impacts modified for the exercise) as an example and let’s say we use 4 customers in the below example:

**Customer 1:** Has 2 of 5 areas of impact.  
**Customer 2:** Has 1 of 5 areas of impact.  
**Customer 3:** Has 4 of 5 areas of impact.  
**Customer 4:** Has 0 of 5 areas of impact.

Messages/Notifications for upcoming outages would show up as such for example:

**Customer 1:**  
There is scheduled maintenance affecting your instance planned for the following regions: **cn-20** , **us-14**.

1. The work for **cn-20** is scheduled to be performed on _ **14-Dec-2024 10:00 PM SGT → 15-Dec-2024 02:00 AM SGT** _.  
**IMPACT** : MEDIUM - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes)
2. The work for **us-14** is scheduled to be performed on _ **28-Dec-2024 10:00 PM EST → 29-Dec-2024 02:00 AM EST** _.  
**IMPACT** : ⚠ HIGH - Loss of service (\<60 minutes) or significant performance degradation (\<180 minutes) ⚠

**Customer 2:**  
There is scheduled maintenance affecting your instance planned for the following regions: **usgov**.

1. The work for **usgov** is scheduled to be performed on _ **07-Dec-2024 10:00 PM EDT → 08-Dec-2024 02:00 AM SGT** _  
**IMPACT** : LOW - Brief loss of service (\<1 minute) or significant performance degradation (\<15 minutes)

**Customer 3:**  
There is scheduled maintenance affecting your instance planned for the following regions: **cn-20** , **apac-9** , **eu-7** , **us-14**.

1. The work for **cn-20** is scheduled to be performed on _ **14-Dec-2024 10:00 PM SGT → 15-Dec-2024 02:00 AM SGT** _.  
**IMPACT** : MEDIUM - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes)
2. The work for **apac-9** is scheduled to be performed on _ **14-Dec-2024 10:00 PM SGT → 15-Dec-2024 02:00 AM SGT** _.  
**IMPACT** : MEDIUM - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes)
3. The work for **eu-7** is scheduled to be performed on _ **21-Dec-2024 10:00 PM CET → 22-Dec-2024 02:00 AM CET** _.  
**IMPACT** : MEDIUM - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes)
4. The work for **us-14** is scheduled to be performed on _ **28-Dec-2024 10:00 PM EST → 29-Dec-2024 02:00 AM EST** _.  
**IMPACT** : MEDIUM - Brief loss of service (\<10 minutes) or significant performance degradation (\<30 minutes)

**Customer 4:** (nothing applicable and subsequently, nothing shown.)  
.  
.  
.  
Lastly, 🍒 on top would be if you could set (within Account Settings) specific users or user groups to receive the messages/notifications directly. This could allow for timely/proper internal communications, awareness, and preparedness. Also, adding frequency/cadence of notifications in Account Settings could offer more tailored versions of this.  
EXAMPLES:

- “Every 1 day until service”
- “Every 1 week until service”
- “Every 1 week until service” + “1 hour warning prior to service”
- “Every 1 day until service” + “3 hours warning prior to service” + “1 hour warning prior to service”

Just some thoughts, thanks!

---

<div class="post-metadata">

**Author:** ![Grant](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/grant/32/182_2.png) [@Grant](https://community.tulip.co/u/Grant)\
**Post date:** [December 5, 2024, 3:21pm UTC](https://community.tulip.co/t/maintenance-event-december-2024/13194/3 "2024-12-05T15:21:04Z")

</div>

@klickal Hey Alex, thanks for sharing your detailed thoughts here!

We’re certainly looking at ways to improve our maintenance communication process. I would say your approach aligns with our long-term thinking about having Tulip serve as the notification source for these types of events. We’re beginning to think more about general in-product notifications in 2025, which feels like a natural home for something like this.

We may also look to tie this effort into our status page work we’re planning with the understanding of the importance of proactive notifications!

---

<div class="post-metadata">

**Author:** ![jordan.munson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jordan.munson/32/6434_2.png) [@jordan.munson](https://community.tulip.co/u/jordan.munson)\
**Post date:** [December 14, 2024, 6:18pm UTC](https://community.tulip.co/t/maintenance-event-december-2024/13194/4 "2024-12-14T18:18:07Z")

</div>

Maintenance activities for 14-Dec-2024 have concluded, applicable gardens fully operational as of the end of the maintenance window.

---

<div class="post-metadata">

**Author:** ![jordan.munson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jordan.munson/32/6434_2.png) [@jordan.munson](https://community.tulip.co/u/jordan.munson)\
**Post date:** [December 29, 2024, 5:44am UTC](https://community.tulip.co/t/maintenance-event-december-2024/13194/5 "2024-12-29T05:44:44Z")

</div>

Maintenance activities in `us-14*` for 28-Dec-2024 have concluded.