The underlying incident has now been resolved and all systems are operational again. This incident was caused by an outage in AWS us-east-2 AZ-1 losing power, which resulted in some of our critical systems failing. We failed over to other AZs where we could, restoring operational capability.
As a result of this incident however you may see:
Missing API logs from your dashboard for the period of 16:59 - 17:30 UTC
Missing workflow run logs for the period of 16:59 - 17:30 UTC
Resolved
The underlying incident has now been resolved and all systems are operational again. This incident was caused by an outage in AWS us-east-2 AZ-1 losing power, which resulted in some of our critical systems failing. We failed over to other AZs where we could, restoring operational capability.
As a result of this incident however you may see:
Missing API logs from your dashboard for the period of 16:59 - 17:30 UTC
Missing workflow run logs for the period of 16:59 - 17:30 UTC
Monitoring
All services within Knock are operational again. Some downstream providers may still be impacted by the outage in AWS us-east-2.
We're continuing to monitor.
Investigating
There are ongoing issues with downstream providers, some notification deliverability may be impacted as a result.
Current Knock status:
In-app feeds are operational
Notification engine is processing normally
Webhooks are processing normally
Workflow run logs are delayed
API logs are delayed
Investigating
Our current status is:
In-app feeds are partially degraded
Notifications are still being sent
API logs are not currently being processed
Workflow run logs are currently not being processed
Webhooks are current not being processed
Investigating
We're having a major outage with our hosting provider. We're currently looking for ways to mitigate.