30 days uptime
100.000%
30 of 30 days clean · 0m total downtime
All windows
No incidents recorded for this service.
Official status page: https://luarocks.org/ (opens in new tab)
Live status pill for Luarocks Registry. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=luarocks-registry"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/luarocks-registry" style="border:0;width:260px;height:44px" loading="lazy" title="Luarocks Registry status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/luarocks-registry)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/luarocks-registry/badge.svgLuarocks Registry is currently Operational. CheckUpstream tracks Luarocks Registry in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
Looking for the live "is Luarocks Registry down" view? See the Luarocks Registry Status page.
Luarocks Registry has not had a resolved incident in the past 12 months on the surfaces CheckUpstream monitors.
Luarocks Registry's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
Sign up to CheckUpstream and add Luarocks Registry to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection — covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Luarocks Registry's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.