User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
logz.io · Productivity
Is Logz down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Tests logz.io from your browser and compares it with our checks, the official status, and user reports.
Your browser → logz.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
Press Run testNothing leaves your browser except a request to the site and to us.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 137 ms · 3 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 240 ms | 0 |
| 03:15 | 0 | 0.0 | 175 ms | 0 |
| 03:30 | 0 | 0.0 | 59 ms | 0 |
| 03:45 | 0 | 0.0 | 133 ms | 0 |
| 04:00 | 0 | 0.0 | 68 ms | 0 |
| 04:15 | 0 | 0.0 | 309 ms | 0 |
| 04:30 | 0 | 0.0 | 274 ms | 0 |
| 04:45 | 0 | 0.0 | 116 ms | 0 |
| 05:00 | 0 | 0.0 | 283 ms | 0 |
| 05:15 | 0 | 0.0 | 82 ms | 0 |
| 05:30 | 0 | 0.0 | 206 ms | 0 |
| 05:45 | 0 | 0.0 | 76 ms | 0 |
| 06:00 | 0 | 0.0 | 117 ms | 0 |
| 06:15 | 0 | 0.0 | 142 ms | 0 |
| 06:30 | 0 | 0.0 | 272 ms | 0 |
| 06:45 | 0 | 0.0 | 136 ms | 0 |
| 07:00 | 0 | 0.0 | 219 ms | 0 |
| 07:15 | 0 | 0.0 | 350 ms | 0 |
| 07:30 | 0 | 0.0 | 182 ms | 0 |
| 07:45 | 0 | 0.0 | 161 ms | 0 |
| 08:00 | 0 | 0.0 | 838 ms | 0 |
| 08:15 | 0 | 0.0 | 193 ms | 0 |
| 08:30 | 0 | 0.0 | 120 ms | 0 |
| 08:45 | 0 | 0.0 | 206 ms | 0 |
| 09:00 | 0 | 0.0 | 189 ms | 0 |
| 09:15 | 0 | 0.0 | 139 ms | 0 |
| 09:30 | 0 | 0.0 | 95 ms | 0 |
| 09:45 | 0 | 0.0 | 140 ms | 0 |
| 10:00 | 0 | 0.0 | 292 ms | 0 |
| 10:15 | 0 | 0.0 | 130 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Logz status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Logz yet. Outages of 10 minutes or more get their own page here.
Having trouble with Logz?
One report per service every 10 minutes from this network. No account.
Follow Logz
Get an email when Logz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Logz alerts to Slack, Discord or a webhook — free.
Questions
Is Logz down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Logz not working for me but the status is fine. What now?
If Logz is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Logz's side.
How does Damn is it down decide Logz's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Logz checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.