Resolved after 1 day 14 hours, affecting ntfy.sh API, on March 29, 2026.
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.
Affected components
Update timeline
- 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.
- 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
- 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.
Your product runs on more than Ntfy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services