- Simply retry any tasks that failed during the window
- If the website feels sluggish, force-refresh the page (Ctrl/Cmd + Shift + R)
- API endpoints are no longer affected
← Back to Live Updates · 📚 Monthly Archive
Website 502 Resolved: Upstream Vendor Started Maintenance Early
From 23:07 to 23:20 (UTC+8) on 7/22, the website returned 502 for about 15 minutes with brief API disruption, after an upstream backend server vendor started scheduled maintenance roughly 2 hours early. Service is recovered — please retry failed tasks; force-refresh if the site feels sluggish. API endpoints are no longer affected.
2026/7/22 23:59 (UTC+8) · Service Notice
✅ The website returned 502 from 23:07–23:20 (UTC+8) tonight — service is recovered; please retry any tasks that failed during the window
Root cause: an upstream backend server vendor had scheduled maintenance for July 23, 01:00–05:00 (UTC+8), but started roughly 2 hours early, causing a sudden interruption. Our backend failover was prepared and ready to switch at any time, yet cache and DNS resolution caching still led to about 15 minutes of website 502s and API disruption.
What to do next:
← Back to Live Updates · 📚 Monthly Archive
← Back to Live Updates · 📚 Monthly Archive
此页面对您有帮助吗？