Website & API monitoring
Check HTTP and HTTPS responses, expected status codes and page keywords. Track response time alongside availability to spot a service that is responding slowly, not just one that is offline.
Open beta · Built for service teams
Free status pages.
A clearer picture of uptime.
Know what is happening across your websites, APIs and servers. Give your customers a status page that tells the story, not just a green light.
25 monitors. Your branding. Free during beta.
Your service statusstatus.yourcompany.com
The view your customers get
All systems operational
Website100.00% uptime
Public API99.98% uptime
Infrastructure100.00% uptime
30 days agoToday
Product illustration · Example data, not live measurements
One platform. More than a website check.HTTP / HTTPSICMP PINGTCPDNSIPv4 + IPv6
Built for both sides of an incident. The detail your team needs. The clarity your customers deserve.
From checks to communication ↓01 / Know your infrastructureThe right checks.
The right checks.
The full picture.
A website being reachable is only part of the story. Check individual services, compare probe locations, and bring your monitors together in one dashboard.
Start monitoring →Beyond the browser
Check IPv4 and IPv6 ping targets, TCP ports and DNS resolution. Monitor the network and supporting services your application depends on.
Checks from multiple locations
Compare results from monitoring probes rather than relying on one network's view. Probe consensus helps distinguish a regional failure from wider unavailability.
A dashboard that stays organised
Switch between cards and a table, filter by type or status, and group related services. Bulk controls make changes such as maintenance easier across multiple monitors.
02 / Keep people informedWhen things change,
When things change,
keep everyone in the loop.
A useful status page answers three questions: what is affected, what is being done, and what happens next.
Incident communication / Example
Investigating elevated API latency
Some requests are taking longer than expected. Our team is investigating the affected service.
Fix applied. Monitoring recovery.
Traffic has been moved to a healthy node. Response times are returning to normal.
Resolved
The service has recovered. Thank you for your patience while we worked on the issue.
Illustrative incident, not a current service announcement.
A status page that feels like yours.
Use your logo, colours and custom domain. Choose which monitors are public and organise them into service groups, so customers see a useful overview rather than your entire inventory.
- Publish incident updates with affected services and severity.
- Schedule maintenance and explain expected disruption.
- Show uptime history alongside current service health.
- Configure notification channels for your team's workflow.
DiscordSlackEmailWebhooks
03 / Go beneath the surfaceReachable is good.
Reachable is good.
Understanding why is better.
Add optional agents when you need a view inside a host. Explore CPU, memory, disk and network metrics alongside your availability checks.
Choose which supported metrics appear on public monitor pages. Keep internal details private while sharing the information your users actually need.
Agents are optional. Website, API, ping, TCP and DNS checks do not require an agent on the target. Available host metrics depend on the operating system and hardware.
Host performanceapp-server-01
- CPU utilisation
- 18.4%
- Memory used
- 4.2 / 16 GB
CPU / Last 24 hoursExample data
For developers & SaaS teams
Bring your web application, API and supporting services into one view. Give users somewhere to check before opening a support ticket.
For hosting & infrastructure
Group services by location or function. Combine network checks and optional host metrics with clear maintenance communication.
For agencies & small teams
Keep a project's monitors, branding and incident communication together in a workspace. Start with the services that matter most.
From first check to public clarity
Your status page starts here.
Create a workspace
Sign up for the free beta and give your workspace a name. Add your logo and choose the look of your public page.
Add what matters
Add your endpoints and choose suitable checks. Organise monitors into groups and decide what to share publicly.
Share your status
Publish your status page link, configure notifications and add it to your site. Use the dashboard to manage incidents and maintenance.
Start small. See the value.Useful monitoring.
Useful monitoring.
A free place to start.
VigilPing is in open beta. Start with the free plan, explore the dashboard, and publish a status page for your project.
We're building with feedback from the people using it. Found something that could work better? Join the community and tell us.
Join the VigilPing Discord →Free during beta, not a promise of permanently free access to every feature. Additional paid plans are not available yet.
Free beta
$0 / month during beta
- 25
- Monitors
- 1
- Workspace
- 3
- Probes
- 120s
- Check interval
- Branded public status page
- Incident and maintenance updates
- Custom domain support
Start with your website. Add more services when you're ready.
Community-powered perspectives
Meet our sponsors →A network made possible together.
Meet the companies contributing probe nodes to our monitoring network.
Explore the network and learn about contributing a node on our sponsors page.
Before you startA few things
A few things
worth knowing.
Answers about free status pages, monitoring and making VigilPing your own.
Read the status page guide →Is VigilPing really free?
VigilPing is free during beta. The current free plan includes 25 monitors, one workspace, three probes and 120-second checks. The pricing section describes the available offer; additional paid plans are not available yet.
What is the difference between uptime monitoring and a status page?
Uptime monitoring checks whether a service responds and records the result. A status page shares service health with users, with incident explanations and maintenance updates. VigilPing brings the checks and the communication into one platform.
Can I use my own domain, logo and colours?
Yes. Workspace settings support your logo, theme colours and a custom domain for the public status page. Follow the domain setup instructions in the dashboard and configure the required DNS record.
What can I monitor?
Monitor HTTP and HTTPS websites and APIs, IPv4 and IPv6 ping targets, TCP ports and DNS resolution. Optional host agents add metrics such as CPU utilisation, RAM, disk and network activity where supported.
Do I need to install an agent?
No agent is required on the target for website, API, ping, TCP or DNS checks. Install an agent only when you want internal host metrics. Metric availability depends on the host's operating system, hardware and configuration.
Can I keep internal monitors and metrics private?
Yes. Choose which monitors appear publicly and control supported public metrics in the dashboard. Your public status page does not need to expose your full internal monitoring inventory.
How do incidents and maintenance work?
Publish incident updates with the affected services, severity and progress. Schedule maintenance with a start and end time, and explain what customers should expect. Notification channels can send updates through Discord, Slack, email or webhooks when configured.
How quickly are services checked?
The free beta plan uses a minimum 120-second check interval. Detection and notification timing also depends on timeouts, probe results and confirmation settings; alerts are not a guarantee of instant detection.
Less uncertainty. Better communication.Give your services
Create your free status page Give your services
a place to speak.
Start monitoring. Share your status. Keep people informed.