This repository is archived.

The status page of TarkovTracker.org services can be found on :

• OnlineOrNot Status page
• Kuma Status page
• TarkovTracker.org Discord Server

Status Page

Live service status page for the TarkovTracker.org community. Runs lightweight health checks against each service and shows a 7-day incident history.

Overview

A small Express server serves a static dashboard and exposes two JSON endpoints:

Endpoint	Responsibility
GET /api/status	Runs a live health check against every configured service and returns the latest result.
GET /api/history	Returns a 7-day rolling summary of failed checks per service.

The frontend refreshes automatically every 30 seconds. A service is flagged when it times out, returns a non-2xx status, or returns a Cloudflare/bad-gateway error.

Requires Node.js 18+.

Getting started

npm install
npm run start

Open http://localhost:3000.

Configure monitored services

Edit config/services.json. Each entry describes one health check:

{
  "id": "tarkovtracker",
  "name": "TarkovTracker.org",
  "type": "web",
  "url": "https://tarkovtracker.org",
  "method": "GET"
}

The dashboard renders one card per service automatically.

Environment variables

Variable	Default	Description
PORT	3000	Port the server listens on.
STATUS_TIMEOUT_MS	5000	Per-check request timeout in milliseconds.
HISTORY_INTERVAL_MS	300000	How often background checks run for history tracking.

Project structure

status/
├── server.js              # Express server: health checks + API
├── config/
│   └── services.json      # List of monitored services
└── public/                # Static dashboard
    ├── index.html
    ├── styles.css
    └── app.js

License

Released under the MIT License.