Incident in AWS
18 days ago

Increased API Error Rates

Resolved Minor
6:52 PM PDT We are investigating an increased error rates and latencies for the ELB APIs in the US-EAST-1 Region. Some other AWS services - including Elastic Container Service, Amazon Certificate Manager, and Directory Services - are also experiencing API error rates and latencies. Existing load balancers are not affected by the issue. We are working to identify the root cause and resolve the issue. 7:03 PM PDT We have identified the root cause of the increased error rates and latencies for the ELB APIs in the US-EAST-1 Region. This is causing increased provisioning times for new load balancers, as well as delays in registering new instances and targets. Connections and traffic to existing load balancers are not affected by the issue. Some other AWS services - including Elastic Container Service, Amazon Certificate Manager, and Directory Services - are also experiencing API error rates and latencies. We are working to resolve the issue and expect to see an improvement in error rates as that progresses. 7:54 PM PDT We continue to make progress towards resolving the increased error rates and latencies for the ELB APIs in the US-EAST-1 Region. While error rates have stabalized, we continue to see increased provisioning times for new load balancers, as well as delays in registering new instances and targets. Connections and traffic to existing load balancers are not affected by the issue. Some other AWS services - including Elastic Container Service, Amazon Certificate Manager, and Directory Services - are also experiencing API error rates and latencies. We will continue to keep you updated on our progress. 8:13 PM PDT Starting at 7:46 PM PDT we experienced higher error rates and latencies for AWS services within the US-EAST-1 region. These error rates and latencies have seen some improvement from 7:55 PM PDT, but remain elevated. The issue is also affecting the AWS Management Console for the US-EAST-1 region. We continue to work towards mitigating the impact and will continue to provide updates as we progress. 8:38 PM PDT We continue to work on addressing the error rates and latencies for AWS services in the US-EAST-1 Region. The issue initially affected the Elastic Load Balancing APIs, with some impact to other services, including Elastic Container Service, Amazon Certificate Manager, and Directory Services. At 7:46 PM PDT, other AWS services began to experience an increase in error rates and latencies. Action was taken and error rates started to improve at 7:55 PM PDT. This issue also affected access to the the AWS Management Console for the US-EAST-1 Region. Error rates and latencies for services in the US-EAST-1 Region remain elevated for a number of services, including Connect, DynamoDB, SQS, SNS, EC2, CloudFormation, CloudFront, amongst others. We continue to work towards resolving the issue. 9:13 PM PDT We continue to see a reduction in error rates and latencies for AWS services within the US-EAST-1 Region as we work to resolve the issue. While many AWS services are experiencing elevated error rates and latencies, services that are experiencing higher error rates have been tagged on this Service Health Dashboard event. The event continues to affect APIs for affected services, while the EC2 network, Elastic Load Balancing and API Gateway data planes are not affected by this issue. The AWS Management Console is operating normally, however some customers may observe API Errors at times. AWS Connect error rates have improved as well and we continue to work towards full recovery. We are working on applying mitigations to fully resolve the issue. 9:32 PM PDT We continue to see a reduction in API error rates and latencies for services within the US-EAST-1 Region. Elastic Load Balancer APIs have recovered and returned to normal levels. The AWS Management Console has recovered. AWS Connect error rates have returned to normal levels. CloudWatch metrics have recovered and the EC2 API error rates have returned to normal levels. DynamoDB has recovered and is operating normally. Services that were affected by this event remain tagged to this Service Health Dashboard event. The event continues to affect APIs for affected services, while the EC2 network, Elastic Load Balancing and API Gateway data planes are not affected by this issue.
Don't waste time! Know when there's an external outage happening.

Monitor AWS and all your business critical cloud services

Never miss when your external dependencies are down. Instant notifications when there are outages.

Get Started Free 197 companies signed up in the last month!
No credit card required · Cancel anytime · 1622 services available to monitor

"I spend 2 hours trying to solve an issue and then realize it's due to an [EXTERNAL SERVICE] outage"
Every engineer at some point in time

How can we help?

No more frantic searching for the source of the problem.

All of your service statuses in one place

Check the status of all your services in one place. No more going to each of the status pages and managing them individually.

Notifications of incidents in real time

We monitor 24 hours a day, 7 days a week and will notify you if there is an incident. No more wasting time trying to figure out why something isn't working.

Notifications in your favorite channel

Get instant notifications in your email, Slack, or Discord.

Keep track of scheduled maintenance

Never again be caught off guard by unexpected maintenance from your services. A feed of the next scheduled maintenances is available.

Set the notification level for each service

Configure which notifications you want to receive from each service. You can choose to receive notifications for all incidents, only critical incidents, or just display them on the dashboard.

Integrate with your current workflows

Using Zapier or Webhooks, you can easily integrate notifications into your processes.

Receive a Weekly Digest

Every Monday, you'll receive a weekly summary of what happened the previous week as well as the maintenance schedule for the following week.

Multiple Profiles

Create one profile for each of your teams. One Dashboard and specific Notifications settings for each team.

Only receive notifications for specific components

Filter notifications by service components. You can opt to receive notifications only when a specific component is affected.

For every team in your company

Engineering

Add another dimension (external systems) to your monitoring data and complement it with the external factors. Monitor the services your company relies on for the development experience. Don't waste time looking elsewhere, when it's an external outage.

Customer Support

Know before your clients tell you. Anticipate possible issues and make the necessary arrangements. Understand if your business is being impacted by outages in external services.

Marketing

One of your competitors is down? Maybe a good time to spread the word about your service.

Start monitoring
all your essential services

  1. Step 1 Create an account

    Start with a trial account that will allow you to try and monitor up to 30 services for 14 days.

  2. Step 2 Select your services

    There are 1622 services to choose from, and we're adding more every week.

  3. Step 3 Set up notifications

    You can get notifications by email, Slack, and Discord. You can also use Zapier or Webhooks to build your workflows.

Frequently Asked Questions

Is AWS down today?
AWS seems to be up and running. We've updated the status 1 minute ago.
I'm having issues with AWS, but the status is OK. What's going on?
There are a few things you can try:
How can I be notified when AWS is having issues?
You can subscribe for updates on the official status page or create an account in IsDown. We will send you a notification in real-time when AWS has issues.
Why use IsDown?
We want to keep you updated on the status of the services that impact your company. You can setup a notification via email, Slack, or Discord when a service you monitor has issues or when maintenances are scheduled.
What happens when I create an account?
You'll have access to a 14-day trial in our Pro plan. You can cancel or delete your account anytime. After 14 days, you'll need to subscribe to continue to use the service and get notifications.
How can I pay for a subscription?
You can go to the Billing section in your account and choose one of the plans. We've monthly and yearly options. We accept all major credit cards, Apple Pay, and Google Play. We use Stripe for payments.
Can I get a refund?
We'll refund your subscription if you cancel it until ten days after the subscription has started. No questions asked.
Are we missing an integration?
Contact us, and we'll add it ASAP.

Ready to start monitoring your cloud services?

Increase the productivity and efficiency of your team. Enable monitoring for your services, and start receiving real-time alerts when your services have outages.

Start today for FREE