Embeddable Status Badge
Show a live badge — sometimes called a status image, an uptime badge, or simply an embed badge — on your README, blog, status page, or anywhere else you can drop an image. The badge updates every 60 seconds from our monitoring infrastructure and links back to the full status page.
How to embed
Replace google.com
with the domain you want to monitor. Any domain in our catalog works (we track 2,700+).
Markdown
For GitHub READMEs, GitLab, Reddit posts, and most static-site generators:
[](https://isitdownchecker.com/check/google.com) HTML
For blog posts, dashboards, custom status pages:
<a href="https://isitdownchecker.com/check/google.com">
<img src="https://isitdownchecker.com/api/badge/google.com.svg" alt="google.com status" />
</a> BBCode (forums)
[url=https://isitdownchecker.com/check/google.com][img]https://isitdownchecker.com/api/badge/google.com.svg[/img][/url] What the colors mean
- Green / "up" — site is responding and crowd reports are at baseline.
- Yellow / "issues" — site responds but user reports have spiked above baseline.
- Red / "down" — confirmed HTTP failure or major report spike.
Caching & rate limits
Badges are cached at the edge for 60 seconds, so the same domain can be loaded by
millions of viewers without hitting our origin. There are no per-IP rate limits on
the badge endpoint — it's designed to be embedded freely. The status logic powering
each badge is the same dual-signal system documented on our
methodology page;
for color thresholds and edge cases, see the
FAQ.
You can also check the live
current outages feed
or browse monthly outage reports
to see how reliable a service has been over time. To find the exact /check/{domain}
URL for a site you want to monitor, search from the homepage
or browse all categories.
Permitted use
You may embed the badge on any public or private page, with or without attribution.
Each badge is wrapped in a link back to the corresponding
/check/{domain} page on Is it down checker;
we ask that you keep the link intact so readers can investigate when the badge turns yellow or red.
Frequently asked questions
Is the badge free? Is the embeddable status badge free? ▼
Yes, the badge is free — completely free, with no rate limits and no attribution requirement. The badge image is served from a public endpoint cached at the edge for 60 seconds, so embedding it on a high-traffic page or README is no different from embedding any other public image. There's no signup, no API key, and no per-domain billing.
How fresh is the badge data? ▼
Each badge fetch reads the latest cached status from our edge, which is refreshed every 60 seconds from the same monitoring pipeline that powers the live status page. Color transitions (green to yellow to red) propagate within roughly 60-90 seconds of detection by our backend.
Can I use the badge on a private repo or internal dashboard? ▼
Yes. The badge is a public image that any client can fetch over HTTPS. It works in private GitHub/GitLab repos, internal Confluence and Notion pages, intranet dashboards, and any other context that can render an image from a public URL.
What domains are supported by the embed badge? ▼
Any domain in our monitoring catalog (2,700+ sites) has an embed badge available at /api/badge/{domain}.svg. If a domain isn't in the catalog yet, contact us at contact@isitdownchecker.com and we'll add it within a few days, after which the badge endpoint will start working automatically.
Will the badge slow down my page? ▼
No. The badge is a tiny SVG (typically under 2 KB), served with aggressive edge caching and HTTP/2 multiplexing. Browser image-loading happens after critical content paints, so the badge does not block your Core Web Vitals (LCP, FCP, CLS, INP) on any modern site.
Can I customize the badge color, size, or style? ▼
The current badge is a fixed-style SVG matching our brand. We're tracking customization requests (size, monochrome, dark-mode variants) for a future release - email feedback@isitdownchecker.com if you have specific design needs.
More questions? Email contact@isitdownchecker.com.