Ntfy Outage History
Ntfy is up right nowPingoru has recorded 2 incidents for Ntfy: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 568 (0%) |
Incidents, newest first
Minor March 29, 2026 Email sending not working 1d 14h ntfy.sh API
Started Mar 29, 2026, 10:35 PM UTC· resolved Mar 31, 2026, 12:51 PM UTC
- 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.
Minor February 24, 2026 User signup issues 1h 31m ntfy.sh API
Started Feb 24, 2026, 05:47 PM UTC· resolved Feb 24, 2026, 07:18 PM UTC
- investigating Feb 24, 2026, 05:47 PM UTC
We are currently investigating an issue with user signups between Feb 23, 21:41 UTC and Feb 24, 15:27 UTC.
- resolved Feb 24, 2026, 07:18 PM UTC
The issue has been fixed as best as is possible. The paid users have been notified and credited. There are still 90 free user signups in that 17+ hour period that "got lost", and since I do not collect email addresses, these users will just have to recreate their accounts. My sincere apologies. I've identified the root cause (human error, by me), and I'll put guardrails in place to make sure it doesn't happen again.