Logz.io: Certificate renewal for Filebeat-based Integrations in us-east-1 and eu-central

What to do

Check whether you use Logz.io in eu, us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-07-28 09:22 UTC and 2025-07-25 13:00 UTC may need a replay.
Subscribe to Logz.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=logzio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedJul 25, 2025, 1:00 PM UTC
We’ve completed a retroactive maintenance operation to address a renewal related to an outdated certificate that may affect customers using Filebeat-based integrations in the US-east-1 and EU-central regions. Only customers using Filebeat integrations that rely on outdated versions are potentially impacted. If you’re experiencing issues with Filebeat log shipping, please update your Filebeat configuration to trust the latest certificate chain. You can download the updated certificate and follow our integration guide to apply the necessary changes.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Logz.io still down?

No, this incident was resolved 2025-07-25 13:00 UTC. For Logz.io's live state, see https://down.guide/logzio.

How long did it last?

0m, from 2025-07-28 09:22 UTC to 2025-07-25 13:00 UTC, by the times Logz.io posted.

What was affected?

Logz.io named in eu, us, us-east-1.

What caused it?

Logz.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

Logz.io's official status page, https://status.logz.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.