Skip to main content
Logz.io logo

Is Logz.io Down?

No — Logz.io is up

Reachable from all 8 checked regions

Average response time: 140ms

Last checked · checks run every 6 hours

Official status page: https://status.logz.io

Logz.io uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
170ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

34-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 47 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
193ms
DNS 168ms TCP 2ms TLS 7ms TTFB 184ms
arn
59ms
DNS 36ms TCP 0ms TLS 7ms TTFB 51ms
cdg
151ms
DNS 123ms TCP 1ms TLS 10ms TTFB 143ms
ord
61ms
DNS 41ms TCP 1ms TLS 6ms TTFB 55ms
sin
246ms
DNS 227ms TCP 1ms TLS 4ms TTFB 238ms
sjc
136ms
DNS 115ms TCP 1ms TLS 5ms TTFB 129ms
syd
177ms
DNS 161ms TCP 0ms TLS 4ms TTFB 170ms
yyz
97ms
DNS 66ms TCP 1ms TLS 13ms TTFB 89ms

What Logz.io does

Logz.io is a hosted observability platform built on open source tooling, taking in logs, metrics and traces from an organisation's systems and providing search, dashboards, alerting and security analytics over them. Accounts are hosted in a specific cloud region. Because it is the system teams watch to learn that something else is wrong, its own failures are easy to mistake for calm.

What an outage looks like

Dashboards render empty or stop advancing, so recent activity appears to have stopped when it is the pipeline rather than the systems that went quiet. Alerts stop firing while data continues to arrive, which produces silence that reads as healthy. Log or metric ingestion can fail on its own, leaving a gap in history. Sign-in and the API may fail independently of everything else.

What to do about it

Read status.logz.io, which groups components by cloud region, including AWS N. Virginia, Frankfurt, Canada, Sydney and London. Find your account's region first, because the others tell you nothing. Within a region, Logs Ingestion is reported separately from Logs Visualizations and Dashboards and from Alerts and Security rules, so match the symptom to the row before treating quiet dashboards as good news.

Is it down for everyone, or just you?

If this page says Logz.io is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Datadog
Datadog
Splunk
Splunk
Sumo Logic
Sumo Logic
New Relic
New Relic

Logz.io outage FAQ

My dashboards are empty. Did my systems stop sending data?
Check the pipeline before you check your systems. Logz.io reports Logs Ingestion as a component separate from Logs Visualizations and Dashboards, so an empty dashboard is equally consistent with data arriving and not being displayed. Look at the two rows for your region on status.logz.io. Getting this the wrong way round sends teams hunting through healthy applications for a fault that is in the observability layer.
No alerts have fired. Does that mean nothing is wrong?
Not reliably, and this is the risk worth planning for. Alerts and Security rules is its own component in each region, so alerting can be degraded while ingestion and dashboards work normally. Silence from a monitoring system is ambiguous during its own incident. Where an alert protects something important, check the underlying system directly for the duration rather than trusting the absence of a page.
My colleague's account works and mine does not. Why?
Almost certainly region. Logz.io publishes separate component groups for AWS N. Virginia, Frankfurt, Canada, Sydney and London, and an account lives in one of them. An incident scoped to a single region leaves everyone else unaffected, so a working colleague is not evidence unless you share a region. Confirm which region your account is in before comparing notes or opening a support ticket.
Will logs sent during an outage be lost?
It depends on what is between your systems and Logz.io. A shipper or agent that buffers to disk commonly retries and backfills once ingestion recovers, while a direct send with no buffer has nowhere to hold the data. Logz.io does not publish a guarantee covering every shipping path, so treat the incident window as a possible gap and check whether your own agents buffer before assuming a complete record.
Should I fail over to another region during a Logz.io incident?
Moving an account between regions is not a same-day action and is the wrong response to an incident. The components in each region are separate deployments rather than a failover pair, so an unaffected region does not hold your data. The practical step during an incident is to keep your own local logs and agent buffers available for the period so the gap can be reconstructed afterwards.

How we measure this

  • We request Logz.io's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Logz.io publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Logz.io goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required