Tell customers what is down before they have to ask.

• Overall stateThe worst state among the components you show, in words and in colour.
• ComponentsIn groups, each with its state, a bar for every day of up to 90 days and, if you like, its uptime.
• IncidentsFrom investigating to resolved, with every update kept. A published update is corrected, never removed.
• MaintenanceAnnounce planned work with a window. Yuva starts and completes it on time.
• HistoryPast incidents and maintenance by month, each with its own page.
• Response timesWhen you turn it on: the last 24 hours of each component with an HTTP or TCP check, with median and p95.
• Feed, badge and JSONAn Atom feed that needs no subscription, a badge for your README, and the same page as JSON for your own site or app.
• Your look and languageYour logo and accent colour. The page speaks English, Turkish and German; visitors see times in their own time zone.

A page stays private until you publish it, and your team previews it in the panel before that.

• HeartbeatsYour cron job or server calls a URL on a schedule. When the calls stop, the component goes down.
• Pushed statesSend a working or an outage state yourself. Alertmanager and Grafana alerts are accepted as they are.
• HTTPYuva requests a URL on an interval and checks the status code, optionally a keyword and the certificate's expiry.
• TCPYuva opens a connection to a host and port and checks that it answers.

• Incidents drafted for youWhen a check goes down, Yuva can open a draft incident for you to review, publish one at once, or open none. When it recovers, Yuva resolves what it opened.
• Your word firstYou choose how many failures in a row count, and a state your team set by hand is never overridden by a check.

• Double opt-inThe answer is the same for every address, and nobody is subscribed without confirming.
• Their choiceOne checkbox per component, and a link in every mail to change it or leave.
• Plain noticesThe state in words, the affected components and the updates, with no images, tracking or promotion. In English, Turkish or German.
• Held, then sentA notice waits 60 seconds so you can undo it, and notices about one incident keep their distance, so a long outage does not flood inboxes.

Notices go out through your inbox's own e-mail channel, from its address, and the people on the list are kept apart from your newsletters.

• 01Link conversations to the incident in the panel. The incident page lists them.
• 02Write one reply. Review shows how many conversations get it, and you can close each one afterwards.
• 03Yuva sends it as you to every linked conversation that is still open, through each one's own channel. It cannot be recalled once sent.

• CertificatesIssued and renewed automatically, by an on-demand proxy such as Caddy or by Cloudflare custom hostnames.
• Everything movesLinks, the feed, the badge, the JSON and e-mail notices all use your domain.
• Only yoursOnly the page is served on your domain, never the API or the panel.

<script src="https://support.example.com/yuva-status.js" defer></script>
<yuva-status page="acme" theme="auto" components></yuva-status>

• pageThe address of your status page.
• themelight, dark or auto, which follows the visitor's colour scheme. The default is auto.
• componentsAdd it for a second row with each component's state.