Resolved on October 22, 2026.
On 10/21/2026, between 5:00 PM and 5:40 PM Pacific, some customers received 502 errors when trying to access Aeries. The cause was a configuration change that was deployed in error. We reverted the change and service was fully restored after about 40 minutes. We apologize for the disruption, and we are reviewing our deployment process to help prevent this from happening again.
Update timeline
- resolved Oct 22, 2026, 12:51 AM UTC
On 10/21/2026, between 5:00 PM and 5:40 PM Pacific, some customers received 502 errors when trying to access Aeries. The cause was a configuration change that was deployed in error. We reverted the change and service was fully restored after about 40 minutes. We apologize for the disruption, and we are reviewing our deployment process to help prevent this from happening again.
Your product runs on more than Aeries Software
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services