How to Check Service Status
During incidents, our status page is the single source of truth for current impact, affected components, and recovery updates.
1) Open the official status page
Check khaleejiapi.dev/status first. For machine-readable checks, use GET /api/v1/status, which returns the centralized incident feed as JSON with overall and per-service status details. Current fields: { overall, updatedAt, services[], uptime }.
To monitor liveness directly, KhaleejiAPI also provides two dedicated health endpoints:
GET /api/v1/ping— unauthenticated, always returns{ ok: true }(HTTP 200) as long as the platform is reachable. Use this for uptime monitors and load-balancer health checks.GET /api/v1/health— requires anAuthorization: BearerAPI key. Returns a detailed subsystem breakdown (HTTP 200 when healthy, 503 when degraded). Use this for authenticated, server-side monitoring dashboards. See full documentation →
2) Understand status levels
Operational
All services are healthy and responding within normal performance targets.
Degraded Performance
Services are available, but response times are slower than normal for some users.
Partial Outage
One or more features or APIs are unavailable, while the rest of the platform remains online.
Major Outage
A broad outage affecting multiple core services or most customer traffic.
3) Incident communication policy
- Status updates are posted on the status page as soon as we confirm an incident.
- We continue posting progress updates there until full resolution.
- For major incidents, we may also post short updates on social media channels.
- Post-incident summaries are published on the status page when available.
x-request-id when contacting [email protected].