Nothing is being checked. The scheduler last ran 4 days ago. It should run every minute. Add this one line to cron: Ask your host for the versioned CLI PHP path, then run php artisan pharos:cron with that PHP. The web PHP selector does not configure cron.

← Incidents

Report an incident

Three steps: what happened, what it affects, and what you tell customers

New incident

Published as soon as you press the button

What happened?
A short title customers recognise, and how far along you are. Use a template

Fills the title and the message. Replace any placeholder in double braces before publishing. Manage templates

Title

Status
Investigating Identified Monitoring Resolved

Impact

Visibility

Started at Backdate an incident you log afterwards. Times shown in UTC (UTC+00:00).
Which components, and their status?
Leave a component unchanged unless customers notice it. More than one is fine. Shared hosting
web-01Now operational New status for web-01

web-02Now operational New status for web-02

web-03Now operational New status for web-03

web-04Now operational New status for web-04

web-05Now operational New status for web-05

web-06Now operational New status for web-06

web-07Now operational New status for web-07

web-08Now operational New status for web-08
Email
Outbound queueNow partial outage New status for Outbound queue

IMAP and SMTPNow operational New status for IMAP and SMTP
Network and DNS
NameserversNow operational New status for Nameservers

BackupsNow operational New status for Backups
What do you tell customers?
Shown on the status page and mailed to subscribers when the incident is public.
Message to customers

Pin to the top of the status pageFor an ongoing incident people should see first. Pin

Resolve automatically when checks recoverCloses the incident after three healthy checks and posts the closing update. Resolve on recovery

Cancel

Report an incident

What happened?

Which components, and their status?

What do you tell customers?