TRMNL incident

Database overloaded

Resolved after 14 hours 57 minutes, affecting Display API, on November 23, 2025.

resolved Nov 23, 2025, 04:05 PM UTC

A long-running database process (WalSender - Write Ahead Log Sender) was the root cause of extra memory usage and has since finished. We also up-sized the database permanently and removed temporary webhook rate limit reductions.

Started
Nov 23, 2025, 01:07 AM UTC
Resolved
Nov 23, 2025, 04:05 PM UTC
Duration
14h 57m
Detected by Pingoru
Nov 23, 2025, 01:07 AM UTC

Affected components

Display API

Update timeline

  1. investigating Nov 23, 2025, 01:07 AM UTC

    We’re investigating a database-related issue that prevents our API from responding to some device requests for new content. We have temporarily reduced webhook rate limits to 5 per hour, down from 12 and 30 per hour (TRMNL+ subscribers).

  2. resolved Nov 23, 2025, 04:05 PM UTC

    A long-running database process (WalSender - Write Ahead Log Sender) was the root cause of extra memory usage and has since finished. We also up-sized the database permanently and removed temporary webhook rate limit reductions.

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 →