Amazon Connect Status: How to Check If Amazon Connect Is Down

Calls failing, agents can’t log in, or the CCP is stuck? Before you start a long troubleshooting session, check the Amazon Connect status to see whether the service itself is having a problem. This guide shows the official places to check Amazon Connect status, and how to tell an AWS outage from a problem on your side.

1. Check Amazon Connect Status on the AWS Health Dashboard

The public AWS Health Dashboard shows the status of every AWS service in every Region. No login is needed. Search for Amazon Connect and check your Region, for example US East (N. Virginia) or Europe (London).

2. AWS Health in Your Account

Your account view shows events that affect your resources, including planned maintenance. Sign in to the AWS console, then open AWS Health → Your account health. This often shows issues earlier and in more detail than the public page.

3. Get Alerts Automatically with EventBridge

Do not wait for agents to report problems. Create an Amazon EventBridge rule for AWS Health events and send them to Amazon SNS (email or SMS), Slack or Microsoft Teams.

{
  "source": ["aws.health"],
  "detail-type": ["AWS Health Event"],
  "detail": { "service": ["CONNECT"] }
}

Use this event pattern in your EventBridge rule, and set an SNS topic as the target. Create the rule in the same Region as your Amazon Connect instance, because AWS Health sends events to EventBridge in the Region where the event happens.

Want to confirm the service code yourself? Run this in AWS CloudShell. It lists every Amazon Connect event type AWS Health can send:

aws health describe-event-types --filter services=CONNECT --region us-east-1 --query "eventTypes[].[code,category]" --output table

The AWS Health API endpoint is in us-east-1, so keep --region us-east-1 even if your instance is in another Region. The API needs a Business, Enterprise On-Ramp or Enterprise Support plan; without one you get a SubscriptionRequiredException, but the EventBridge rule still works.

Is It AWS or Is It Us?

Symptom	If AWS Health shows an issue	If AWS Health is clear
All agents in all locations affected	Likely an AWS event. Follow the AWS updates.	Check your instance config, SAML/IdP and recent changes
Only one site or office affected	Unlikely to be AWS	Check that site’s firewall, proxy, VPN and ISP
One agent affected	Not AWS	Check the agent’s browser, headset and network
Calls fail in contact flows	Check AWS Health for Lambda or Lex too	Check CloudWatch flow logs and Lambda errors

Check Your Own Side

1. Run the Amazon Connect Endpoint Test Utility from an affected agent’s computer.
2. Open CloudWatch → Metrics → AWS/Connect and look at CallsPerInterval, ThrottledCalls, MissedCalls and ContactFlowErrors.
3. Check contact flow logs and Lambda logs in CloudWatch Logs for errors.
4. Download CCP logs from an affected agent.
5. Review recent changes: new flows, IAM edits, firewall rules or IdP certificate rotation.

Related Guides

• Amazon Connect 503 errors at peak volume
• Fix Amazon Connect API throttling (429)
• AWS ME-CENTRAL-1 outage recovery

Frequently Asked Questions

How do I check if Amazon Connect is down?

Check the public AWS Health Dashboard at health.aws.amazon.com for Amazon Connect in your Region, then check AWS Health in your own AWS console for account-specific events.

Is there an Amazon Connect status page?

Amazon Connect status is shown on the AWS Health Dashboard, alongside all other AWS services, broken down by Region.

How do I get alerts when Amazon Connect has an issue?

Create an Amazon EventBridge rule for AWS Health events with service CONNECT and send them to an SNS topic, Slack or Microsoft Teams.

AWS Health is green but calls are failing. What next?

The problem is likely on your side. Run the Endpoint Test Utility, check CloudWatch metrics and logs, review CCP logs, and look at recent changes.