https://uptimepage.dev https://uptimepage.dev/static/marketing/uptime-monitoring-dashboard.webp?v=294aa954 Dashboard — uptime, response time, and every monitor at a glance https://uptimepage.dev/static/marketing/uptime-monitors-list.webp?v=8c65527b Monitors — grouped by environment, filterable by type, tag, or owner https://uptimepage.dev/static/marketing/monitor-latency-by-region.webp?v=18af52ac Monitor detail — latency broken down by region https://uptimepage.dev/static/marketing/notification-channels-slack-pagerduty-sms.webp?v=ae28e16d Alerting — Slack, PagerDuty, SMS, webhook, and seven more https://uptimepage.dev/static/marketing/add-notification-channel.webp?v=fea8ed41 Adding a channel — pick a transport, paste one credential https://uptimepage.dev/static/marketing/public-status-page.webp?v=6d758de6 Public status page — 90 days of history per component https://uptimepage.dev/pricing https://uptimepage.dev/blog 2026-07-20 https://uptimepage.dev/blog/how-to-write-incident-status-updates 2026-07-20 https://uptimepage.dev/static/marketing/blog-incident-updates-hero.webp A large split-flap departure board updating in a dark train station at night. https://uptimepage.dev/static/marketing/blog-incident-lifecycle.webp The four incident stages in order: investigating, identified, monitoring, resolved, each with a sample status message. https://uptimepage.dev/static/marketing/blog-incident-bad-vs-good.webp A vague incident update next to a specific one that names the impact and a next-update time. https://uptimepage.dev/blog/choosing-rust-for-an-uptime-monitor 2026-07-18 https://uptimepage.dev/blog/is-98-uptime-good 2026-07-17 https://uptimepage.dev/static/marketing/blog-98-open-24-hours.webp A yellow open 24 hours sign shining on the corner of a dark brick building at night. https://uptimepage.dev/static/marketing/blog-98-uptime-year.webp One year at 98% uptime drawn as 52 weeks of day cells: four short red outage runs totalling 7.3 days scattered through a green year, labelled with the note that the 98% target is still met, and the math line 28.8 minutes per day, 14.4 hours per month, 7.3 days per year, $14,600 at $2,000 a day. https://uptimepage.dev/static/marketing/blog-98-uptime-shape.webp Two 30-day bars that both score 98% uptime: the top bar loses thirty minutes every night at 03:00, shown as thin red ticks, captioned nobody writes a postmortem; the bottom bar loses one 14.4-hour red block on launch day, captioned every customer notices. https://uptimepage.dev/static/marketing/blog-98-nines-ladder.webp Four steps rising from 98% to 99.99%, each labelled with its downtime per 30-day month, from 14.4 hours down to 4.3 minutes. The 99.9% step is outlined in green and tagged aim here. The caption reads: each step to the right costs about ten times more engineering. https://uptimepage.dev/blog/status-page-you-cant-fake 2026-07-15 https://uptimepage.dev/blog/pingdom-alternatives 2026-07-15 https://uptimepage.dev/blog/error-budgets-explained 2026-07-15 https://uptimepage.dev/static/marketing/blog-error-budget-healthy.webp Budget burn-down chart for a 99.9% SLO at 99.95% measured availability: a green line falling from full budget to the halfway mark over the month, staying above the dashed on-budget line, labelled 50% left. https://uptimepage.dev/static/marketing/blog-error-budget-overspent.webp Budget burn-down chart for a 99.9% SLO at 99.0% measured availability: an amber line dropping to zero after about a tenth of the month, far below the dashed on-budget line, labelled gone in 3d. https://uptimepage.dev/blog/clickhouse-system-tables-filled-disk 2026-07-14 https://uptimepage.dev/static/marketing/blog-disk-usage-breakdown.webp Docker disk usage broken down: images 16.2 GB, volumes 13.8 GB (Postgres and ClickHouse data), build cache 3.8 GB, containers 2.5 GB https://uptimepage.dev/static/marketing/blog-clickhouse-system-logs.webp ClickHouse system tables ranked by on-disk size: text_log 5.29 GiB, trace_log 3.02 GiB, part_log 1.11 GiB and smaller logs, next to the actual data table at 2.8 MiB https://uptimepage.dev/blog/postgres-vs-clickhouse-uptime-monitor 2026-07-08 https://uptimepage.dev/blog/http-prober-in-rust-no-reqwest 2026-07-14 https://uptimepage.dev/blog/email-bombing-uptime-pages 2026-07-04 https://uptimepage.dev/static/marketing/blog-email-flood.webp A phone home screen where the Mail app shows 6,753 unread emails https://uptimepage.dev/static/marketing/blog-hacker.webp Green binary code glowing on a screen next to a laptop keyboard in the dark https://uptimepage.dev/blog/building-an-uptime-monitor-in-rust 2026-07-14 https://uptimepage.dev/blog/best-self-hosted-uptime-monitoring-tools 2026-07-15 https://uptimepage.dev/blog/ask-dont-click 2026-06-18 https://uptimepage.dev/blog/osi-layers 2026-07-06 https://uptimepage.dev/blog/monitoring-as-code 2026-07-19 https://uptimepage.dev/blog/mcp-server 2026-07-19 https://uptimepage.dev/blog/boring-uptime 2026-05-20 https://uptimepage.dev/status-page-for-saas 2026-07-19 https://uptimepage.dev/status-page-for-agencies 2026-07-19 https://uptimepage.dev/open-source-status-page 2026-07-19 https://uptimepage.dev/open-source-uptime-monitoring 2026-07-19 https://uptimepage.dev/self-hosted-status-page 2026-07-19 https://uptimepage.dev/white-label-uptime-monitoring 2026-07-19 https://uptimepage.dev/uptime-monitoring-for-developers 2026-07-19 https://uptimepage.dev/vs/uptimerobot 2026-07-19 https://uptimepage.dev/vs/statuspage 2026-07-19 https://uptimepage.dev/vs/better-stack 2026-07-19 https://uptimepage.dev/vs/oneuptime 2026-07-19 https://uptimepage.dev/vs/uptime-kuma 2026-07-19 https://uptimepage.dev/vs/pingdom 2026-07-19 https://uptimepage.dev/vs/self-hosted-status-pages 2026-07-02 https://uptimepage.dev/vs/self-hosted-monitoring 2026-07-19 https://uptimepage.dev/compare/openstatus-vs-uptime-kuma 2026-07-05 https://uptimepage.dev/compare/uptime-kuma-vs-gatus 2026-07-17 https://uptimepage.dev/compare/pingdom-vs-statuscake 2026-07-14 https://uptimepage.dev/compare/uptime-kuma-vs-healthchecks 2026-07-14 https://uptimepage.dev/compare/uptime-kuma-vs-cachet 2026-07-14 https://uptimepage.dev/compare/openstatus-vs-gatus 2026-07-14 https://uptimepage.dev/compare/blackbox-exporter-vs-uptime-kuma 2026-07-14 https://uptimepage.dev/compare/uptime-kuma-vs-upptime 2026-07-17 https://uptimepage.dev/compare/uptime-kuma-vs-oneuptime 2026-07-17 https://uptimepage.dev/compare/uptime-kuma-vs-kener 2026-07-17 https://uptimepage.dev/compare/terraform-providers 2026-07-20 https://uptimepage.dev/terraform-status-page 2026-07-19 https://uptimepage.dev/compare/mcp-servers 2026-07-14 https://uptimepage.dev/terraform-uptime-monitoring 2026-07-19 https://uptimepage.dev/mcp-server 2026-07-19 https://uptimepage.dev/about 2026-07-21 https://uptimepage.dev/tools 2026-07-13 https://uptimepage.dev/tools/uptime-sla-calculator 2026-07-14 https://uptimepage.dev/tools/cron-expression-generator 2026-07-09 https://uptimepage.dev/tools/error-budget-calculator 2026-07-13 https://uptimepage.dev/tools/incident-update-generator 2026-07-20 https://uptimepage.dev/terms https://uptimepage.dev/privacy https://uptimepage.dev/cookies https://uptimepage.dev/impressum https://uptimepage.dev/abuse-policy https://uptimepage.dev/security-policy https://uptimepage.dev/bot