Service disruption in us-east-3
Nov 7, 16:08 UTCNov 7, 17:26 UTC
Duration
1h 19m
Impact
Informational
Root cause
Not disclosed
Lambda, 90 days
7 incidents
Affected
Not listed by the vendor.
Final update
Severity Level: Medium This incident has been resolved. Between approximately 15:31 and 16:27 UTC, a fault in network equipment in the us-east-3 region disrupted some connectivity to instances in the region. Our teams found the cause and applied a fix. Service has been fully restored, and we have monitored the region since then to confirm it is stable. We’re also working on follow-up actions to prevent this from happening again. We apologize for the disruption and thank you for your patience. --- If you’re experiencing issues with your instances in us-east-3, please open a support ticket and we’ll get back to you as soon as possible.
Timeline
- Resolved · Nov 7, 17:26 UTC
Severity Level: Medium This incident has been resolved. Between approximately 15:31 and 16:27 UTC, a fault in network equipment in the us-east-3 region disrupted some connectivity to instances in the region. Our teams found the cause and applied a fix. Service has been fully restored, and we have monitored the region since then to confirm it is stable. We’re also working on follow-up actions to prevent this from happening again. We apologize for the disruption and thank you for your patience. --- If you’re experiencing issues with your instances in us-east-3, please open a support ticket and we’ll get back to you as soon as possible.
- Investigating · Nov 7, 16:08 UTC
Severity Level: Medium We’re currently investigating a potential issue with our On-Demand Cloud in the us-east-3 region. Users may experience connectivity issues with existing instances in us-east-3. Launching new instances in the region is currently unavailable. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you for your patience and understanding during this time. --- In the event you’re unsure as to whether your service is impacted by this incident, please open a support ticket. We’ll get back to you as soon as possible. **To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.**
More from Lambda
Full historylambda.ai Unreachable Due to DNS Issuelasted 2h 32mDegraded instance launches and terminations in us-east-3lasted 0mExperiencing issues with instance launches/terminations in us-west-1lasted 2h 56mUS-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminationslasted 2h 6mIssue with Cloud Services API Keyslasted 8h 54mInstances Unreachable in us-south-2 regionlasted 2d 2h