Is TRMNL down?

Last checked 7m ago
Current status
TRMNL is up

No incidents right now.

Official status page: https://trmnl.statuspage.io · Polled every 5 minutes · 6 components tracked

TRMNL is operational right now. Last checked 7m ago; the most recent incident resolved 26d ago.

Real-time TRMNL status, recent outages, and incident history — pulled directly from TRMNL's official status page at https://trmnl.statuspage.io every 5 minutes. Pingoru tracks 6 TRMNL services and has captured 6 incidents in the last 90 days (97.78% uptime). Get email, Slack, Discord, or webhook alerts the moment TRMNL reports a new incident — free for 5 monitors, no credit card.

Users who monitor TRMNL also follow these Productivity services: Dropbox Box Smartsheet Lucid RealVNC Mural Tungsten Automation Americas Guru NetDocuments US Doodle View all 6,000+ providers
TRMNL uptime 97.78% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 8m
    Started May 19, 2026, 12:07 AM UTC · Resolved May 19, 2026, 01:15 AM UTC
    Display API
    Timeline · 3 updates
    • investigating · May 19, 2026, 12:07 AM UTC

      The Dashboard and device API are currently not responding. The CPU usage on these two servers is higher than normal. We are investigating the issue.

    • monitoring · May 19, 2026, 12:21 AM UTC

      The Dashboard and API have been restored. We have disabled some features to lower server CPU usage. We are looking further into the initial cause of the outage.

    • resolved · May 19, 2026, 01:15 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 33m
    Started May 05, 2026, 01:21 PM UTC · Resolved May 05, 2026, 01:55 PM UTC
    Timeline · 3 updates
    • investigating · May 05, 2026, 01:21 PM UTC

      The TRMNL dashboard application is intermittently down. The API is still up, so device refresh isn't affected. We're looking into the issue.

    • monitoring · May 05, 2026, 01:41 PM UTC

      We discovered that an expensive analytics query was running, consuming a large amount of the web server CPU and memory. The query was killed and the server became responsive again. The situation: monitored.

    • resolved · May 05, 2026, 01:55 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 47m
    Started Apr 28, 2026, 06:47 PM UTC · Resolved Apr 28, 2026, 07:34 PM UTC
    Display APIFirmware APIScreen Generation Workers
    Timeline · 4 updates
    • investigating · Apr 28, 2026, 06:46 PM UTC

      Under investigation

    • investigating · Apr 28, 2026, 06:47 PM UTC

      We have started to investigate this issue.

    • 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.

    • resolved · Apr 28, 2026, 07:34 PM UTC

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

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

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

    • investigating · Apr 14, 2026, 12:18 AM UTC

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

    • resolved · Apr 14, 2026, 12:49 AM UTC

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

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

  5. Resolved 3h 33m
    Started Mar 30, 2026, 05:16 PM UTC · Resolved Mar 30, 2026, 08:50 PM UTC
    Screen Generation Workers
    Timeline · 4 updates
    • 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.

    • 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.

    • 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.

    • 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.

    Latest: 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 worke…

See the full TRMNL outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse TRMNL outage history →

Or sign up free to get alerts when TRMNL breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →