Pagely incident
Subset of EC2 instances in AWS Virginia Experiencing Issues
Pagely experienced a major incident on May 8, 2026 affecting VPS Hosting Infrastructure, lasting 7h 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 12:05 AM UTC
We are investigating an issue affecting a subset of EC2 instances in AWS US East (Virginia). Those instances are temporarily unreachable while we determine root cause.
- identified May 08, 2026, 12:41 AM UTC
We have identified the affected EC2 instances in AWS. Reboots have been started on all of them while we continue to confirm recovery. Additional updates will be provided shortly.
- identified May 08, 2026, 01:01 AM UTC
A few hosts still show EBS volume issues that prevent a full restart; we are actively fixing those and continuing investigation alongside the broader recovery work.
- identified May 08, 2026, 03:00 AM UTC
A small number of instances still have an EBS-related issue we’re actively investigating, and all other instances, those not affected by this problem, have been back to normal for some time now.
- identified May 08, 2026, 06:19 AM UTC
We’ve restored several EBS volumes and brought associated EC2 instances back online; work is still in progress on the remaining instances, and we’ll share another update shortly.
- monitoring May 08, 2026, 07:38 AM UTC
All affected instances are now restored and we continue to monitor for any issues.
- resolved May 08, 2026, 07:50 AM UTC
This incident is now resolved.