Status page and incident notices
Read the components and uptime of the independent public status page, and publish and resolve incident and maintenance notices in Turkish and English.
The Status page screen manages the public status page, which is built to be hosted independently of the main servers. The page shows six components: Dashboard and API, Guest captive portal, RADIUS / AAA, Law 5651 logging and timestamping, VPN gateway and Website.
Components and uptime
The worker probes the components every 2 minutes and records the result. The table shows the latest probe; the 30 days and 90 days percentages are computed only from these probe records:
- Degraded (slow but reachable) counts as available.
- No data (the probe could not read the signal) is excluded.
- Intervals with no probe record at all (server, PM2 or worker down) count as downtime for the dashboard/API and the portal. For other components they are excluded but shown next to the percentage on the status page as "... min unmeasured".
- Percentages are rounded down; 99.996% never shows as "100%".
If the latest probe is older than 10 minutes, the component shows No data: check the worker on the Server status screen.
Opening an incident
- Click New incident.
- Optionally pick a Template; the title and message are filled in TR/EN.
- Choose the Type (Incident or Scheduled maintenance), the Impact and the Affected components.
- For maintenance, optionally enter a Planned start (at most 90 days ahead).
- Edit the message and publish it with Publish.
A future maintenance is announced in the Scheduled maintenance section of the status page until it starts; it does not change component or overall status. If you resolve (cancel) a maintenance before it starts, its start time is moved to the moment it was resolved.
If an open incident's impact is worse than the probe status of its components, the page shows the incident. You can announce an outage before the probes catch it. Uptime is not affected by incidents.
Messages are public
The Turkish message is required; if English is empty, the English page shows the Turkish text. Do not put customer names, IP addresses or internal details in messages.
Updating and resolving
- Add update: adds a new status (Identified, Monitoring) and a public message.
- Resolve: resolves the incident with a closing message. Resolved incidents take no further updates and stay in the history for 14 days.
- Edit: fixes the title, impact and components (publishes no message).
Every action is written to the audit log. Changes reach the summary endpoint within 1 minute and the static page on its next build (recommended interval: 5 minutes).
SLA
The SLA text with a 99.5% target and the credit policy stay a draft until 90 days of measurements are collected; the line at the bottom of the screen shows the measured days. Even after 90 days the SLA is not published automatically; it needs approval.