TRMNL Outage History

TRMNL is up right now

There were 4 TRMNL outages since March 26, 2026 totaling 13h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trmnl.statuspage.io

Major April 28, 2026

Redis cache timeouts

Detected by Pingoru
Apr 28, 2026, 06:47 PM UTC
Resolved
Apr 28, 2026, 07:34 PM UTC
Duration
47m
Affected: Display APIFirmware APIScreen Generation Workers
Timeline · 4 updates
  1. investigating Apr 28, 2026, 06:46 PM UTC

    Under investigation

  2. investigating Apr 28, 2026, 06:47 PM UTC

    We have started to investigate this issue.

  3. identified Apr 28, 2026, 06:52 PM UTC

    We've identified a commit that failed worker deployment, and a second that affected Redis. These have been reverted and we continue to find the root cause.

  4. resolved Apr 28, 2026, 07:34 PM UTC

    We've manually redeployed workers and systems continue to be stable.

Read the full incident report →

Minor April 13, 2026

DNS "Hostname not known" Errors

Detected by Pingoru
Apr 13, 2026, 09:17 PM UTC
Resolved
Apr 14, 2026, 12:49 AM UTC
Duration
3h 32m
Affected: Screen Generation Workers
Timeline · 3 updates
  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.

Read the full incident report →

Notice March 30, 2026

Some plugins are not rendering

Detected by Pingoru
Mar 30, 2026, 05:16 PM UTC
Resolved
Mar 30, 2026, 08:50 PM UTC
Duration
3h 33m
Affected: Screen Generation Workers
Timeline · 4 updates
  1. investigating Mar 30, 2026, 05:16 PM UTC

    Some users are reporting that some of their plugins have not updated since about 14:00 UTC. We are investigating.

  2. investigating Mar 30, 2026, 06:09 PM UTC

    On our background worker nodes, we have found that Firefox times out during plugin rendering. We are continuing to investigate the cause.

  3. monitoring Mar 30, 2026, 08:05 PM UTC

    We have deployed a fix and worker health has improved. We are continuing to monitor the situation.

  4. resolved Mar 30, 2026, 08:50 PM UTC

    We identified that a change made to the Google Calendar plugin resulted in very long render times for that particular plugin. This delay quickly exhausted our pool of Firefox workers and prevented other plugins from getting a chance to generate. The offending change has been rolled back.

Read the full incident report →

Major March 26, 2026

DB Replica lag affecting site responsiveness

Detected by Pingoru
Mar 26, 2026, 02:22 PM UTC
Resolved
Mar 26, 2026, 07:58 PM UTC
Duration
5h 36m
Affected: Display APIFirmware APIScreen Generation Workers
Timeline · 5 updates
  1. investigating Mar 26, 2026, 02:58 PM UTC

    We are currently investigating the issue as the main database has 32GB of replica lag.

  2. monitoring Mar 26, 2026, 03:33 PM UTC

    We've identified the issue and restored site functionality. We are still monitoring the system as we identify the underlying cause. Screen generation will still see lag due to the backlog and one worker being taken offline.

  3. monitoring Mar 26, 2026, 05:45 PM UTC

    Screen generation workers continue to work through the backlog. This can result in: - Existing plugins not showing up-to-date information (old screeens) - New devices showing "You're all caught up!" due to no screens yet generated

  4. monitoring Mar 26, 2026, 06:22 PM UTC

    All workers are caught up, but one worker is currently still offline. While this is technically degraded, the existing workers can handle the ongoing load.

  5. resolved Mar 26, 2026, 07:58 PM UTC

    All screen generation workers and APIs have been restored. Internal infrastructure analysis and adjustments will continue with no impact on customers or operations.

Read the full incident report →

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