Skip to content

Outage tracker / Logz.io

Is Logz.io down?

I'm having a problem

Vendor reports no incidentWhat Logz.io reports

Logz.io reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:00 UTC.

Logz.io's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Logz.io pass from all 4 regions we check.

As of Nov 5, 2026, 3:08 PM UTC, RealUptime's checks of Logz.io passed in all 4 regions that returned a reading.

Front-door checks

our check readinglive · checked Nov 5, 2026, 3:08 PM UTC
US-East629 msChecks passing
US-West904 msChecks passing
Europe417 msChecks passing
Asia-Pacific1065 msChecks passing
their status pagetheir claim, not our reading

Logz.io reports: All systems operational (“All Systems Operational”)

from Logz.io's own status page, checked Nov 5, 2026, 2:52 PM UTC
Logz.io's own status page shows no incident, and our checks of Logz.io pass right now.

Logz.io's own component breakdown, as they publish it

  • Alerts & Security rulesOperational
  • Alerts & Security rulesOperational
  • Alerts & Security rulesOperational
  • Alerts & Security rulesOperational
  • Alerts & Security rulesOperational
  • Alerts & Security rulesOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • Archive & RestoreOperational
  • Archive & RestoreOperational
  • Archive & RestoreOperational
  • Archive & RestoreOperational
  • Archive & RestoreOperational
  • Archive & RestoreOperational
  • K8S 360Operational
  • K8S 360Operational
  • K8S 360Operational
  • K8S 360Operational
  • K8S 360Operational
  • K8S 360Operational
  • SIEMOperational
  • SIEMOperational
  • SIEMOperational
  • SIEMOperational
  • SIEMOperational
  • SIEM - Web ApplicationOperational
  • Sign up & LoginOperational
  • Sign up & LoginOperational
  • Sign up & LoginOperational
  • Sign up & LoginOperational
  • Sign up & LoginOperational
  • Sign up & LoginOperational
  • Alerts & Security rulesOperational
  • Log IngestionOperational
  • Logs IngestionOperational
  • Logs IngestionOperational
  • Logs IngestionOperational
  • Logs IngestionOperational
  • APIOperational
  • Logs Visualizations and DashboardsOperational
  • Logs Visualizations and DashboardsOperational
  • Logs Visualizations and DashboardsOperational
  • Logs Visualizations and DashboardsOperational
  • Logs Visualizations and DashboardsOperational
  • Logs Visualizations and DashboardsOperational
  • Archive & RestoreOperational
  • Metrics IngestionOperational
  • Metrics IngestionOperational
  • Metrics IngestionOperational
  • Metrics IngestionOperational
  • Metrics IngestionOperational
  • Metrics IngestionOperational
  • K8S 360Operational
  • Metrics Visualizations and DashboardsOperational
  • Metrics Visualizations and DashboardsOperational
  • Metrics Visualizations and DashboardsOperational
  • Metrics Visualizations and DashboardsOperational
  • Metrics Visualizations and DashboardsOperational
  • Metrics Visualizations and DashboardsOperational
  • SIEMOperational
  • Tracing Visualizations and DashboardsOperational
  • Tracing Visualizations and DashboardsOperational
  • Tracing Visualizations and DashboardsOperational
  • Tracing Visualizations and DashboardsOperational
  • Tracing Visualizations and DashboardsOperational
  • Tracing Visualizations and DashboardsOperational
  • Orion IQOperational
  • Orion IQOperational
  • Orion IQOperational
  • Orion IQOperational
  • Orion IQOperational
  • Sign up & LoginOperational
  • Logs IngestionOperational
  • Logs IngestionOperational
  • Logs Visualizations and DashboardsOperational
  • Orion IQOperational
  • Metrics IngestionOperational
  • Metrics Visualizations and DashboardsOperational
  • Tracing Visualizations and DashboardsOperational
  • Platform ExperienceOperational

These are Logz.io's components, named and scored by Logz.io. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Logz.io's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Logz.io response time, by region

US-East
1.0sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 979ms2026-11-03 UTC: p95 966ms2026-11-04 UTC: p95 942ms2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
825msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 986ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 825ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Logz.io

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Logz.io. It cannot diagnose Logz.io's own systems.

Email me when Logz.io reports an incident on its status page, and again when it reports it resolved.

Get an email when Logz.io reports an incident

Email me when Logz.io reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Logz.io's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 629msstatus code: 200checked: Nov 5, 2026, 3:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Logz.io normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 904msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Logz.io normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionLogz.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionLogz.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionLogz.io is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 417msstatus code: 200checked: Nov 5, 2026, 3:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Logz.io normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionLogz.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1065msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Logz.io normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionLogz.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionLogz.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Logz.io, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Logz.io yet, which is not evidence that nothing is wrong.

Recent probe events

Data Ingestions Delays For Some Customers - Degraded Performance - us-east-1, 1h 1mdeclared on their status page2026-11-04
EU-Central-1: Some Customers Experiencing Lag, 1h 2mdeclared on their status page2026-09-09
Canada - Data Ingestions Delays For Some Customers, 57mdeclared on their status page2026-08-21
Data Ingestions Delays For Some Customers - Degraded Performance - us-east-1, 1mdeclared on their status page2026-08-05
US-East - Data Ingestions Delays For Some Customers, 22mdeclared on their status page2026-07-09
US-East - Data Ingestions Delays For Some Customers, 1h 46mdeclared on their status page2026-07-08
Logs Ingestions Delays For Some Accounts - Monitoring, 3h 19mdeclared on their status page2026-06-08
US-EAST-1: Some Customers Experiencing Delayed Metrics Ingestion, 4h 19mdeclared on their status page2026-06-08

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Logz.io since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Logz.io covering any window you pick, with our check readings and Logz.io's own claim at the time, side by side.

Full check history for Logz.io: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Logz.io uptime by RealUptime's checksLive, from this page's own readings.
[![Logz.io uptime by RealUptime's checks](https://realuptime.io/outages/logz-io/badge.svg?days=30)](https://realuptime.io/outages/logz-io)
<a href="https://realuptime.io/outages/logz-io"><img src="https://realuptime.io/outages/logz-io/badge.svg?days=30" alt="Logz.io uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Logz.io down?", https://realuptime.io/outages/logz-io. The readings change with every check, so give the date you read them.

What we check

primary
https://logz.io/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: logz.io

RealUptime is not affiliated with Logz.io; the name identifies what we checked, and nothing here speaks for Logz.io's own team. We send a single web request to Logz.io from 4 regions on our own schedule and time the response. We do not see inside Logz.io's systems, do not use an account or real transaction, and are not the same signal Logz.io's own team has access to. Treat this as one external data point, not a verdict. What we check for Logz.io is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Logz.io operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1256 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.