📈 Live Status: 🟧 Partial outage

This repository contains the open-source uptime monitor and status page for Namo ID, powered by Upptime.

With Upptime, you can get your own unlimited and free uptime monitor and status page, powered entirely by a GitHub repository. We use Issues as incident reports, Actions as uptime monitors, and Pages for the status page.

URL	Status	History	Response Time	Uptime
Marketing	🟩 Up	marketing.yml	59ms	100.00%
API Liveness	🟩 Up	api-liveness.yml	73ms	100.00%
API Readiness	🟥 Down	api-readiness.yml	125ms	83.58%
OIDC Discovery	🟩 Up	oidc-discovery.yml	78ms	100.00%
JWKS	🟩 Up	jwks.yml	74ms	100.00%

Visit our status website →

About

NamoID's public status page — live uptime, response time, and incident history for NamoID, the OAuth 2.1 + OIDC identity provider. It runs entirely on GitHub (Actions + Pages) via Upptime and is independent of the production EC2/Caddy stack.

What it monitors

The real public surfaces:

Service	Endpoint	Expected
Marketing	https://namoid.in	200
API — liveness	https://api.namoid.in/healthz	200
API — readiness	https://api.namoid.in/readyz	200 (returns 503 when Postgres/Redis is degraded — we want that to alert)
OIDC discovery	https://api.namoid.in/.well-known/openid-configuration	200 + "issuer" in body
JWKS	https://api.namoid.in/jwks.json	200 + "keys" in body

Dashboard (app.namoid.in) and Docs (docs.namoid.in) are commented out in .upptimerc.yml while they sit behind the pre-GA HTTP Basic Auth gate. At GA, uncomment them and flip expectedStatusCodes from 401 to 200.

How it works

• GitHub Actions probes each endpoint every ~5 min (best-effort cron — treat ~5–15 min as the real resolution).
• Response time is tracked automatically (response-time.yml).
• Incidents are logged as GitHub Issues (status label); assignees are emailed automatically by GitHub. Alerting is GitHub-native email only — no Slack/SMTP.
• setup.yml / site.yml are gated to the default branch, so config PRs don't generate merge conflicts in the auto-managed data files.

To add or change a service

Edit .upptimerc.yml under sites:. Set expectedStatusCodes to match the real response (e.g. 401 for a Basic-auth-gated host) and a maxResponseTime. Open a PR — on merge, Setup CI regenerates the page.

To post a manual incident

Open a GitHub Issue with the status label using the Incident Report template.

Secrets

Secret	Purpose
GH_PAT	Token for Actions to commit uptime data and trigger downstream workflows

Alerting is GitHub-native (issue assignees are emailed) — no Slack webhook or SMTP secret is configured.

📄 License

• Powered by: Upptime
• Code: MIT © PolyMindsLabs Pvt. Ltd.
• Data in the ./history directory: Open Database License