Is Indicator testing down or not working?

What happened to Indicator testing, why did the service go down and not work? Here you can see who else is having the same problem with Indicator testing, as well as possible solutions. According to our statistics, the following most often do not work: af-south-1, ap-east-1, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ap-southeast-3, AWS Console, ca-central-1, EC2, eu-central-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-1, eu-west-2, eu-west-3, me-central-1, me-south-1, sa-east-1, us-east-1, us-east-2, us-gov-east-1, us-gov-west-1, us-west-1, us-west-2.

Current status: No failures

At the moment, according to our data, Indicator testing is working fine, but single failures are possible. If Indicator testing does not work for you, then report your problem and write a comment.
Add comment

Indicator testing outage reports in the last 24 hours

User reports by hour (UTC), last 24 hours

Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0

Total weight in 24 hours: 0 Busiest hour: 21:00 UTC (weight 0)

How this score compares

Current 24-hour weight is 0. Warnings start at 20, Failed at 50. Median services on this language today is 0.

Other services in this category

Indicator testing covers internal checks that AWS runs to confirm its systems respond as expected. When you see activity here, it usually means engineers are probing status systems rather than fixing a problem. Most of the time, no action is needed on your part, and your workloads keep running normally.
This page tracks indicator testing across many AWS regions and services, from us-east-1 to ap-northeast-2 and beyond. These tests generate signals on purpose so the monitoring pipeline can be verified end to end. They are routine and not tied to customer incidents. Because the tests touch a wide list of regions, entries can appear in several places at once. That is expected. A test in one region does not imply problems in another. On your side, there is little to check. If you notice an unrelated error in your own application, look at your CloudWatch metrics and service quotas first. Indicator testing entries resolve on their own and rarely require follow-up.

Questions

Is Indicator testing down right now?

According to reports on this page, Indicator testing looks fine for most people. Isolated failures still happen — report yours if you are stuck.

When was the last mass outage?

We do not have a recorded mass outage for Indicator testing yet.

Do indicator tests affect my running instances?

No. The tests inject signals into monitoring systems only. They do not touch EC2 instances, storage, or network traffic belonging to customers.

Why do tests show up in so many regions at once?

The monitoring pipeline is global, so verification runs across the full region list together. Seeing multiple regions in one entry is normal and does not mean a wide incident.

Indicator testing - error and failure reports, troubleshooting methods

Is Indicator testing down or not working?
Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.