Status

Service status

The website, the API and the MCP server, checked from outside every minute. When something goes wrong, what happened and each update are posted here.

System status

Cricket Database status

Everything is working normally

Every part of Cricket Database is answering.

Checked 6s ago

Uptime, 24 hours100%

Uptime, 7 days99.99%

Uptime, 90 days99.99%

API reply503ms

Components, last 90 days

WebsiteWorking

90 days agoToday

100%uptime, 30 days

APIWorking

90 days agoToday

99.97%uptime, 30 days

MCP serverWorking

90 days agoToday

100%uptime, 30 days

WorkingSlow, or down up to 5 minutesDown over 5 minutesHover a day for its detail. Times are UTC.

Past incidents

12 October 2026

No incidents.

11 October 2026

No incidents.

10 October 2026

ResolvedAPI unavailable05:06 to 05:14 UTC, 8 minutes

Answering normally again.

9 October 2026

No incidents.

8 October 2026

No incidents.

7 October 2026

No incidents.

6 October 2026

No incidents.

Something not working for you?

If this page says everything is working and it is not, tell us: open a ticket and we answer there.

Open a ticket Status as JSON

For your code

GET /status.json gives the same record: the state, each part and any open incident. It never needs a key.

For your monitoring

Two addresses to check from your own code. Neither needs a key and neither counts against your plan.

`https://cricketdatabase.com/status.json`

This page as data: the overall state, the uptime and each part by its key.

{"ok": true, "state": "up",
 "uptime": {"day": ..., "week": ..., "month": ..., "quarter": ...},
 "components": [{"key": "site", "state": "up", "reply_ms": ...},
  {"key": "api", ...}, {"key": "mcp", ...}],
 "incident": null}

`https://api.cricketdatabase.com/v1/status`

The API's own answer, in the same shape as every other endpoint.

{"data": {"ok": true, "matches": 23858,
  "latest_update": "2026-10-12T03:15:03Z",
  "latest_match": "2026-10-11", ...},
 "meta": {}}