Skip to service health
MMARSA EmpowerSystem Status
Status data is up to date
Live system monitor

Service outage detected

Independent health checks against every production dependency — authentication, database, AI engine and public website. Data is read from UptimeRobot and our own health endpoint; nothing is simulated.

Updated just now21 Nov 2026, 05:58 UTC

24h uptime
—
Avg response
—
Incidents 30d
0

Some monitoring data is unavailable

  • UptimeRobot: api_key not found.
  • Health endpoint: Health endpoint returned HTTP 404.

Affected services are shown as Unknown instead of operational — never the other way around.

Service health

6 monitored services · live checks and uptime history in UTC

Website Availability

Public website and application shell

No uptime history — this dependency is checked live on every refresh.

Unknown

Avg response—

api_key not found.

Backend API

Next.js server runtime and API routes

No uptime history — this dependency is checked live on every refresh.

Outage

Latency62 ms

Health endpoint returned HTTP 404.

Database

Neon PostgreSQL primary data store

No uptime history — this dependency is checked live on every refresh.

Unknown

Latency—

Cannot verify while the health endpoint is unreachable.

Authentication

Clerk sign-in and session tokens

No uptime history — this dependency is checked live on every refresh.

Unknown

Latency—

Cannot verify while the health endpoint is unreachable.

AI Engine (Maryam)

OpenAI provider connectivity

No uptime history — this dependency is checked live on every refresh.

Unknown

Latency—

Cannot verify while the health endpoint is unreachable.

Status Dashboard

This page and its monitoring pipeline

No uptime history — this dependency is checked live on every refresh.

Operational

Latency—

Response time

No monitor is configured for response-time history

Real data

No response-time samples yet

UptimeRobot has not returned any response-time history for this monitor. Samples appear after the first few checks — nothing is simulated here.

Incident history

Downtime events logged by UptimeRobot, newest first

No incidents recorded

UptimeRobot has not logged a downtime event for the current retention window. Incidents appear here automatically when a check fails.

Data sources

UptimeRobot

Uptime, response times, incidents

Error

Health endpoint

Database, auth and AI verification

Error

Dashboard

Refreshes every 60 seconds

Live

Still experiencing an issue?

If something feels broken but this page shows operational, tell our support team — your report may reach us before the next automated check does.

Contact support