An engineer monitoring data servers with a laptop in a server room

RESOURCES → DEVELOPER CENTER → SYSTEM STATUS

DISHA Platform Health.

The operational source of truth for platform availability — separating current health from historical incidents and scheduled maintenance, with explicit timestamps and auditable status transitions.

Is DISHA operating normally, what is affected, and what should I do?

Developer honesty: no public API, SDK packages, webhook deliveries, release history or status monitoring are live yet. Every contract, payload and console below is a clearly-labeled illustrative design — no fabricated endpoints, SDK support, incidents or uptime figures.

One Developer Center · six connected surfacesDocumentation How do I understand/build this?API Reference What exactly is the contract?SDKs How do I build this in my stack?Webhooks How do I respond to events?Release Notes What changed and what must I do?System Status Is anything operationally wrong?

Status system not connected. This preview environment runs no public status monitoring, so no health state is claimed — not even "operational". When the authoritative status system connects, this banner reports one of the four documented states below, driven by real monitoring.

Service health model

API

— not monitored here · last updated: —

Authentication

— not monitored here · last updated: —

Webhooks

— not monitored here · last updated: —

AI services

— not monitored here · last updated: —

Data/Storage

— not monitored here · last updated: —

Developer Portal

— not monitored here · last updated: —

Experience surfaces

— not monitored here · last updated: —

Background workers

— not monitored here · last updated: —

Health states — documented and consistent

All Systems Operational

All monitored components normal

Degraded Performance

Operating with reduced performance

Partial Outage

Some components unavailable

Major Outage

Core systems unavailable

Status reflects monitored service health — it never implies every customer workflow is unaffected unless that has been established.

Incident history

No incident history exists.

Nothing is fabricated here: no invented outages, no made-up uptime percentages. Availability statistics appear only when based on a defined measurement method and period.

Maintenance center

Upcoming maintenance shows its window, affected components, expected behavior, any customer action and the update cadence — and links to Release Notes and Documentation. None is scheduled yet — nothing invented.

Historical reliability

No uptime figure is displayed — none can be honestly computed yet. When reliability statistics appear, they will publish their measurement method and period alongside the number.

Status governance: incident communications have operational ownership; timestamps and status transitions are auditable; security incidents follow controlled disclosure; subscriptions are reliable and accessible. The Developer Center is ready only when a developer can move from a conceptual question to a working integration — and from a production problem back to the exact contract, event, release or incident that explains it — without contradictory definitions or undocumented behavior.

Was this page accurate?