nirva|deploy
HomeChangelog

📊 System Status

Real-time status of NirvaDeploy services · ปรับปรุงทุก 60 วินาที

❌ Some systems are down

อัปเดตล่าสุด: 25 ก.ค. 2569 21:03

Services

🌐 Web Dashboard

nirvadeploy.com

✅ Operational

🤖 MCP Server

GitHub releases + npm

✅ Operational

🔑 Authentication

NextAuth (NIRVA SSO + external providers)

Wired: nirva

✅ Operational

💳 Billing

Stripe Thailand

STRIPE_SECRET_KEY missing

❌ Outage

📦 Engine

Dokploy on Contabo Singapore

✅ Operational

🤝 Affiliate Tracking

/api/affiliate/track

✅ Operational

📧 Transactional Email

Resend

RESEND_API_KEY missing — emails will log to stdout only

⚠️ Degraded Performance

🗄 Database (Postgres)

Cloud SQL / Hetzner

✅ Operational

₿ Bitcoin / Lightning

OpenNode

OPENNODE_API_KEY + OPENNODE_WEBHOOK_SECRET missing — BTC checkout disabled, Stripe still works

⚠️ Degraded Performance

💱 FX Rates

open.er-api.com (free, ECB-derived)

Live rates with hardcoded fallback. Outage degrades to stale quotes — pricing page still renders.

✅ Operational

🔒 At-rest encryption

lib/crypto.ts (AES-256-GCM + HKDF)

✅ Operational

🔌 Programmatic probes: GET /api/health (503 on outage) · GET /api/version (build SHA + region). Wire these into UptimeRobot / Cronitor / BetterStack.

📈 Uptime (90 days)

Web Dashboard

100.00%

SLA: N/A (best-effort)

Engine API

99.95%

SLA: 99% (Business)

Auth

100.00%

SLA: N/A (best-effort)

📜 Recent incidents (last 90 days)

✅ Resolvedminor14 พ.ค. 2569 08:00· resolved 14 พ.ค. 2569 08:00

Pre-launch soak test — intentional degraded mode (Resend not yet wired)

Affects: 📧 Transactional Email

## Resolution This is a seed-file documenting an intentional "degraded" state during pre-launch development: `RESEND_API_KEY` is intentionally absent in development, so the new `/api/health` endpoint correctly reports the email subsystem as `degraded` (emails fall back to `console.log`). No customer impact — this dates from before public launch. We're keeping this entry as the schema-demo example so the `/status` page has at least one row to render and contributors can see what the markdown looks like in production. The real first incident is filed later as a `2026-MM-DD-<slug>.md` file in this same directory.

📡 Get notified

เราจะ broadcast incident updates ผ่านช่องทางต่อไปนี้

📱 Line OA: @nirvadeploy (broadcast แจ้งเตือน)

🐦 X/Twitter: @nirvadeploy (Phase 2 launch)

📧 Email: subscribe ที่ /dashboard/settings/notifications

📋 RSS: /status/feed.rss (Phase 2.x)

🔧 Phase 4+ จะมี dedicated status page ที่ status.nirvadeploy.com