Skip to content
PramaanDPDP Live
Public reliability

PRAMAAN Status

Public uptime and component health for Web, API, and Apps. This dashboard reports known telemetry and labels incomplete history clearly.

Overall state
Operational
Last snapshot
22/6/2026, 9:44:31 am IST
No active incidents.
Incident log
Operational

Web

Marketing site, pricing, trust center, help, and public conversion pages.

Target
200 OK under 2000 ms
Latency
91 ms
HTTP
200
Owner
PRAMAAN Web

Known history: 15 of 30 dates · 6.67% over known window

24 May: Unknown25 May: Unknown26 May: Unknown27 May: Unknown28 May: Unknown29 May: Unknown30 May: Unknown31 May: Unknown1 Jun: Unknown2 Jun: Unknown3 Jun: Unknown4 Jun: Unknown5 Jun: Unknown6 Jun: Unknown7 Jun: Degraded8 Jun: Degraded9 Jun: Down10 Jun: Down11 Jun: Down12 Jun: Down13 Jun: Down14 Jun: Down15 Jun: Unknown16 Jun: Down17 Jun: Down18 Jun: Down19 Jun: Down20 Jun: Down21 Jun: Down22 Jun: Operational
Operational

API

Hono verification, badge, chat, auth, DSR, and partner APIs.

Target
200 OK under 2000 ms
Latency
53 ms
HTTP
200
Owner
PRAMAAN Backend

Known history: 15 of 30 dates · 20.00% over known window

24 May: Unknown25 May: Unknown26 May: Unknown27 May: Unknown28 May: Unknown29 May: Unknown30 May: Unknown31 May: Unknown1 Jun: Unknown2 Jun: Unknown3 Jun: Unknown4 Jun: Unknown5 Jun: Unknown6 Jun: Unknown7 Jun: Operational8 Jun: Down9 Jun: Down10 Jun: Down11 Jun: Down12 Jun: Down13 Jun: Down14 Jun: Down15 Jun: Unknown16 Jun: Down17 Jun: Operational18 Jun: Down19 Jun: Degraded20 Jun: Down21 Jun: Down22 Jun: Operational
Operational

Apps

Worker and resident app web assets, manifest, and update surface.

Target
manifest reachable under 2000 ms
Latency
81 ms
HTTP
200
Owner
PRAMAAN Apps

Known history: 15 of 30 dates · 6.67% over known window

24 May: Unknown25 May: Unknown26 May: Unknown27 May: Unknown28 May: Unknown29 May: Unknown30 May: Unknown31 May: Unknown1 Jun: Unknown2 Jun: Unknown3 Jun: Unknown4 Jun: Unknown5 Jun: Unknown6 Jun: Unknown7 Jun: Down8 Jun: Down9 Jun: Down10 Jun: Down11 Jun: Down12 Jun: Down13 Jun: Down14 Jun: Degraded15 Jun: Unknown16 Jun: Down17 Jun: Down18 Jun: Degraded19 Jun: Down20 Jun: Down21 Jun: Degraded22 Jun: Operational

Uptime over known telemetry window

Known history only: 15 of 30 dates. Unknown dates are not counted as downtime.

11.11% known-window average
24 May: Unknown25 May: Unknown26 May: Unknown27 May: Unknown28 May: Unknown29 May: Unknown30 May: Unknown31 May: Unknown1 Jun: Unknown2 Jun: Unknown3 Jun: Unknown4 Jun: Unknown5 Jun: Unknown6 Jun: Unknown7 Jun: Down8 Jun: Down9 Jun: Down10 Jun: Down11 Jun: Down12 Jun: Down13 Jun: Down14 Jun: Down15 Jun: Unknown16 Jun: Down17 Jun: Down18 Jun: Down19 Jun: Down20 Jun: Down21 Jun: Down22 Jun: Operational
OperationalDegradedDownUnknown / no samples

Incident history

Public incident status is intentionally simple until incident history grows.

  1. No active incidents

    Clear

    No active incident is currently published in the status summary.

Reliability is more useful when the data is honest.

Use the JSON feed, incident log, docs, or support path for operational review.