Ntfy incident

Email sending not working

Minor Resolved View vendor source →

Ntfy experienced a minor incident on March 29, 2026 affecting ntfy.sh API, lasting 1d 14h. The incident has been resolved; the full update timeline is below.

Started
Mar 29, 2026, 10:35 PM UTC
Resolved
Mar 31, 2026, 12:51 PM UTC
Duration
1d 14h
Detected by Pingoru
Mar 29, 2026, 10:35 PM UTC

Affected components

ntfy.sh API

Update timeline

  1. investigating Mar 29, 2026, 10:35 PM UTC

    The email sending feature is currently not working. The ntfy AWS SES account was paused. I am investigating, but I'm expecting this disruption to take multiple days. Apologies.

  2. identified Mar 31, 2026, 12:12 AM UTC

    ntfy server v2.21.0: Email verification has been deployed and released to ntfy.sh. AWS SES support has been notified, and I expect the AWS SES account to be re-instated soon. I added the email addresses of paid users to the database. Once the AWS account has been re-instated, others can add their own email addresses. Even free accounts can still send 5 emails per day, provided that the address was verified before. The incident is still ongoing until the AWS account is unpaused. https://github.com/binwiederhier/ntfy/releases/tag/v2.21.0

  3. resolved Mar 31, 2026, 12:51 PM UTC

    The email sending issue has been resolved. Email addresses now have to be verified before you can use them via the X-Email header. You can do so in the web app under "Account". I apologize for any inconveniences this may have caused.