Edit Billing

Name iThe name shown on the public page and in this list. Use whatever your customers will recognise: a service name or a server name, whichever they know.

Status iThe status shown right now. A Pharos check overwrites this on its next run, except Under maintenance, which stays until you clear it. With Manual only it stays exactly as you set it. Operational Degraded performance Partial outage Major outage Under maintenance

Group iThe service this appears under on the public page. Ungrouped is published too, as a row of its own without a heading. Ungrouped Internal tools × + New service Click a service to put this component in it. The × deletes the service itself.

Link iOptional. Turns the name on the public page into a link that opens in a new tab. http and https only.

Tags iOnly returned by the API, for scripts written against Cachet. Nothing inside Pharos reads them. Comma separated.

Source iWho sets this status. Checked by Pharos: Pharos tests it itself, over HTTP, TCP or a heartbeat from your job. Set from outside: Uptime Kuma, n8n or a script writes it through the API. Manual only: you set it here. Pharos marks a service as set from outside by itself the first time the API or Uptime Kuma writes its status. HTTP or TCP check Heartbeat from your job Uptime Kuma API or webhook (n8n, scripts) Upstream provider Manual only

Check iHTTP GET fetches the URL and counts 200 through 399 as up. TCP port only opens a socket: for mail, databases, anything without a web page. HTTP GET DNS record TCP port

Interval (seconds) iHow often to look, minimum 30 seconds. Two failures in a row turn it red and open an incident; the first success turns it green, and three in a row close the incident.