Quick Start: Setup in 5 Minutes
Uptime monitoring without delays — go from sign-up to live monitoring in under five minutes.
Create Free Account Read Full DocsGet your first monitor running
Four steps, zero configuration files. Follow along and you'll have real-time uptime tracking for your production endpoints before your coffee gets cold.
Create your account
Head to app.pingkit.io/register and sign up with your work email. No credit card required for the free tier — you get 3 monitors, 60-second check intervals, and email notifications out of the box. Verification takes about 12 seconds.
Add your first monitor
Click Monitors → Add Monitor from the sidebar. Enter the URL you want to track — for example https://api.yourcompany.com/health. Choose HTTP GET as the method, set the expected status code to 200, and pick a check interval (60s, 300s, or 600s). PingKit supports HTTPS, TCP, and ICMP checks from 12 global probe locations.
Configure notifications
Go to Settings → Notifications and add at least one alert channel. Email is enabled by default. To add Slack, paste your incoming webhook URL (looks like https://hooks.slack.com/services/T02ABC/B03XYZ/qR7sT...). You can also configure PagerDuty, VictorOps, or a custom webhook. Set your escalation policy so critical outages reach your on-call engineer within 30 seconds.
Verify everything works
Return to your monitor dashboard. You should see the first health check result within 60 seconds of creation. The status badge will read Operational with a response time in milliseconds. To confirm alerts fire, temporarily change your expected status code to 404 — you'll receive a "Monitor Down" notification within one check cycle. Revert the setting immediately after testing.
Dashboard walkthrough
Here's a preview of the screens you'll encounter during setup, so you know exactly where to click.
Monitor creation form
The form appears at /monitors/new. Fields include: monitor name (e.g., "Production API — EU-West"), target URL, protocol (HTTPS/TCP/ICMP), check interval, timeout threshold (default 10s), and expected response body match. You can enable SSL certificate expiry tracking here — it alerts you 30 days before expiration.
Live status dashboard
After your first check completes, the dashboard shows a real-time status table with columns for monitor name, current state, last response time, uptime percentage (calculated over the last 24h, 7d, and 30d), and number of incidents. Each row links to a detailed timeline view with per-probe-location results.
Notification settings panel
Found at /settings/notifications. You'll see a list of configured channels with toggle switches for each severity level (Info, Warning, Critical). Each channel displays a "Send Test" button so you can verify delivery before trusting it with real alerts. Rate limiting is set to one alert per 5 minutes per channel by default.
What to do next
Your first monitor is live. Here's how to make PingKit work harder for your team.
Add monitors for every critical endpoint
Don't stop at one. Add monitors for your login page, checkout flow, WebSocket endpoint, and DNS resolution. Each monitor can be tagged (e.g., production, payments) so you can filter the dashboard by service tier.
Set up status pages
Create a public status page at yourcompany.status.pingkit.io in under a minute. Embed it in your app's footer so customers can self-serve outage information. Status pages automatically reflect monitor states and support custom incident posts with markdown formatting.
Invite your team
Go to Settings → Team and add engineers by email. Assign roles: Admin (full access), Editor (manage monitors and alerts), or Viewer (read-only dashboard access). Team members receive their own notification preferences independently.
Explore API and integrations
PingKit's REST API lets you programmatically create monitors, fetch uptime history, and trigger synthetic checks. Use the API key from /settings/api-keys. Webhooks fire on state changes with a JSON payload containing monitor ID, previous state, new state, and timestamp — ideal for feeding into your own incident management pipeline.
Quick Start: Setup in 5 Minutes
Uptime monitoring without delays — go from sign-up to live monitoring in under five minutes.
Create Free Account Read Full DocsGet your first monitor running
Four steps, zero configuration files. Follow along and you'll have real-time uptime tracking for your production endpoints before your coffee gets cold.
Create your account
Head to app.pingkit.io/register and sign up with your work email. No credit card required for the free tier — you get 3 monitors, 60-second check intervals, and email notifications out of the box. Email verification takes about 12 seconds.
Add your first monitor
Click Monitors → Add Monitor from the sidebar. Enter the URL you want to track — for example https://api.yourcompany.com/health. Choose HTTP GET as the method, set the expected status code to 200, and pick a check interval (60s, 300s, or 600s). PingKit supports HTTPS, TCP, and ICMP checks from 12 global probe locations.
Configure notifications
Go to Settings → Notifications and add at least one alert channel. Email is enabled by default. To add Slack, paste your incoming webhook URL (looks like https://hooks.slack.com/services/T02ABC/B03XYZ/qR7sT...). You can also configure PagerDuty, VictorOps, or a custom webhook. Set your escalation policy so critical outages reach your on-call engineer within 30 seconds.
Verify everything works
Return to your monitor dashboard. You should see the first health check result within 60 seconds of creation. The status badge will read Operational with a response time in milliseconds. To confirm alerts fire, temporarily change your expected status code to 404 — you'll receive a "Monitor Down" notification within one check cycle. Revert the setting immediately after testing.
Dashboard walkthrough
Here's a preview of the screens you'll encounter during setup, so you know exactly where to click.
Monitor creation form
The form appears at /monitors/new. Fields include: monitor name (e.g., "Production API — EU-West"), target URL, protocol (HTTPS/TCP/ICMP), check interval, timeout threshold (default 10s), and expected response body match. You can enable SSL certificate expiry tracking here — it alerts you 30 days before expiration.
Live status dashboard
After your first check completes, the dashboard shows a real-time status table with columns for monitor name, current state, last response time, uptime percentage (calculated over the last 24h, 7d, and 30d), and number of incidents. Each row links to a detailed timeline view with per-probe-location results.
Notification settings panel
Found at /settings/notifications. You'll see a list of configured channels with toggle switches for each severity level (Info, Warning, Critical). Each channel displays a "Send Test" button so you can verify delivery before trusting it with real alerts. Rate limiting is set to one alert per 5 minutes per channel by default.
What to do next
Your first monitor is live. Here's how to make PingKit work harder for your team.
Add monitors for every critical endpoint
Don't stop at one. Add monitors for your login page, checkout flow, WebSocket endpoint, and DNS resolution. Each monitor can be tagged (e.g., production, payments) so you can filter the dashboard by service tier.
Set up status pages
Create a public status page at yourcompany.status.pingkit.io in under a minute. Embed it in your app's footer so customers can self-serve outage information. Status pages automatically reflect monitor states and support custom incident posts with markdown formatting.
Invite your team
Go to Settings → Team and add engineers by email. Assign roles: Admin (full access), Editor (manage monitors and alerts), or Viewer (read-only dashboard access). Team members receive their own notification preferences independently.
Explore API and integrations
PingKit's REST API lets you programmatically create monitors, fetch uptime history, and trigger synthetic checks. Use the API key from /settings/api-keys. Webhooks fire on state changes with a JSON payload containing monitor ID, previous state, new state, and timestamp — ideal for feeding into your own incident management pipeline.