Dear Digication Community,
Status: RESOLVED
Service disruption impact window (ET): Approximately 5:27 AM — 9:00 AM ET on May 8, 2026, during which users experienced timeouts, slow page loads, and intermittent errors when accessing Digication.
What happened
The disruption was caused by an upstream incident at our cloud provider, Amazon Web Services (AWS), affecting the us-east-1 region. A power and cooling event in one of AWS's data center availability zones impacted database infrastructure that Digication depends on. Specifically, our read-replica database remained in an extended recovery state for approximately 3.5 hours while AWS worked to restore the affected zone. During this period, application requests that relied on that database were unable to complete in a timely manner, resulting in the slow responses and errors that customers observed.
Resolution
The database returned to a healthy state once AWS restored the affected availability zone. No data was lost, and no customer action is required.
What we're doing next
While the underlying cause was an AWS infrastructure event outside our direct control, we are reviewing our resilience posture to reduce the impact of similar events in the future. Planned improvements include:
- Faster failure detection so unhealthy components are taken out of rotation more quickly
- Tighter database timeouts and improved fallback behavior so the application degrades gracefully rather than hanging
- Multi-zone redundancy improvements for our database read capacity
We sincerely apologize for the disruption and appreciate your patience!
If you continue to experience any issues, please contact our support team at [support@digication.com](mailto:support@digication.com).
Kind regards,
Your friends at Digication