TRMNL incident

DNS "Hostname not known" Errors

Minor Resolved View vendor source →
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.

Looking to track TRMNL downtime and outages?

Pingoru polls TRMNL's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when TRMNL reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track TRMNL alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring TRMNL for free

5 free monitors · No credit card required