AWS Amazon CloudWatch (N. Virginia) Status

Service is operating normally: [RESOLVED] Elevated Faults for CloudWatch Logs APIs

Between 4:00 AM and 6:17 AM PST customers experienced elevated faults when calling CloudWatch Logs APIs in the US-EAST-1 Region. Log events and metrics were delayed, and CloudWatch alarms on delayed metrics transitioned into INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Service degradation: Elevated Faults for CloudWatch Logs APIs

We can confirm increased faults for CloudWatch Logs APIs in the US-EAST-1 Region. Log events and metrics are delayed. Alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics. Customers will experience faults in the CloudWatch Logs Management Console.

Last Update: A few months ago

Informational message: Elevated Faults for CloudWatch Logs APIs

We are investigating increased faults for CloudWatch Logs APIs in the US-EAST-1 Region. Log events and metrics may be delayed. Alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed Log Event Processing for Metric Filter Extraction and Subscriptions

Between 3:23 PM and 4:48 PM PDT , some customers experienced increased delays for CloudWatch log event processing for metric filter extraction and log subscriptions in the US-EAST-1 Region. Metrics extracted using Logs Filter Patterns were delayed, and CloudWatch alarms on those delayed metrics transitioned into INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events for subscriptions are in the process of backfilling. The service is operating normally.

Last Update: A few months ago

Informational message: Delayed Log Event Processing for Metric Filter Extraction and Subscriptions

We are investigating increased delays for CloudWatch log event processing for metric filter extraction and log subscriptions in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on metrics extracted using log filters.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Elevated API Faults

Between 9:29 AM and 10:00 AM PST, customers experienced increased faults for CloudWatch alarms APIs and delays in processing some alarms in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Informational message: Elevated API Faults

We are investigating increased faults for CloudWatch alarms APIs and delays in processing some alarms in the US-EAST-1 Region.

Last Update: A few months ago

Informational message: Elevated API faults

We are investigating increased faults for CloudWatch alarms APIs and delays in processing some alarms in the US-EAST-1 Region.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Increased Error Rates

Between 9:37 AM and 1:17 PM PST, customers experienced elevated faults when making GetMetricStatistics API requests for metrics data more than two days old in the US-EAST-1 Region and CloudWatch Dashboards were unavailable. Between 9:37 AM and 2:05 PM PST, CloudWatch logs customers experienced elevated API faults and delayed log events. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Informational message: Increased Error Rates

CloudWatch is starting to see service recovery. CloudWatch Metrics APIs fault rates and availability of data more than two days old has now recovered. CloudWatch Dashboards are now available for read only access. CloudWatch logs customers continue to experience elevated API faults and delayed log events. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Increased Error Rates

We can confirm impacts to the GetMetricStatistics API for metrics data more than two days old in the US-EAST-1 Region. Additionally, CloudWatch dashboards are currently unavailable. We are actively working to resolve the issue. Metric Graphs and GetMetricStatistic API requests configured to retrieve less than two days of data are working normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] CloudWatch Logs: Elevated Faults

Between 10:14 AM PDT and 10:44 AM PDT , some customers experienced elevated faults when calling CloudWatch Logs PUT APIs in the US-EAST-1 Region. We have resolved the issue and the service is operating normally.

Last Update: A few months ago

Informational message: CloudWatch Logs: Elevated Faults

We can confirm elevated CloudWatch Logs PUT API faults and some delayed log events in US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Alarm delays in US-EAST-1

Between 6:05 AM and 9:16 AM PDT, customers may have experienced some delayed alarms in the US-EAST-1 Region. The service is operating normally.

Last Update: A few months ago

Informational message: Alarm delays in US-EAST-1

We are investigating increased latencies for processing some alarms in the US-EAST-1 Region.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Alarm delays in US-EAST-1

We are investigating increased latencies for processing some alarms in the US-EAST-1 Region.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Elevated Latencies and Faults in US-EAST-1

Between 02:23 AM PDT and 07:27 AM PDT, customers experienced elevated faults when calling CloudWatch Logs and Metrics APIs in the US-EAST-1 Region. Customers also experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Informational message: Elevated Latencies and Faults in US-EAST-1

We are seeing recovery in API faults for CloudWatch metrics and logs in the US-EAST-1 Region. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. Customers may still experience delayed or missing data points for CloudWatch metrics and CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on affected metrics. We are continuing to monitor recovery.

Last Update: A few months ago

Performance issues: Elevated Latencies and Faults in US-EAST-1

We are beginning to see recovery in API faults for CloudWatch metrics and logs in the US-EAST-1 Region. Customers may still experience delayed or missing data points for CloudWatch metrics and CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on affected metrics. We are continuing to work to resolve the issue.

Last Update: A few months ago

Service disruption: Elevated Latencies and Faults in US-EAST-1

We can confirm significantly increased API faults for CloudWatch metrics and logs in the US-EAST-1 Region. Customers are experiencing delayed or missing data points for CloudWatch metrics and CloudWatch alarms will transition into "INSUFFICIENT_DATA" state if set on affected metrics.

Last Update: A few months ago

Performance issues: Elevated latencies and Faults in US-EAST-1

We can confirm increased delays for CloudWatch log events and API faults in the US-EAST-1 Region. Customers may experience delayed or missing data points for CloudWatch metrics and CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Elevated latencies and Faults in US-EAST-1

We are investigating increased faults and latencies for CloudWatch Logs, Metrics and Alarms APIs in the US-EAST-1 Region. Log events and metrics may be delayed. Alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Delayed Instance Status Check metrics in US-EAST-1

We are investigating delays for some EC2 Status Check metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on the delayed metrics. The EC2 service is operating normally, only EC2 CloudWatch metrics are affected.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Elevated API faults and latencies in US-EAST-1

Between 10:12 PM PDT on 7/30 and 12:50 AM PDT on 7/31, customers experienced elevated alarms API faults, delayed alarms, and delays in creating new metrics in the US-EAST-1 Region. We have restored service and CloudWatch is operating normally.

Last Update: A few months ago

Informational message: Elevated API faults and latencies in US-EAST-1

We have resolved the elevated alarms API faults in the US-EAST-1 Region and continue to work on resolving delays in creating new metrics.

Last Update: A few months ago

Performance issues: Elevated API faults and latencies in US-EAST-1

We can confirm an elevated rate of API faults and delays in processing some alarms in US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Elevated API faults and latencies in US-EAST-1

We are investigating increased faults and latencies for CloudWatch APIs and metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 2:05 PM PDT and 4:45 PM PDT in the US-EAST-1 Region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The CloudWatch service is operating normally.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Delayed Log Events in US-EAST-1

Between 2:10 PM and 2:47 PM PDT, some customers experienced increased delays for CloudWatch log events in the US-EAST-1 Region. Metrics filtered from those log events were delayed, and CloudWatch alarms on delayed metrics may have transitioned into INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Informational message: Delayed Log Events in US-EAST-1

Between 2:10 PM and 2:47 PM PDT, some customers experienced increased delays for CloudWatch log events in the US-EAST-1 Region. Metrics filtered from those log events were delayed, and CloudWatch alarms on delayed metrics may have transitioned into INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Informational message: Delayed/Missing Amazon Route 53 Health Check Metrics in US-EAST-1

Between 3:05 PM PDT and 3:45 PM PDT in the US-EAST-1 Region, customers experienced missing datapoints for Amazon Route 53 Health Check Status metrics. During that time, alarms on Amazon Route 53 Health Check Status metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. The service is operating normally.

Last Update: A few months ago

Informational message: Delayed/Missing Amazon Route 53 Health Check Metrics in US-EAST-1

Between 3:05 PM PDT and 3:45 PM PDT in the US-EAST-1 Region, customers experienced missing datapoints for Amazon Route 53 Health Check Status metrics. During that time, alarms on Amazon Route 53 Health Check Status metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Service is operating normally: [RESOLVED]Delayed metrics in US-EAST-1

Between 9:25 PM PDT and 11:30 PM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED]Delayed metrics in US-EAST-1

Between 9:25 PM PDT and 11:30 PM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 9:25 PM PDT and 11:30 PM PDT Aug 16 in the US-EAST-1 Region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 9:25 PM PDT and 11:30 PM PDT Aug 16 in the US-EAST-1 Region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 9:25 PM PDT and 11:30 PM PDT Aug 16 in the US-EAST-1 Region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in processing some alarms in the US-EAST-1 Region. We continue to work to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 Region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 Region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 05:15 AM PDT and 07:45 AM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 05:15 AM PDT and 07:45 AM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 05:15 AM PDT and 07:45 AM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 05:15 AM PDT and 07:45 AM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The issue has been resolved and the service is operating normally.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We can confirm delays in some CloudWatch metrics in the US-EAST-1 region. We are actively working to resolve the issue.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

Informational message: Elevated API faults and latencies in US-EAST-1

Between 09:30 PM and 10:20 PM PDT, some customers experienced elevated faults when calling CloudWatch Logs APIs in the US-EAST-1 Region. Some log events and metrics were delayed, and CloudWatch alarms on delayed metrics transitioned into INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events have now been backfiled in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Informational message: Elevated API faults and latencies in US-EAST-1

Between 09:30 PM and 10:20 PM PDT, some customers experienced elevated faults when calling CloudWatch Logs APIs in the US-EAST-1 Region. Some log events and metrics were delayed, and CloudWatch alarms on delayed metrics transitioned into INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events have now been backfiled in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 07:10 AM PDT and 07:45 AM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Service is operating normally: [RESOLVED] Delayed metrics in US-EAST-1

Between 07:10 AM PDT and 07:45 AM PDT in the US-EAST-1 region, customers experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.

Last Update: A few months ago

Informational message: Delayed metrics in US-EAST-1

We are investigating increased delays for CloudWatch metrics in the US-EAST-1 region. CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics.

Last Update: A few months ago

© 2018 - Cloudstatus built by jameskenny