Your websites are being watched.
Veyra checks availability, HTTP status, response time and SSL security so you can quickly see when something feels off.
How fast did it answer?
No checks yetSystem status
LiveWhat happened lately
Real monitoring activityMonitored websites
| Website | Status | HTTP | Response | SSL | |
|---|---|---|---|---|---|
| Loading... | |||||
Check history
| Website | Status | HTTP | Response | SSL | Checked |
|---|---|---|---|---|---|
| Loading... | |||||
What does Veyra actually check?
You don't need to understand servers or networking to use Veyra. It checks the important parts of a website and turns the results into simple information.
Availability
Veyra connects to your website to see whether it can be reached.
HTTP status
It checks the server response such as 200, 404 or 500.
Response time
Veyra measures how long the website takes to respond.
SSL security
It checks whether HTTPS is valid and how many days remain before the certificate expires.
Why retries?
A single failed request does not always mean that a website is actually down. Veyra can retry the check before creating an incident, reducing false alarms.
Your alerts, your inbox.
Create an account and verify your email. Then choose which monitored websites should send you outage and recovery notifications.
Create an account
Use a real email address so you can receive the verification code.
Verify email
Enter the six-digit code sent to your email. The code expires in 10 minutes.
Log in
You must verify your email before logging in.
Website alert subscriptions
Subscribe to any website already listed in Veyra. Alerts are sent only after an incident is confirmed or resolved.
Log in to manage your subscriptions.
Monitoring settings
Automatic monitoring
Automatically check monitored websites.
Monitoring interval
How often Veyra performs automatic checks.
Retry attempts
Additional attempts before a failure is confirmed.
Email alerts
Send an email when a website goes down or recovers.
Alert recipient
Email address that should receive Veyra alerts.
Email delivery requires valid SMTP credentials in your project's .env file. A test email confirms whether the current configuration can send messages.