TRMNL incident

DNS "Hostname not known" Errors

Resolved after 3 hours 32 minutes, affecting Screen Generation Workers, on April 13, 2026.

investigating Apr 14, 2026, 12:18 AM UTC

We continue to investigate the issue. It is not related to any recent code changes.

Started
Apr 13, 2026, 09:17 PM UTC
Resolved
Apr 14, 2026, 12:49 AM UTC
Duration
3h 32m
Detected by Pingoru
Apr 13, 2026, 09:17 PM UTC

Affected components

Screen Generation Workers

Update timeline

  1. investigating Apr 13, 2026, 09:17 PM UTC

    Over the weekend we noticed a growing surge of "Hostname not known" errors where usually there are nominal, causing plugins to not be able to reach endpoints to refresh data. This is a transient issue and is under investigation.

  2. investigating Apr 14, 2026, 12:18 AM UTC

    We continue to investigate the issue. It is not related to any recent code changes.

  3. resolved Apr 14, 2026, 12:49 AM UTC

    We've resolved an issue with DNS resolution errors on all worker machines.

Your product runs on more than TRMNL

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →