Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Sweethawk outage history

    17 recorded Sweethawk incidents since July 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    App server (new platform)

    Started August 10, 2026 at 2:45 PM UTC · 18m

    OutageMajor incident
    1. August 10, 2026 at 2:45 PM UTCinvestigating

      App server (new platform) went down

    2. August 10, 2026 at 3:03 PM UTCresolved

      App server (new platform) recovered

    App server (new platform)

    Started August 9, 2026 at 1:54 AM UTC · 2h 9m

    OutageMajor incident
    1. August 9, 2026 at 1:54 AM UTCinvestigating

      App server (new platform) went down

    2. August 9, 2026 at 4:03 AM UTCresolved

      App server (new platform) recovered

    App server (new platform)

    Started August 2, 2026 at 11:00 PM UTC · 3m

    OutageMajor incident
    1. August 2, 2026 at 11:00 PM UTCinvestigating

      App server (new platform) went down

    2. August 2, 2026 at 11:03 PM UTCresolved

      App server (new platform) recovered

    App server (legacy)

    Started August 2, 2026 at 12:15 AM UTC · 15m

    OutageMajor incident
    1. August 2, 2026 at 12:15 AM UTCinvestigating

      App server (legacy) went down

    2. August 2, 2026 at 12:30 AM UTCresolved

      App server (legacy) recovered

    App server (legacy)

    Started August 1, 2026 at 11:03 PM UTC · 9m

    OutageMajor incident
    1. August 1, 2026 at 11:03 PM UTCinvestigating

      App server (legacy) went down

    2. August 1, 2026 at 11:12 PM UTCresolved

      App server (legacy) recovered

    App server (legacy)

    Started August 1, 2026 at 2:10 AM UTC · 1h 8m

    OutageMajor incident
    1. August 1, 2026 at 2:10 AM UTCinvestigating

      App server (legacy) went down

    2. August 1, 2026 at 3:18 AM UTCresolved

      App server (legacy) recovered

    App server (legacy)

    Started July 31, 2026 at 1:22 PM UTC · 2m

    OutageMajor incident
    1. July 31, 2026 at 1:22 PM UTCinvestigating

      App server (legacy) went down

    2. July 31, 2026 at 1:24 PM UTCresolved

      App server (legacy) recovered

    App server (legacy)

    Started May 28, 2026 at 11:39 AM UTC · 9m

    OutageMajor incident
    1. May 28, 2026 at 11:39 AM UTCinvestigating

      App server (legacy) went down

    2. May 28, 2026 at 11:48 AM UTCresolved

      App server (legacy) recovered

    App server (legacy)

    Started May 28, 2026 at 11:22 AM UTC · 3m

    OutageMajor incident
    1. May 28, 2026 at 11:22 AM UTCinvestigating

      App server (legacy) went down

    2. May 28, 2026 at 11:24 AM UTCresolved

      App server (legacy) recovered

    App server unresponsive at times

    Started May 28, 2026 at 11:03 AM UTC · 0m

    Pending
    1. May 28, 2026 at 11:03 AM UTCresolved

      There were jobs taking excessive resources. We have fixed the performance of these jobs and service has been returned to normal.

    App server (legacy)

    Started May 28, 2026 at 10:48 AM UTC · 3m

    OutageMajor incident
    1. May 28, 2026 at 10:48 AM UTCinvestigating

      App server (legacy) went down

    2. May 28, 2026 at 10:51 AM UTCresolved

      App server (legacy) recovered

    Infrastructure issues

    Started May 8, 2026 at 2:03 AM UTC · 11m

    OutageMajor incident
    1. May 8, 2026 at 2:03 AM UTCinvestigating

      Apps are currently not working due to our Redis server being unavailable. We are working on the issue. Apologies for the service interruption.

    2. May 8, 2026 at 2:14 AM UTCresolved

      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].

    App server (new platform)

    Started May 8, 2026 at 1:06 AM UTC · 1h 3m

    OutageMajor incident
    1. May 8, 2026 at 1:06 AM UTCinvestigating

      App server (new platform) went down

    2. May 8, 2026 at 2:09 AM UTCresolved

      App server (new platform) recovered

    Recurring Tickets not being created

    Started February 16, 2026 at 1:01 AM UTC · 0m

    IssuesMinor incident
    1. February 16, 2026 at 1:01 AM UTCresolved

      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.

    Notify app notification unavailable

    Started January 13, 2026 at 1:59 AM UTC · 2h 10m

    OutageMajor incident
    1. January 13, 2026 at 1:59 AM UTCresolved

      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.

    2. January 13, 2026 at 4:09 AM UTCresolved

      The issue has been resolved, all apps working again as normal.

    Database issue

    Started January 12, 2026 at 4:49 PM UTC · 18m

    OutageMajor incident
    1. January 12, 2026 at 4:49 PM UTCinvestigating

      We are having issues with our database on our legacy app server and are looking into the cause, apologies for the outage.

    2. January 12, 2026 at 5:07 PM UTCresolved

      The apps are working again and we have rolled back a recent release. We are looking into the cause.

    Jobs not processing on time

    Started July 2, 2025 at 6:32 PM UTC · 0m

    IssuesMinor incident
    1. July 2, 2025 at 6:32 PM UTCresolved

      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.