1. Project Introduction
WorldMonitor-CN is a 7×24 global information aggregation and monitoring platform that unifies TV live streaming, stock quotes, foreign exchange rates, global news, natural disasters and conflict hotspots into one interface, providing a real-time, intuitive overview of global dynamics.
Online Access
- Project site: https://world.astock.com.cn/
Design Philosophy
- Never black screen: all external data sources have multi-tier degradation strategies; any failed source automatically switches to a backup or degrades to a friendly empty state
- Fresh data: each panel refreshes independently according to its own characteristics
- Long-term stability: automated operations and fault tolerance keep the service continuously online
2. Core Features
| Feature | Description |
|---|---|
| TV live streaming | Built-in CCTV-13 news channel with automatic multi-source failover; degrades gracefully on failure, never a stuck black screen |
| A-share quotes | Real-time intraday refresh, automatic suspended-stock detection, auto-stop after market close |
| Forex rates | 20 major currency pairs with 10-second auto refresh |
| News aggregation | Multi-source news and hotspot aggregation with independent per-source caches |
| Global disasters | Real-time earthquake and climate disaster monitoring |
| Conflict hotspots | Global conflict and hotspot tracking |
3. Uptime and Stability
The project has been running for about 119 days since its creation on 2026-05-04, through 15+ development iterations and 7 major feature evolutions. Only 1 planned reboot occurred (kernel security patch maintenance window), with no unplanned downtime.
3.1 Key Stability Metrics (2026-08-31 measured)
| Metric | Value |
|---|---|
| Project lifetime | 119 days (since 2026-05-04) |
| Server continuous run | ~107 days (15 weeks 1 day) |
| Service processes continuous run | 4 days 7 hours (since latest deployment) |
| Homepage response time | ~42 ms (HTTP 200) |
| Recent log errors | 0 (last 2000 lines scanned) |
| Data links | All caches fresh, matching refresh cycles |
3.2 Milestones
| Date | Milestone |
|---|---|
| 2026-05-04 | Project created and launched |
| 2026-05-05 | Static map data and deployment docs |
| 2026-05-07 | 20 forex pairs integrated |
| 2026-05-12 | A-share suspended-stock double filtering |
| 2026-05-16 | Systemic fixes + kernel security upgrade (the only planned reboot) |
| 2026-06-13 | Live-source architecture refactor with auto sync |
| 2026-07-30 | A-share quote protocol migration, outage recovery |
| 2026-08-27 | Full live-source failure fix and player hardening |
| 2026-08-31 | Full stability checkup |
3.3 Stability Safeguards
- Circuit breaker & degradation: external data sources auto-break on repeated failures; UI degrades to friendly empty states instead of crashing
- Fast/slow resource decoupling: live video streams load asynchronously in the background without blocking data panels
- Live multi-source auto-switch: sources fail over by priority; explicit error + retry when all fail
- Quote collection fault tolerance: suspended stocks auto-filtered and auto-recovered on resumption; auto-stop after close
- Scripted process management: one-click start/stop/status with full process lifecycle control
- Security baseline: high-risk kernel and component vulnerabilities fixed, with ongoing tracking
Pattern: every external data-source change gets diagnosed and hardened within 1~2 days, with anti-regression mechanisms accumulated each time — stability rises in a spiral.
4. System Runtime Architecture
4.1 Architecture Source
The following architecture information was generated by Archify from real source-code analysis of the project repository. Every module maps to a real source file, giving the diagram a verifiable, explainable code-to-diagram correspondence.
- Full interactive architecture diagram (Archify HTML output): Open architecture diagram
Interactive diagram notes
Open the link above to view the full interactive architecture diagram, supporting node search, route tracing, semantic views, theme switching, zoom/pan and presentation playback.
4.2 Architecture Overview
4.3 Core Components
| Component | Type | Role | Source files |
|---|---|---|---|
| Browser / Frontend | External | TypeScript SPA | — |
| Preact Frontend | Frontend | 16 panels + services | src/App.ts |
| Vite API Server | Backend | bypass /api/* + HLS proxy | vite.config.ts |
| Price Monitor Service | Backend | pytdx 5s quote feed | scripts/heartbeat/fetch_astock_tdx.py |
| Data Sync Service | Backend | heartbeat scrapers | scripts/heartbeat/heartbeat.py |
| GitHub Source | External | iptv-org/iptv zho.m3u | — |
| Local Data & Snapshot | Database | .cache JSON + static geo | src/data/static-geo.ts, public/config.yml |
| Scheduler / Cron Jobs | Backend | THQ loop + heartbeat | scripts/scrape-thq.mjs, start.sh |
4.4 Data Flow and Connections
| Connection | Direction | Description |
|---|---|---|
| HTTPS | Browser / Frontend → Preact Frontend | User entry point |
| fetch /api/* | Preact Frontend → Vite API Server | Frontend fetches data APIs |
| quotes /api/market | Vite API Server → Price Monitor Service | Fetches quote data |
| write snapshot | Price Monitor Service → Local Data & Snapshot | Writes quote snapshots |
| refresh data | Vite API Server → Data Sync Service | Triggers data refresh |
| upstream feeds | Data Sync Service → GitHub Source | Fetches upstream data |
| upstream data | GitHub Source → Local Data & Snapshot | Upstream data flows in locally |
| schedule scrapes | Scheduler → Vite API Server | Periodic scheduled scraping |
| trading hours 5s | Scheduler → Price Monitor Service | 5-second quotes during trading hours |
4.5 Three Operational Perspectives
User Entry
- The Preact SPA renders 16 live panels over MapLibre.
- Requests reach the Vite API layer through /api/* bypass.
Data Path
- Heartbeat scrapers refresh ifeng, climate, conflict, and exchange.
- pytdx writes A-share quotes every 5s during trading hours.
Upstream & Resilience
- iptv-org playlist refreshes hourly with config.yml fallbacks.
- Every service falls back to built-in mock data when offline.
The diagram includes two views: Primary runtime flow (user-facing panels reach the Vite API layer, which serves quote and news data from local snapshots) and Data sync path (heartbeat scrapers and the THQ loop refresh local snapshots from upstream sources).
5. Security & Compliance
- Known high-risk kernel vulnerabilities (Copy Fail / Dirty Frag CVEs) fixed in the maintenance window
- Data sources use legal public interfaces, following each source's usage rules
- Running status and logs fully auditable for post-hoc tracing
This document is the public introduction of WorldMonitor-CN, focusing on features, stability and system architecture. Internal implementation details and tuning parameters are internal research materials and are not displayed here.