Zenduty Outage History
Zenduty is up right nowPingoru has recorded 8 incidents for Zenduty: 4 in the last 12 months and 2 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 | 1 | 1 of 720 (0%) |
| July 2026 | 1 | 123 of 744 (16%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 2 | 2 of 720 (0%) |
| October 2026 | 0 | 0 of 525 (0%) |
Incidents, newest first
Notice September 18, 2026 Degraded Performance – Delayed Incident Notification Delivery 45m
Started Sep 18, 2026, 06:30 PM UTC· resolved Sep 18, 2026, 07:15 PM UTC
- resolved Sep 18, 2026, 07:39 PM UTC
Incident Summary Between approximately 18:45 and 19:15 UTC, some users may have experienced delayed delivery of incident notifications across push, SMS, call and email channels. Impact Incident notifications were delayed during this window. No notifications were lost, all notifications were eventually delivered, though with a delay. Normal notification delivery was restored by 19:15 UTC.
Minor September 1, 2026 Delayed Incident Notifications 48m Zenduty Notification
Started Sep 01, 2026, 10:30 AM UTC· resolved Sep 01, 2026, 11:18 AM UTC
- resolved Sep 01, 2026, 12:52 PM UTC
Between approximately 10:30 and 11:18 UTC , you might have experienced delayed delivery of incident notifications (push, SMS, call, and email). No notifications were lost. All notifications were eventually delivered, but with delay. Our team identified the issue within minutes and took action to restore normal processing. Notification delivery returned to normal by 11:18 UTC We apologize for the delay this may have caused to your incident response workflow.
Minor July 17, 2026 Voice call notification delivery failures - Singapore 5d 2h Zenduty Notification
Started Jul 17, 2026, 11:48 AM UTC· resolved Jul 22, 2026, 02:19 PM UTC
- investigating Jul 17, 2026, 11:48 AM UTC
We've identified an issue affecting voice-call notifications to Singapore (+65) phone numbers. Affected customers may experience failed or missing call alerts. This is caused by a disruption at our upstream voice provider. All other notification channels (SMS, email, push, and chat) are operating normally. Incidents are still being delivered through these channels.
- investigating Jul 22, 2026, 02:18 PM UTC
This incident is resolved. Voice-call notifications to Singapore (+65) numbers are delivering normally again. The disruption originated with our upstream voice provider and has since been corrected. We've verified successful call delivery and are monitoring to ensure stability. We apologize for the disruption. If you're still seeing failures, please reach out to support.
- resolved Jul 22, 2026, 02:19 PM UTC
This incident has been resolved.
Minor June 2, 2026 We had a partial degradation in notification service 1h 9m Zenduty Notification
Started Jun 02, 2026, 10:56 AM UTC· resolved Jun 02, 2026, 12:05 PM UTC
- resolved Jun 02, 2026, 12:37 PM UTC
Between 10:56 and 12:05 UTC on Jun 2, 2026, we experienced partial degradation in notification delivery. The notification service has been fully restored and is operating normally. We are actively investigating the root cause.
- postmortem Jun 02, 2026, 01:10 PM UTC
A routine security patch deployed earlier today caused an unexpected disruption to notification delivery. Our team identified the issue, rolled back the change, and notification service ha been restored to normal. We're conducting a full review to prevent recurrence. We apologize for any inconvenience.
Minor October 20, 2025 Investigating Potential Issue - Delayed Notifications(SMS/Voice/Email) and impact to Email Integration 40m Alerts Ingestion
Started Oct 20, 2025, 09:31 AM UTC· resolved Oct 20, 2025, 10:11 AM UTC
- investigating Oct 20, 2025, 09:31 AM UTC
We are currently experiencing issues with our Email integration, Voice, SMS and Email alerts. Our team is actively investigating the issue and working to restore full access as quickly as possible.
- investigating Oct 20, 2025, 09:52 AM UTC
We are monitoring recovery of all the impacted functionalities. We appreciate your patience and will provide the next update in 30-minutes.
- monitoring Oct 20, 2025, 09:53 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 20, 2025, 10:11 AM UTC
This issue is now resolved for all users and are seeing signs of complete recovery across Zenduty. Users will see success in triggering Incidents via the Email integration, along with recovery to their Email, SMS and Voice notifications. We apologize for any disruptions to your day.
Notice March 20, 2025 [Resolved] Delay in sending Notifications 33m
Started Mar 20, 2025, 12:30 PM UTC· resolved Mar 20, 2025, 01:03 PM UTC
- resolved Mar 20, 2025, 01:56 PM UTC
[Resolved] Users may have experienced a delay in receiving notifications. This issue was identified at 12:43 PM GMT and was resolved by 1:03 PM GMT.
Major January 8, 2025 [Resolved] Issue with Alert Rule evaluation – Alerts Ingestion
Started Jan 08, 2025, 02:29 PM UTC· resolved Jan 08, 2025, 02:29 PM UTC
- resolved Jan 08, 2025, 02:29 PM UTC
We identified an issue at 2.15pm UTC after a release that impacted the evaluation of a subset of alert rules. Upon detection, our engineering team promptly investigated and fixed the issue. As of now, there is no ongoing impact, and all systems are functioning as expected. We sincerely apologize for any inconvenience caused and appreciate your understanding. If you experience any further issues, please reach out to our support team at [email protected]. Thank you for your patience. — The Zenduty Team