Priority Reminder / Infrastructure Request: Official Real-Time Public Status Page for Z.ai & ZCode Services #1265

Context & Community Incident

• Discord Reference: https://discord.com/channels/1346756824233148527/1563553464037019688
• Thread Title: "zcode desktop - Reconnecting all the time, a simple task is completed in 30 minutes or ends"
• Incident Summary: Extended routing/connection degradations where ZCode Desktop repeatedly dropped into "Reconnecting" loops for international users outside Asia (often taking 30+ minutes or failing simple tasks).

The Core Problem: Silence During Outages

When infrastructure degraded, paid customers received no automated status broadcast or incident timeline. Users were left guessing whether:

1. Their local network or VPN was broken.
2. Their account was rate-limited or banned.
3. The platform was undergoing an active regional CDN/gateway incident.

As seen in thread 1563553464037019688, the absence of an authoritative status page led to deep user frustration, accusations of deception, and community panic. In the words of community moderators: "An honest 'It is broken, here is the honest ETA' beats silence every single time."

Why a Public Status Page is Critical

1. Reduces Support Load: During incidents, hundreds of users flood Discord and support tickets with identical complaints. A status page deflects redundant inquiries automatically.
2. Restores User Trust: Transparent reporting of partial outages, elevated latency, and scheduled maintenance shows professionalism and respect for paying subscribers.
3. Regional Visibility: Clear component breakdowns show when specific regions (e.g., North America / Europe routes vs. Asia-Pacific gateways) experience transit degradation.

Actionable Implementation Plan

1. Public Status Domain: Launch status.z.ai powered by standard infrastructure status tooling (e.g. Instatus, Better Uptime, or Statuspage).
2. Granular Component Tracking:
   • Web Chat (chat.z.ai)
   • ZCode Desktop Sync & Remote Server
   • Model API Inference Endpoints (GLM-5.3, GLM-5.3-Flash, GLM-5.2)
   • Authentication & Billing Services
   • Regional Gateway Latency (Asia-Pacific, North America, Europe)
3. Automated Incident Updates: Publish honest status states: Operational, Degraded Performance, Partial Outage, Maintenance.