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/architecture 2026-08-03 https://uptimepage.dev/blog 2026-09-22 https://uptimepage.dev/blog/uml-viewer-rust-dependency-cycles 2026-09-22 https://uptimepage.dev/static/marketing/blog-uml-viewer-layers.webp Two panels of five stacked layers, vocabulary at the bottom and assembly at the top. Before: five red arrows point up from storage and config into api, worker, auth and billing, and two grey loops mark cycles between api and web and between storage and quotas. After: the same modules plus dashed green boxes for request, templates, security and pagination, and every arrow points down or sideways. https://uptimepage.dev/static/marketing/blog-uml-viewer-before-after.webp Four paired horizontal bars, red for before and green for after: Dependency Rule violations 167 to 109, module pairs importing each other 35 to 3, modules importing api 17 to 4, lines in app.rs 1,087 to 642. https://uptimepage.dev/static/marketing/blog-uml-viewer-rounds.webp A line chart over seven points from start to round six. Module pairs importing each other fall 35, 28, 23, 19, 16, 8, 3. Modules importing api fall 17, 11, 9, 6, 6, 6, 4. Under each round a short label names what moved. https://uptimepage.dev/blog/how-to-debug-redirect-loops 2026-09-05 https://uptimepage.dev/blog/how-to-monitor-ssl-certificate-expiry 2026-09-18 https://uptimepage.dev/blog/uptime-kuma-rest-api 2026-09-05 https://uptimepage.dev/blog/why-dns-returns-different-ip-addresses 2026-09-05 https://uptimepage.dev/blog/icmp-vs-tcp-vs-udp 2026-09-02 https://uptimepage.dev/static/marketing/blog-icmp-tcp-udp-exchanges.webp ICMP echo, TCP three-way handshake and UDP datagram drawn as three lanes between you and a host, each ending with what silence means on that protocol. https://uptimepage.dev/blog/cron-jobs-fail-silently 2026-08-27 https://uptimepage.dev/blog/monitor-an-mcp-server 2026-08-18 https://uptimepage.dev/static/marketing/blog-mcp-shallow-health-check.webp A GET stops at the proxy and health handler and returns a green 200, while a POST initialize reaches the JSON-RPC handler behind it and finds it broken. https://uptimepage.dev/blog/statuspage-alternatives 2026-08-06 https://uptimepage.dev/static/marketing/blog-statuspage-two-tool-flow.webp A monitor detects an outage, Statuspage publishes the incident, and subscribers receive the update, showing that monitoring and communication are two separate products and bills. https://uptimepage.dev/static/marketing/blog-statuspage-choice-tree.webp A decision tree for choosing a Statuspage alternative based on whether you are replacing only the page or both monitoring and the page, with hosted and self-hosted options. https://uptimepage.dev/blog/uptime-sla 2026-08-06 https://uptimepage.dev/blog/rust-scheduler-one-heap 2026-08-05 https://uptimepage.dev/blog/how-much-downtime-is-99-9-uptime 2026-08-02 https://uptimepage.dev/blog/how-much-downtime-is-99-95-uptime 2026-08-02 https://uptimepage.dev/blog/how-much-downtime-is-99-99-uptime 2026-08-02 https://uptimepage.dev/blog/monitor-the-login-not-the-login-page 2026-09-05 https://uptimepage.dev/static/marketing/blog-login-http-stops-at-200.webp HTTP monitoring stops at 200 OK, leaving the login form, authentication, session cookie and dashboard untested. https://uptimepage.dev/static/marketing/blog-login-four-failures.webp Four login failures that keep HTTP monitoring green: an expired OAuth secret, missing JavaScript, a dropped session cookie and a bot challenge. https://uptimepage.dev/static/marketing/blog-login-detection-gap.webp A server outage triggers an immediate alert, while a broken login stays green until failed attempts and support reports expose it. https://uptimepage.dev/static/marketing/blog-login-five-claims.webp A five-step browser login check fills both fields, submits the form, then verifies the dashboard URL and text to prove sign-in worked. https://uptimepage.dev/blog/your-login-test-never-runs-in-production 2026-08-02 https://uptimepage.dev/static/marketing/blog-login-ci-production-gap.webp A passing CI login test compared with a broken production login caused by real secrets, CDN assets, cookie rules and bot protection. https://uptimepage.dev/static/marketing/blog-login-two-clocks.webp CI runs a login test once per pull request, while production monitoring repeats the journey every five to fifteen minutes and alerts when it fails. https://uptimepage.dev/static/marketing/blog-login-day-one-blockers.webp Three practical monitoring paths: verify the two-factor code screen, verify the magic-link confirmation page, or bypass a bot wall or monitor a reachable endpoint. https://uptimepage.dev/static/marketing/blog-login-selector-durability.webp Broad and fragile browser selectors compared with a stable data-testid hook, with iframe and shadow DOM boundaries marked as unreachable. https://uptimepage.dev/static/marketing/blog-login-alert-evidence.webp One failed browser run is recorded without paging anyone; a second consecutive failure confirms the incident, sends an alert and preserves scrubbed page evidence. https://uptimepage.dev/blog/stop-false-uptime-alerts 2026-07-25 https://uptimepage.dev/blog/domain-expired-but-site-still-up 2026-09-05 https://uptimepage.dev/static/marketing/blog-domain-expiry-hero.webp A server topped with a dark error cross, while two monitoring checks beside it still show green success ticks. https://uptimepage.dev/static/marketing/blog-domain-expiry-server-down.webp An illustration of a server disconnected from its monitor, the link between them broken. https://uptimepage.dev/blog/map-your-codebase-for-ai-agents 2026-07-23 https://uptimepage.dev/static/marketing/blog-map-codebase-flow.webp The interactive architecture map: columns of labelled boxes from Actors and Ingress through Edge and Routing, HTTP Handlers, Core Services, the Probe Engine and Stores, with one flow lit up as a numbered amber path across them. https://uptimepage.dev/static/marketing/blog-map-codebase-hero.webp A scattered codebase of many small files on the left flows through an amber arrow into a single JSON map file marked with a green source dot, which then branches into a human-readable page and an interactive node map. https://uptimepage.dev/static/marketing/blog-map-codebase-method.webp Four steps left to right joined by an amber line: explore in parallel across several small files, build one large JSON map file with a green source dot, check the numbers in it with a magnifying glass, then render the views into two output cards. The map is drawn largest as the anchor. https://uptimepage.dev/blog/do-i-need-an-uptime-monitor 2026-09-05 https://uptimepage.dev/static/marketing/blog-monitor-need-hero.webp A shop door locked at night with a handwritten back in five minutes note taped to the glass. https://uptimepage.dev/static/marketing/blog-outage-cost-iceberg.webp A stack showing the small visible cost of an outage above a waterline and the larger hidden costs of ad spend, support, SLA credits and trust below it. https://uptimepage.dev/static/marketing/blog-detection-gap.webp Two timelines of the same outage: without a monitor nobody knows for four hours, with a monitor detection takes two minutes. https://uptimepage.dev/static/marketing/blog-homepage-check-blind-spots.webp A green homepage check above six failing checks for the database, certificate, domain, DNS, backup job and login form. 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-08-03 https://uptimepage.dev/blog/is-98-uptime-good 2026-08-03 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-08-08 https://uptimepage.dev/blog/pingdom-alternatives 2026-08-08 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-08-03 https://uptimepage.dev/blog/http-prober-in-rust-no-reqwest 2026-09-18 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-08-05 https://uptimepage.dev/blog/best-self-hosted-uptime-monitoring-tools 2026-09-05 https://uptimepage.dev/blog/ask-dont-click 2026-06-18 https://uptimepage.dev/blog/osi-layers 2026-09-05 https://uptimepage.dev/blog/monitoring-as-code 2026-08-18 https://uptimepage.dev/blog/mcp-server 2026-08-18 https://uptimepage.dev/blog/boring-uptime 2026-07-24 https://uptimepage.dev/status-page-for-saas 2026-08-11 https://uptimepage.dev/status-page-for-agencies 2026-08-08 https://uptimepage.dev/open-source-status-page 2026-08-11 https://uptimepage.dev/open-source-uptime-monitoring 2026-09-03 https://uptimepage.dev/white-label-uptime-monitoring 2026-08-08 https://uptimepage.dev/uptime-monitoring-for-developers 2026-09-18 https://uptimepage.dev/cron-job-monitoring 2026-08-27 https://uptimepage.dev/browser-login-monitoring 2026-07-31 https://uptimepage.dev/vs/uptimerobot 2026-09-03 https://uptimepage.dev/vs/statuspage 2026-08-11 https://uptimepage.dev/vs/better-stack 2026-09-03 https://uptimepage.dev/vs/oneuptime 2026-09-03 https://uptimepage.dev/vs/uptime-kuma 2026-09-03 https://uptimepage.dev/vs/pingdom 2026-09-03 https://uptimepage.dev/vs/self-hosted-status-pages 2026-09-03 https://uptimepage.dev/vs/self-hosted-monitoring 2026-09-03 https://uptimepage.dev/compare/openstatus-vs-uptime-kuma 2026-09-03 https://uptimepage.dev/compare/uptime-kuma-vs-gatus 2026-08-11 https://uptimepage.dev/compare/pingdom-vs-statuscake 2026-09-03 https://uptimepage.dev/compare/uptime-kuma-vs-healthchecks 2026-08-11 https://uptimepage.dev/compare/uptime-kuma-vs-cachet 2026-08-11 https://uptimepage.dev/compare/openstatus-vs-gatus 2026-09-03 https://uptimepage.dev/compare/blackbox-exporter-vs-uptime-kuma 2026-09-03 https://uptimepage.dev/compare/uptime-kuma-vs-zabbix 2026-09-03 https://uptimepage.dev/compare/uptime-kuma-vs-upptime 2026-09-03 https://uptimepage.dev/compare/uptime-kuma-vs-oneuptime 2026-09-03 https://uptimepage.dev/compare/uptime-kuma-vs-kener 2026-08-11 https://uptimepage.dev/compare/terraform-providers 2026-08-11 https://uptimepage.dev/compare/terraform-uptime-kuma 2026-08-11 https://uptimepage.dev/compare/terraform-uptimerobot 2026-08-11 https://uptimepage.dev/compare/terraform-statuspage 2026-08-11 https://uptimepage.dev/terraform-status-page 2026-07-19 https://uptimepage.dev/compare/mcp-servers 2026-08-11 https://uptimepage.dev/terraform-uptime-monitoring 2026-08-19 https://uptimepage.dev/mcp-server 2026-09-17 https://uptimepage.dev/mcp-server/claude 2026-09-17 https://uptimepage.dev/mcp-server/cursor 2026-09-17 https://uptimepage.dev/mcp-server/vscode 2026-09-17 https://uptimepage.dev/mcp-server/grok 2026-09-17 https://uptimepage.dev/why-uptimepage 2026-08-19 https://uptimepage.dev/about 2026-08-27 https://uptimepage.dev/tools 2026-09-18 https://uptimepage.dev/tools/uptime-sla-calculator 2026-09-04 https://uptimepage.dev/tools/cron-expression-generator 2026-09-04 https://uptimepage.dev/tools/error-budget-calculator 2026-09-04 https://uptimepage.dev/tools/incident-update-generator 2026-09-04 https://uptimepage.dev/tools/dns-lookup 2026-08-05 https://uptimepage.dev/tools/http-header-checker 2026-09-18 https://uptimepage.dev/tools/ssl-certificate-checker 2026-09-18 https://uptimepage.dev/tools/domain-expiry-checker 2026-09-05 https://uptimepage.dev/tools/website-security-checker 2026-09-18 https://uptimepage.dev/docs 2026-09-21 https://uptimepage.dev/docs/getting-started 2026-09-08 https://uptimepage.dev/docs/overview 2026-08-27 https://uptimepage.dev/docs/architecture 2026-09-20 https://uptimepage.dev/docs/ui 2026-09-08 https://uptimepage.dev/docs/incidents 2026-09-08 https://uptimepage.dev/docs/monitor-types 2026-09-17 https://uptimepage.dev/docs/notifications 2026-09-11 https://uptimepage.dev/docs/public-status 2026-09-20 https://uptimepage.dev/docs/per-org-status 2026-09-10 https://uptimepage.dev/docs/share-links 2026-08-30 https://uptimepage.dev/docs/team 2026-09-05 https://uptimepage.dev/docs/organizations 2026-09-07 https://uptimepage.dev/docs/variables 2026-09-06 https://uptimepage.dev/docs/authentication 2026-09-17 https://uptimepage.dev/docs/api 2026-09-20 https://uptimepage.dev/docs/terraform 2026-09-08 https://uptimepage.dev/docs/mcp 2026-09-19 https://uptimepage.dev/docs/quotas 2026-09-15 https://uptimepage.dev/docs/multi-tenancy 2026-09-10 https://uptimepage.dev/docs/hosted/plans-and-limits 2026-09-15 https://uptimepage.dev/docs/hosted/regions 2026-09-08 https://uptimepage.dev/docs/hosted/data-retention 2026-09-10 https://uptimepage.dev/docs/hosted/support 2026-08-07 https://uptimepage.dev/docs/configuration 2026-09-21 https://uptimepage.dev/docs/deployment 2026-09-21 https://uptimepage.dev/docs/kubernetes 2026-09-21 https://uptimepage.dev/docs/multi-region 2026-09-11 https://uptimepage.dev/docs/metrics 2026-09-20 https://uptimepage.dev/docs/troubleshooting 2026-09-20 https://uptimepage.dev/docs/development 2026-09-20 https://uptimepage.dev/docs/benchmarks 2026-05-14 https://uptimepage.dev/docs/loadtest 2026-07-25 https://uptimepage.dev/changelog 2026-09-21 https://uptimepage.dev/changelog/alert-mail-reliability-and-honest-probe-errors 2026-09-21 https://uptimepage.dev/changelog/one-uptime-figure-and-subscribers-hear-the-start 2026-09-20 https://uptimepage.dev/changelog/monitor-type-fixed-after-creation 2026-09-19 https://uptimepage.dev/changelog/september-fixes-heartbeat-telegram-regions 2026-09-17 https://uptimepage.dev/changelog/mcp-setup-from-your-ai-client 2026-09-17 https://uptimepage.dev/changelog/status-page-noindex-site-link-powered-by 2026-09-10 https://uptimepage.dev/changelog/mattermost-gotify-and-ack-from-the-phone 2026-09-08 https://uptimepage.dev/changelog/ssl-domain-expiry-redirect-chain-tools 2026-09-06 https://uptimepage.dev/changelog/organizations-from-the-console 2026-09-05 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