Uptime monitoring for SaaS founders. Your users shouldn’t be the alert.

Logdash checks your site or API around the clock and messages you on Telegram as soon as a check fails. Start with a URL, no account needed.

No signup · No credit card · See the live demo

api.acme.com Every 15 s Live
Response 139 ms
15 min ago Now

Every app goes down sometimes. Finding out last is the bad part.

Logdash calls your URL on a schedule and reads the answer. When a check fails, you get a downtime alert on Telegram or a webhook, and customers see it on your status page.

  • HTTP uptime checks

    Logdash sends a GET request to your URL every 5 minutes on the free plan, every minute on Builder and every 15 seconds on Pro.

  • Clear downtime rules

    Up is a 2xx or 3xx answer within 10 seconds. Down is a 4xx, a 5xx, a timeout or a refused connection, and the alert says which.

  • Telegram downtime alerts

    Add @logdash_uptime_bot to a chat or group. It posts when a monitor goes down, with the status code and error, and when it recovers.

  • Webhook alerts

    Send every up and down change to your own endpoint, with the method and headers you pick. Wire alerts into any tool that takes HTTP.

  • Public status pages

    Live status and 90 days of uptime history on every plan, so customers check it before they email you. Use your own domain on Pro, or build the page yourself on the public API.

  • Response time history

    Every check records how long your server took to answer, so you see an endpoint getting slower well before it starts timing out.

Three steps to your first alert.

Nothing to install on your server and no config file. Paste a URL and the first checks come in while you watch.

  1. Paste your URL

    Enter your site or API address at the top of this page. Checks start right away and each result shows up live, no account needed.

  2. Keep the dashboard

    Open the dashboard and sign in with GitHub or Google within 24 hours. Your monitor keeps running on your plan’s check interval.

  3. Connect Telegram or a webhook

    Add @logdash_uptime_bot to a chat and send it the passphrase, or paste a webhook URL. The next failed check sends the alert.

Your status page, your brand. Even if your brand is bananas.

Every status page has a public API, so yours can look like anything. Swap the lens and the data underneath stays put. Start from our React or Svelte component, or from a blank file.

Acme

Partial outage

Checked every minute

  • Email queue Degraded
    24 h uptime
    99.76%
    7 d uptime
    99.94%
    30 d uptime
    97.75%
    90 d uptime
    99.25%
    30 days ago 90 days ago Today
  • API Operational
    24 h uptime
    100%
    7 d uptime
    100%
    30 d uptime
    99.38%
    90 d uptime
    99.79%
    30 days ago 90 days ago Today
  • Dashboard Operational
    24 h uptime
    100%
    7 d uptime
    100%
    30 d uptime
    100%
    90 d uptime
    100%
    30 days ago 90 days ago Today

Bananas lens. Uptime, measured in potassium.

Add it with one command.

The command copies the component into your project, so the code is yours to change. It runs on @logdash/status, a typed client with React and Svelte hooks. Or deploy the Next.js starter as a site of its own.

Read the status page docs
React 
npx shadcn add https://logdash.io/r/react/status-page.json
Svelte 
npx shadcn-svelte add https://logdash.io/r/svelte/status-page.json

Uptime monitoring FAQ

Have a different question? Reach out on Discord

How often does Logdash check my site?
Every 5 minutes on the free plan, every minute on Builder and every 15 seconds on Pro. Each check is a GET request to your URL, and the result shows up in your dashboard right away.
What counts as downtime?
A check passes when your URL answers with a 2xx or 3xx status within 10 seconds, after following redirects. A 4xx or 5xx status, a timeout or a connection error marks the monitor as down.
Can I get downtime alerts on Telegram?
Yes, on every plan, including the free one. Add @logdash_uptime_bot to a private chat or group and send it the passphrase Logdash shows you. It posts when a monitor goes down, with the status code and error, and again when it comes back up.
Which alert channels can I use?
Telegram and webhooks, both on every plan. A webhook calls any URL you choose with your own method and headers, so you can handle the alert in your own code. Email, Slack and Discord are not built in yet.
Is there a free uptime monitoring plan?
Yes. The Hobby plan is free with no credit card: up to 5 monitors checked every 5 minutes, Telegram and webhook alerts, and one public status page. Builder ($9/month) checks every minute and Pro ($15/month) every 15 seconds.
Can my status page use my own domain?
Yes, on the Pro plan. Add a CNAME record from a subdomain such as status.yourapp.com to statuspage.logdash.io and the status page is served there. Other plans publish it on a logdash.io link. A page you build on the status page API can live on any domain, on any plan.
How much uptime history does the status page show?
90 days on every plan. Each monitor shows its uptime over the last 24 hours, 7, 30 and 90 days, and one bar per day with that day’s uptime, number of checks and average response time. Days are in UTC.
Can I build my own status page?
Yes. Every public status page is also a JSON API, free and with no API key. Use @logdash/status for typed React and Svelte hooks, add our status page component with one command, or deploy the Next.js starter. The status page docs cover all three.
Do I need an account to start monitoring?
No. Paste a URL on this page and the first checks start right away. Claim the dashboard with GitHub or Google within 24 hours to keep it.
Can I monitor a private service?
Yes, with a push (heartbeat) monitor on Pro. Your service sends a POST to its own Logdash URL every few seconds, and if no call arrives within a 15-second window, the monitor goes down and you get the alert.

Know before they do.

Paste your URL and we start watching it right now.

No signup · No credit card · Claim later with GitHub or Google

Or watch the live demo
Your first 30 days
  1. Day 1
    The alert beats the tweet Checks start 30 seconds after you paste a URL. When it goes down, you hear it first.
  2. Day 7
    The refresh reflex is gone Logs and metrics sit next to your uptime, so you stop checking by hand.
  3. Day 30
    Users hear it from you first A status page on your domain answers before they ask. You ship, Logdash watches.