Coralogix incident
AWS is experiencing an incident that is affecting the collection of AWS metrics and resources and causing issues with the chat application.
Coralogix experienced a notice incident on October 20, 2025 affecting Metrics Processing, lasting 13h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 07:28 AM UTC
AWS is experiencing an “Operational issue - Multiple services (N. Virginia)” in the us-east-1 region, impacting the collection of AWS metrics and resources. Don't hesitate to contact our support for assistance. AWS Status updates: https://health.aws.amazon.com/health/status
- investigating Oct 20, 2025, 07:30 AM UTC
We are continuing to monitor this issue.
- investigating Oct 20, 2025, 07:36 AM UTC
AWS is currently experiencing an “Operational issue - Multiple services (N. Virginia)” in the us-east-1 region, which is impacting the collection of AWS metrics and resources. This issue is also affecting the chat application. If you need any assistance, please don’t hesitate to contact our support team at [email protected] AWS Status updates: https://health.aws.amazon.com/health/status
- identified Oct 20, 2025, 09:27 AM UTC
Some AWS services have been restored, and the chat application is back online.
- monitoring Oct 20, 2025, 12:37 PM UTC
AWS is still experiencing an “Operational issue - Multiple services (N. Virginia)” in the us-east-1 region, but it is mostly restored and doesn't impact metrics collection. The chat application is back online. If you need any assistance, please don’t hesitate to contact our support team at [email protected] AWS Status updates: https://health.aws.amazon.com/health/status
- monitoring Oct 20, 2025, 03:15 PM UTC
The chat application is back online, although it may take a bit longer than usual to load. If you experience any issues or the chat fails to load, please contact us at [email protected] - we’ll be happy to assist you with your questions and requests via email. No other issues have been observed or reported.
- resolved Oct 20, 2025, 08:41 PM UTC
This incident has been resolved.