Free
For personal sites, side projects and first monitors.
Available today, no credit card.
- 3 monitors
- Checks every hour
- 30 days history
StatusPing checks websites automatically in the background, sends push alerts to your phone via ntfy and detailed e-mail alerts via Amazon SES.
Dashboard preview
Example project
statusping.kstaq.de
HTTP/HTTPS checks
Uptime
0.00%
statusping.kstaq.de
Response
118 ms
Uptime
99.98%
checkout.example.com
Response
Timeout
Uptime
98.41%
docs.example.com
Response
3,240 ms
Uptime
99.72%
Incidents open and resolve automatically when a monitor changes state.
How it works
StatusPing keeps the setup small: create a project, add monitors, then let the background checks and alerts do the routine work.
Group related websites in a project, then add each HTTP or HTTPS URL you want StatusPing to check.
Cloudflare-Edge checks run on the interval included in your plan, from hourly checks to one-minute checks.
Receive ntfy push alerts, detailed Amazon SES e-mails and a public status page for customer-facing updates.
Features
StatusPing focuses on the workflow that matters first: checks, state changes, alerts, incidents, history and public status.
StatusPing treats HTTP 200-399 as up. HTTP errors, network errors and 10s timeouts are down.
Each check records response time so slow endpoints stand out before they become incidents.
Incidents open automatically when a monitor fails and resolve automatically when it recovers.
Use the free ntfy app and high-entropy private topics generated for your alert channel.
E-mails include status, reason, response time and links back to the StatusPing dashboard.
Share a public project page at /status/your-project without exposing private dashboard data.
Alerts
StatusPing sends alerts only when monitor state changes, then applies cooldowns so repeated failures do not flood your phone or inbox.
Short messages for phones and tablets.
checkout.example.com is down
Reason: Timeout after 10s
Full context for debugging and records.
StatusPing alert: API is down
Status pages
Each project can have a public status page for customers. It shows current state, uptime windows and open incidents without dashboard-only details.
Public URL
/status/your-project
Open incidents
Current issues only.
No private data
No API keys or channels.
Public page preview
24h
100%
7d
99.94%
30d
99.91%
API recovered
One open incident remains for checkout.example.com. Customer-facing status stays clear and limited to the affected monitor.
API
Use StatusPing from scripts, deployment checks or internal tools with project-scoped API keys.
Keys use the sp_live_ prefix in clients and are stored hashed in StatusPing.
Send the key in the Authorization header to read monitor and status data.
curl -s https://statusping.kstaq.de/api/v1/monitors \
-H "Authorization: Bearer sp_live_your_api_key"The API is designed for the same MVP primitives as the dashboard: monitors, status and project-scoped access.
Pricing
The Free plan is available today. Paid plans show the intended limits and monthly pricing for the billing rollout.
For personal sites, side projects and first monitors.
Available today, no credit card.
For production websites that need faster checks.
Per month, cancel anytime.
For teams monitoring more services and customer-facing pages.
Per month, cancel anytime.
Security
StatusPing handles credentials, API keys, URLs and alerts with conservative defaults for a small monitoring product.
Passwords use scrypt hashing, and signed sessions are kept in secure HTTP-only cookies.
StatusPing stores API keys as hashes, so the raw token is only shown when it is created.
Monitor URLs go through SSRF-oriented validation before background checks are allowed to run.
Alerts are sent on status changes with cooldown handling, reducing repeated notification spam.
FAQ
StatusPing is intentionally small today. These answers describe what is available or planned for the MVP.
Use the Free plan for 3 monitors with no credit card required.