SweetHawk Outage History
SweetHawk is up right nowPingoru has recorded 21 incidents for SweetHawk: 20 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 | 5 | 1 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 0 of 744 (0%) |
| August 2026 | 6 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 82 (0%) |
Incidents, newest first
Minor August 10, 2026 App server (new platform) recovered –
Started Aug 10, 2026, 03:03 PM UTC· resolved Aug 10, 2026, 03:03 PM UTC
No vendor updates were posted for this incident.
Minor August 9, 2026 App server (new platform) recovered –
Started Aug 09, 2026, 04:03 AM UTC· resolved Aug 09, 2026, 04:03 AM UTC
No vendor updates were posted for this incident.
Minor August 2, 2026 App server (new platform) recovered –
Started Aug 02, 2026, 11:03 PM UTC· resolved Aug 02, 2026, 11:03 PM UTC
No vendor updates were posted for this incident.
Minor August 2, 2026 App server (legacy) recovered –
Started Aug 02, 2026, 12:30 AM UTC· resolved Aug 02, 2026, 12:30 AM UTC
No vendor updates were posted for this incident.
Minor August 1, 2026 App server (legacy) recovered –
Started Aug 01, 2026, 11:12 PM UTC· resolved Aug 01, 2026, 11:12 PM UTC
No vendor updates were posted for this incident.
Minor August 1, 2026 App server (legacy) recovered –
Started Aug 01, 2026, 03:18 AM UTC· resolved Aug 01, 2026, 03:18 AM UTC
No vendor updates were posted for this incident.
Minor July 31, 2026 App server (legacy) recovered –
Started Jul 31, 2026, 01:24 PM UTC· resolved Jul 31, 2026, 01:24 PM UTC
No vendor updates were posted for this incident.
Minor May 28, 2026 App server (legacy) recovered 23m
Started May 28, 2026, 11:24 AM UTC· resolved May 28, 2026, 11:48 AM UTC
No vendor updates were posted for this incident.
Minor May 28, 2026 App server unresponsive at times – App server (legacy)
Started May 28, 2026, 11:03 AM UTC· resolved May 28, 2026, 11:03 AM UTC
- resolved May 28, 2026, 11:03 AM UTC
There were jobs taking excessive resources. We have fixed the performance of these jobs and service has been returned to normal.
Minor May 28, 2026 App server (legacy) recovered –
Started May 28, 2026, 10:51 AM UTC· resolved May 28, 2026, 10:51 AM UTC
No vendor updates were posted for this incident.
Minor May 8, 2026 App server (new platform) recovered –
Started May 08, 2026, 02:09 AM UTC· resolved May 08, 2026, 02:09 AM UTC
No vendor updates were posted for this incident.
Major May 8, 2026 Infrastructure issues 11m App server (new platform)
Started May 08, 2026, 02:03 AM UTC· resolved May 08, 2026, 02:14 AM UTC
- investigating May 08, 2026, 02:03 AM UTC
Apps are currently not working due to our Redis server being unavailable. We are working on the issue. Apologies for the service interruption.
- resolved May 08, 2026, 02:14 AM UTC
We have now rebuilt our cache server cluster and are bringing things back online. We will continue to monitor but if you notice anything out of the ordinary please email [email protected].
Minor February 23, 2026 App server (legacy) recovered –
Started Feb 23, 2026, 04:12 AM UTC· resolved Feb 23, 2026, 04:12 AM UTC
No vendor updates were posted for this incident.
Minor February 16, 2026 App server (legacy) recovered –
Started Feb 16, 2026, 02:54 AM UTC· resolved Feb 16, 2026, 02:54 AM UTC
No vendor updates were posted for this incident.
Minor February 16, 2026 Recurring Tickets not being created – App server (legacy)
Started Feb 16, 2026, 01:01 AM UTC· resolved Feb 16, 2026, 01:01 AM UTC
- resolved Feb 16, 2026, 01:01 AM UTC
Recurring Tickets are working again after an interruption. Some tickets may have been created later than their schedule by up to 24 hours later. We have also addressed an issue with the Timers app, having a similar issue. Some timers that were started over 24 hours ago and were due to complete in the last 24 hours may have been missed. If you have any concerns, please contact us at [email protected], kindly let us know example ticket ID(s) we can look into and that we have access to your data for troubleshooting purposes and we'll get back to you asap.
Minor February 8, 2026 App server (new platform) recovered –
Started Feb 08, 2026, 10:06 PM UTC· resolved Feb 08, 2026, 10:06 PM UTC
No vendor updates were posted for this incident.
Minor January 24, 2026 App server (new platform) recovered –
Started Jan 24, 2026, 03:57 AM UTC· resolved Jan 24, 2026, 03:57 AM UTC
No vendor updates were posted for this incident.
Major January 13, 2026 Notify app notification unavailable 2h 10m App server (legacy)
Started Jan 13, 2026, 01:59 AM UTC· resolved Jan 13, 2026, 04:09 AM UTC
- investigating Jan 13, 2026, 01:59 AM UTC
Due to a database issue, the Notify app is currently degraded, we are unable to surface whether there are unread notifications when the app loads. Apologies for the trouble, we hope to have this resolved soon.
- resolved Jan 13, 2026, 04:09 AM UTC
The issue has been resolved, all apps working again as normal.
Major January 12, 2026 Database issue 18m App server (legacy)
Started Jan 12, 2026, 04:49 PM UTC· resolved Jan 12, 2026, 05:07 PM UTC
- investigating Jan 12, 2026, 04:49 PM UTC
We are having issues with our database on our legacy app server and are looking into the cause, apologies for the outage.
- resolved Jan 12, 2026, 05:07 PM UTC
The apps are working again and we have rolled back a recent release. We are looking into the cause.
Major December 21, 2025 Unexpected downtime during maintenance release – App server (new platform)
Started Dec 21, 2025, 11:07 PM UTC· resolved Dec 21, 2025, 11:07 PM UTC
- resolved Dec 21, 2025, 11:07 PM UTC
We are looking into an unexpected outage caused by a database schema upgrade. Apologies for the service interruption.
Minor July 2, 2025 Jobs not processing on time – App server (legacy)
Started Jul 02, 2025, 06:32 PM UTC· resolved Jul 02, 2025, 06:32 PM UTC
- resolved Jul 02, 2025, 06:32 PM UTC
An issue with jobs (eg approvals, task lists, timers) not processing in a timely manner has been resolved. Due to a temporary issue with a response from the Zendesk job status this also caused an issue on our side, some jobs were running too long and causing a backlog in the processing queue. The issue was temporary and we have made a fix that prevented some other jobs from waiting too long on others to expedite clearing the queue.