INKY incident

INKY - Google Workspace partners - Emails fail to send or receive

Resolved after 6 hours 59 minutes, affecting Google Workspace, on April 8, 2026.

postmortem Apr 24, 2026, 03:51 PM UTC

On March 31s, our dev team observed that an email filter host was having a disproportionate amount of traffic sent to it, that was slowing down the response time. This in turn caused additional pressure on some of our backend resources that were slowing down the email processing time. This traffic did not cause the service to crash and auto scaling did not occur due to the CPU processing of the items not breaking a threshold.

Started
Apr 08, 2026, 04:03 PM UTC
Resolved
Apr 08, 2026, 11:02 PM UTC
Duration
6h 59m
Detected by Pingoru
Apr 08, 2026, 04:03 PM UTC

Affected components

Google Workspace

Update timeline

  1. investigating Apr 08, 2026, 04:03 PM UTC

    We are aware of a problem where Google Workspace Inky partners' emails are not being sent or received, intermittently. The Kaseya R&D Team is currently investigating this issue.

  2. investigating Apr 08, 2026, 05:50 PM UTC

    We are continuing to investigate and will provide another update as soon as we have more information to provide.

  3. identified Apr 08, 2026, 06:42 PM UTC

    The issue has been identified by our dev team and is due to an issue with Google Workspace. You can view their status page here: https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT Inky's service is dependent on Google Workspace's ability to send emails and will be dependent on Google Workspace restoring service. We will provide another update as we have more information or Google Workspace restores email functionality.

  4. resolved Apr 08, 2026, 11:02 PM UTC

    Google has reported that email functionality has been restored and this issue has been resolved. Internal monitoring is showing INKY traffic has returned to normal.

  5. postmortem Apr 24, 2026, 03:51 PM UTC

    On March 31s, our dev team observed that an email filter host was having a disproportionate amount of traffic sent to it, that was slowing down the response time. This in turn caused additional pressure on some of our backend resources that were slowing down the email processing time. This traffic did not cause the service to crash and auto scaling did not occur due to the CPU processing of the items not breaking a threshold.

Your product runs on more than INKY

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →