# Real-Time Server Status Notifications Feature Request

**URL:** <https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732>\
**Category:** General Discussion\
**Created:** [September 25, 2025, 5:17pm UTC](https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732 "2025-09-25T17:17:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![harry\_cmary](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/harry_cmary/32/518949_2.png) [@harry\_cmary](https://forums.zwift.com/u/harry_cmary)\
**Post date:** [September 25, 2025, 5:17pm UTC](https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732/1 "2025-09-25T17:17:28Z")

</div>

Hi Zwift Team & Community,

One of the challenges many of us face is starting a ride or race only to encounter unexpected server issues or disconnections. At the moment, it’s difficult to know if a problem is on our end (network, hardware, ISP) or if it’s a Zwift server-side issue.

I’d like to propose a **real-time server status notification system** that could:

1. **In-App Alerts:** Notify riders of current server issues before starting or during a session.

2. **Dashboard/Website Updates:** A live status page with real-time information on server health, latency, and outages.

3. **Push Notifications:** Mobile notifications or emails for subscribers when there are known outages or maintenance windows.

4. **Regional Indicators:** Show if the issue is specific to EU/US/Asia servers so users know what to expect.

5. Integration with Events: If a scheduled race is likely to be impacted, display an alert before entry.

```auto
This would greatly improve <a href="https://www.lenovo.com/jp/ja/servers-storage/servers/">server</a> related user experience by reducing confusion, saving time, and helping Zwifters troubleshoot more effectively.

```

What does the community think? Would a system like this make your Zwift experience smoother?

Thanks for considering this feature request!

---

<div class="post-metadata">

**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://forums.zwift.com/u/discourse_ai_spam)\
**Post date:** [September 25, 2025, 5:17pm UTC](https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732/2 "2025-09-25T17:17:36Z")

</div>

Unlisted on September 25, 2025, 5:17pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/gozwift/original/4X/9/1/0/910bea9bd4cc6eaca95dec1ed9fc77a3b5b0ed27.png) [@system](https://forums.zwift.com/u/system)\
**Post date:** [September 25, 2025, 5:23pm UTC](https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732/3 "2025-09-25T17:23:15Z")

</div>

Listed on September 25, 2025, 5:23pm UTC



---

<div class="post-metadata">

**Author:** ![shooj](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/shooj/32/91371_2.png) [@shooj](https://forums.zwift.com/u/shooj)\
**Post date:** [September 25, 2025, 5:24pm UTC](https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732/4 "2025-09-25T17:24:53Z")

</div>

Hi @harry_cmary

Yes. It’s [status.zwift.com](https://status.zwift.com/)

---

<div class="post-metadata">

**Author:** ![Paul\_Southworth](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/paul_southworth/32/538336_2.png) [@Paul\_Southworth](https://forums.zwift.com/u/Paul_Southworth)\
**Post date:** [September 25, 2025, 5:28pm UTC](https://forums.zwift.com/t/real-time-server-status-notifications-feature-request/656732/5 "2025-09-25T17:28:24Z")

</div>

Just be aware that [status.zwift.com](http://status.zwift.com) may not be updated timely or at all. If it doesn’t reveal a known problem, that doesn’t mean there isn’t a problem.