An external uptime monitoring platform with beautiful status pages, built in Koder Lang. Monitor HTTP endpoints, TCP ports, DNS, and SSL certificates from multiple global locations. Get alerted in seconds when something goes down — and keep your users informed with public or private status pages.
import uptime from "koder-uptime" // Define monitors let monitor = uptime.createMonitor({ name: "Production API", url: "https://api.company.com/health", interval: 30, // seconds locations: ["us-east", "eu-west", "ap-south"], assertions: [ { type: "status", value: 200 }, { type: "responseTime", max: 500 }, { type: "body", contains: "\"status\":\"ok\"" } ], alerts: [ { channel: "slack", after: 2 }, // after 2 failures { channel: "pagerduty", after: 3 } ] })
Everything you need, built from the ground up.
Check your services from 10+ global locations simultaneously. Distinguish between local network issues and real outages with location-aware alerting.
Public or private status pages with custom domains, incident management, scheduled maintenance windows, and real-time uptime history. No coding required.
Detect outages in under 30 seconds with high-frequency monitoring. Configurable check intervals from 30 seconds to 24 hours depending on your needs.
Monitor HTTP/HTTPS endpoints, TCP ports, DNS resolution, SSL certificate expiration, ICMP ping, and custom scripts. Validate response content and status codes.
Alert via email, SMS, Slack, Discord, webhooks, PagerDuty, and Koder Notify. Configurable confirmation rounds, escalation policies, and on-call schedules.
Run your own monitoring infrastructure. No per-monitor limits, no vendor lock-in. Deploy on a single server or distribute checkers across your own global network.
Create beautiful, branded status pages for your users with zero code.
# status-page.toml [page] title = "Company Status" domain = "status.company.com" logo = "./logo.svg" theme = "light" [[groups]] name = "Core Services" monitors = ["api", "web", "auth"] [[groups]] name = "Infrastructure" monitors = ["database", "cache", "cdn"] [subscribers] email = true webhook = true rss = true
Define multi-tier alert escalation with on-call schedules and rotation.
# alerts.toml [[policies]] name = "production-critical" confirm_rounds = 3 [[policies.tiers]] delay = "0m" channels = ["slack:#ops"] [[policies.tiers]] delay = "5m" channels = ["pagerduty:on-call"] [[policies.tiers]] delay = "15m" channels = ["sms:manager", "email:team"] [oncall] rotation = "weekly" members = ["alice", "bob", "charlie"]
See how Koder Uptime stacks up against the competition.
| Feature | Koder Uptime | UptimeRobot | Pingdom | BetterStack |
|---|---|---|---|---|
| Self-hosted option | ✓ | — | — | — |
| Beautiful status pages | ✓ | Partial | ✓ | ✓ |
| 30-second intervals | ✓ | — | ✓ | ✓ |
| Multi-location checks | ✓ | ✓ | ✓ | ✓ |
| SSL certificate monitoring | ✓ | ✓ | ✓ | ✓ |
| Incident management | ✓ | Partial | ✓ | ✓ |
| No per-monitor limits | ✓ | — | — | — |
| On-call scheduling | ✓ | — | — | ✓ |
Koder Uptime is self-hosted, so there are no monitor limits or per-check pricing. It also offers 30-second check intervals (vs 5 minutes on UptimeRobot free), built-in incident management, on-call scheduling, and more beautiful status pages.
Yes. Self-host Koder Uptime on any Linux server and monitor unlimited endpoints with no subscription fees. The only cost is your own infrastructure.
Deploy checker nodes in different regions (or use the built-in locations). Each check runs from all configured locations simultaneously. An outage is only confirmed when multiple locations report failure, eliminating false positives from localized network issues.
Yes. Koder Uptime includes a built-in status page generator with custom domains, your branding, incident history, and subscriber notifications. Users can subscribe via email, webhook, or RSS to receive status updates.
Yes. Built-in integrations include Slack, Discord, Microsoft Teams, PagerDuty, OpsGenie, email, SMS (via Twilio), webhooks, and Koder Notify. Custom integrations can be added via the webhook channel.
Know Before Your Users Do