Is Logz API down?
Current Logz API status is UP

We checked the official Logz API Status Page 1 min. 17 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Logz API Outages and Issues

Follow the recent outages and downtime for Logz API in the table below.

Start Time

Type

Length

Message

Details

February 22, 2024 16:37 UTC

WARN

less than a minute

AWS Incident - Ingestion/UI/Latency

See more
Start Time

February 22, 2024 16:37 UTC

Type WARN
Affected Components

AWS Frankfurt (eu-central-1) - Archive & Restore

AWS London (eu-west-2) - SIEM

AWS London (eu-west-2) - K8S 360

AWS London (eu-west-2) - API

AWS London (eu-west-2) - Archive & Restore

AWS London (eu-west-2) - Sign up & Login

AWS London (eu-west-2) - Logs Visualizations and Dashboards

AWS London (eu-west-2) - Tracing Visualizations and Dashboards

AWS London (eu-west-2) - Metrics Visualizations and Dashboards

AWS Frankfurt (eu-central-1) - Alerts & Security rules

AWS Frankfurt (eu-central-1) - API

AWS Frankfurt (eu-central-1) - K8S 360

AWS Frankfurt (eu-central-1) - SIEM - Web Application

AWS Frankfurt (eu-central-1) - Sign up & Login

AWS London (eu-west-2) - Log Ingestion

AWS London (eu-west-2) - Metrics Ingestion

AWS London (eu-west-2) - Alerts & Security rules

AWS Frankfurt (eu-central-1) - Logs Ingestion

AWS Frankfurt (eu-central-1) - Logs Visualizations and Dashboards

AWS Frankfurt (eu-central-1) - Metrics Ingestion

AWS Frankfurt (eu-central-1) - Metrics Visualizations and Dashboards

Message

AWS Incident - Ingestion/UI/Latency

Details

Monitoring - We are monitoring the current AWS outage and it's impact on Logz.io. Feb 22, 2024 - 18:33 IST

February 22, 2024 16:37 UTC

WARN

40 minutes

AWS Incident - Ingestion/UI/Latency

See more
Start Time

February 22, 2024 16:37 UTC

Type WARN
Affected Components

AWS Frankfurt (eu-central-1) - Archive & Restore

AWS London (eu-west-2) - SIEM

AWS London (eu-west-2) - K8S 360

AWS London (eu-west-2) - API

AWS London (eu-west-2) - Archive & Restore

AWS London (eu-west-2) - Sign up & Login

AWS London (eu-west-2) - Logs Visualizations and Dashboards

AWS London (eu-west-2) - Tracing Visualizations and Dashboards

AWS London (eu-west-2) - Metrics Visualizations and Dashboards

AWS Frankfurt (eu-central-1) - Alerts & Security rules

AWS Frankfurt (eu-central-1) - API

AWS Frankfurt (eu-central-1) - K8S 360

AWS Frankfurt (eu-central-1) - SIEM - Web Application

AWS Frankfurt (eu-central-1) - Sign up & Login

AWS London (eu-west-2) - Log Ingestion

AWS London (eu-west-2) - Metrics Ingestion

AWS London (eu-west-2) - Alerts & Security rules

AWS Frankfurt (eu-central-1) - Logs Ingestion

AWS Frankfurt (eu-central-1) - Logs Visualizations and Dashboards

AWS Frankfurt (eu-central-1) - Metrics Ingestion

AWS Frankfurt (eu-central-1) - Metrics Visualizations and Dashboards

Message

AWS Incident - Ingestion/UI/Latency

Details

Monitoring - We are monitoring the current AWS outage and it's impact on Logz.io. Feb 22, 2024 - 18:33 IST

February 22, 2024 16:22 UTC

DOWN

15 minutes

AWS Incident - Ingestion/UI/Latency

See more
Start Time

February 22, 2024 16:22 UTC

Type DOWN
Affected Components

AWS London (eu-west-2) - SIEM

AWS London (eu-west-2) - K8S 360

AWS Canada (ca-central-1) - API

AWS Canada (ca-central-1) - Logs Ingestion

AWS London (eu-west-2) - Archive & Restore

AWS London (eu-west-2) - Sign up & Login

AWS London (eu-west-2) - Metrics Visualizations and Dashboards

AWS London (eu-west-2) - Tracing Visualizations and Dashboards

AWS London (eu-west-2) - Metrics Ingestion

AWS London (eu-west-2) - Alerts & Security rules

AWS Canada (ca-central-1) - Logs Visualizations and Dashboards

Message

AWS Incident - Ingestion/UI/Latency

Details

Update - We are continuing to investigate this issue. Feb 22, 2024 - 18:18 IST

February 22, 2024 15:17 UTC

DOWN

less than a minute

AWS Incident - Ingestion / UI

See more
Start Time

February 22, 2024 15:17 UTC

Type DOWN
Affected Components

AWS Canada (ca-central-1) - API

AWS Canada (ca-central-1) - Logs Visualizations and Dashboards

AWS London (eu-west-2) - API

AWS Frankfurt (eu-central-1) - Logs Ingestion

AWS Frankfurt (eu-central-1) - Logs Visualizations and Dashboards

AWS Canada (ca-central-1) - Logs Ingestion

AWS London (eu-west-2) - Log Ingestion

AWS London (eu-west-2) - Logs Visualizations and Dashboards

Message

AWS Incident - Ingestion / UI

Details

Investigating - We are currently investigating this issue. Feb 22, 2024 - 17:16 IST

February 22, 2024 15:17 UTC

DOWN

about 1 hour

AWS Incident - Ingestion / UI

See more
Start Time

February 22, 2024 15:17 UTC

Type DOWN
Affected Components

AWS Canada (ca-central-1) - API

AWS Canada (ca-central-1) - Logs Visualizations and Dashboards

AWS London (eu-west-2) - API

AWS Frankfurt (eu-central-1) - Logs Ingestion

AWS Frankfurt (eu-central-1) - Logs Visualizations and Dashboards

AWS Canada (ca-central-1) - Logs Ingestion

AWS London (eu-west-2) - Log Ingestion

AWS London (eu-west-2) - Logs Visualizations and Dashboards

Message

AWS Incident - Ingestion / UI

Details

Investigating - We are currently investigating this issue. Feb 22, 2024 - 17:16 IST

2024-04-18 06:53:49 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-18 06:53:49 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-18 06:53:49 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-18 06:53:49 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-18 06:53:49 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Logz API History

StatusGator has over 4 years of Logz API status history.

No outages or status changes in the last 24 hours

Logz API status, last 24 hours:

7:00 AM
1:00 PM
7:00 PM
1:00 AM
7:00 AM
7:00 AM
7:00 PM
7:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Logz API Outage and Status History

We've been monitoring Logz API outages since October 28, 2019.
Here's the history of service outages we've observed from the Logz API Status Page:

Instant enriched data from
3,580 status pages

About Our Logz API Status Page Integration

Logz API is a Cloud Infrastructure, Project Management, and Identity Management solution that StatusGator has been monitoring since October 2019. Over the past over 4 years, we have collected data on on more than 1,154 outages that affected Logz API users. When Logz API publishes downtime on their status page, they do so across 79 components and 8 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

Many StatusGator users monitor Logz API to get notified when it's down, is under maintenance, or has an outage. We've sent more than 4,100 notifications to our users about Logz API incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Logz API is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Logz API is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Logz API posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Logz API enters a pre-planned maintenance window, keeping you up to date.

Since Logz API publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.

When Logz API posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Logz API has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Logz API has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Logz API Down?

Are you experiencing issues with Logz API? Sign up to receive notifications when Logz API publishes outages.

Logz API Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Logz API?

Sign up for StatusGator and see all historical information about Logz API outages and performance issues. Get free, instant notifications when Logz API goes down.