{"id":17454,"date":"2026-06-12T13:00:00","date_gmt":"2026-06-12T19:00:00","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=17454"},"modified":"2026-06-11T00:01:38","modified_gmt":"2026-06-11T06:01:38","slug":"troubleshoot-alb-ec2-intermittent-timeouts","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/troubleshoot-alb-ec2-intermittent-timeouts\/","title":{"rendered":"How to Troubleshoot Intermittent Timeouts Between AWS ALB and EC2 Instances"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Intermittent timeouts between an AWS Application Load Balancer (ALB) and EC2 instances can be among the most frustrating infrastructure issues to diagnose. Unlike complete outages, these problems occur sporadically, making them difficult to reproduce and often difficult to detect through standard monitoring alerts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In most cases, the ALB can successfully reach the target EC2 instance, but the instance either responds too slowly or fails to complete the connection within the expected timeframe. This results in occasional request failures, degraded application performance, and a poor user experience.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we&#8217;ll explore the most common causes of ALB-to-EC2 timeouts and provide a step-by-step troubleshooting framework to help identify and resolve the issue.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding ALB and EC2 Timeout Issues<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">AWS Application Load Balancers are designed to distribute incoming traffic across multiple targets efficiently. When an ALB forwards a request to an EC2 instance, it expects a response within a specific period.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the backend instance fails to respond before the timeout threshold is reached, the ALB returns an error, typically:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>HTTP 504 Gateway Timeout<\/li>\n\n\n\n<li>ELB 504 Errors<\/li>\n\n\n\n<li>Connection timeout messages<\/li>\n\n\n\n<li>Slow application responses<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When these failures occur intermittently, the root cause is usually related to backend performance, network communication, or configuration mismatches.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Common Causes of Intermittent ALB Timeouts<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Slow or Blocked Application Processing<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most common causes of ALB timeouts is application-level performance degradation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even if the server itself appears healthy, the application may struggle to process requests efficiently.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common Application Issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Thread pool exhaustion<\/li>\n\n\n\n<li>Long-running database queries<\/li>\n\n\n\n<li>Deadlocks between application processes<\/li>\n\n\n\n<li>Resource-intensive operations<\/li>\n\n\n\n<li>Garbage collection pauses in Java applications<\/li>\n\n\n\n<li>Worker shortages in Node.js, Python, or PHP applications<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When application resources become saturated, incoming requests begin queuing and eventually exceed ALB timeout limits.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Identify the Issue<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application logs<\/li>\n\n\n\n<li>Request processing times<\/li>\n\n\n\n<li>Database query performance<\/li>\n\n\n\n<li>Thread utilization<\/li>\n\n\n\n<li>Error logs<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Look for requests that consistently take longer than expected to complete.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2. ALB Idle Timeout Mismatch<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">AWS ALB uses a default idle timeout value of 60 seconds.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the application keeps connections open longer than the configured ALB timeout, the load balancer may terminate the connection before the backend response is returned.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common Symptoms<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Random 504 Gateway Timeout errors<\/li>\n\n\n\n<li>Long-running API requests failing<\/li>\n\n\n\n<li>File upload interruptions<\/li>\n\n\n\n<li>Timeout errors during large data processing tasks<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to Fix It<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review your ALB configuration and compare it with your application&#8217;s expected response times.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If necessary:<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Open the AWS Console.<\/li>\n\n\n\n<li>Navigate to the Load Balancer settings.<\/li>\n\n\n\n<li>Select <strong>Attributes<\/strong>.<\/li>\n\n\n\n<li>Increase the idle timeout value.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on workload requirements, administrators commonly configure values between:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>120 seconds<\/li>\n\n\n\n<li>180 seconds<\/li>\n\n\n\n<li>300 seconds<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Only increase the timeout after confirming that long-running requests are expected behavior.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3. Security Group and Network ACL Misconfigurations<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Network communication issues can also lead to intermittent timeout behavior.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In some environments, inbound traffic may be allowed while return traffic is unintentionally restricted.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common Causes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Overly restrictive Network ACLs<\/li>\n\n\n\n<li>Blocked ephemeral ports<\/li>\n\n\n\n<li>Incorrect Security Group rules<\/li>\n\n\n\n<li>Routing inconsistencies<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to Verify<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ensure:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ALB Security Group allows communication to EC2 instances<\/li>\n\n\n\n<li>EC2 Security Group accepts traffic from the ALB<\/li>\n\n\n\n<li>Outbound traffic is permitted<\/li>\n\n\n\n<li>Ephemeral ports (1024\u201365535) are not blocked<\/li>\n\n\n\n<li>Network ACLs allow bidirectional communication<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Improper network filtering can create connection failures that appear random and difficult to diagnose.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4. EC2 Resource Exhaustion<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Backend resource constraints frequently contribute to timeout issues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even if health checks succeed, resource exhaustion can significantly slow request processing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Resources to Monitor<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">CPU Utilization<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">High CPU usage may indicate:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Traffic spikes<\/li>\n\n\n\n<li>Inefficient code execution<\/li>\n\n\n\n<li>Excessive background tasks<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Memory Usage<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Memory pressure can result in:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application slowdowns<\/li>\n\n\n\n<li>Process termination<\/li>\n\n\n\n<li>Out-of-memory conditions<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Disk I\/O<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Heavy storage activity can delay application responses and database operations.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">File Descriptors<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Applications may exhaust available file handles under heavy load.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting Checklist<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU utilization metrics<\/li>\n\n\n\n<li>Memory consumption<\/li>\n\n\n\n<li>Disk I\/O wait times<\/li>\n\n\n\n<li>Network throughput<\/li>\n\n\n\n<li>Open file descriptors<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">On Linux systems, verify file descriptor limits using:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ulimit -n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended Fixes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Upgrade EC2 instance size<\/li>\n\n\n\n<li>Enable Auto Scaling<\/li>\n\n\n\n<li>Increase worker processes<\/li>\n\n\n\n<li>Optimize application performance<\/li>\n\n\n\n<li>Resolve memory leaks<\/li>\n\n\n\n<li>Adjust operating system limits<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">5. Healthy Targets That Cannot Handle Real Traffic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A target group may report all instances as healthy while users continue experiencing failures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This typically occurs when health checks are too simple compared to actual application workloads.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A health check endpoint may return a response in milliseconds, while production requests require:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Database queries<\/li>\n\n\n\n<li>API integrations<\/li>\n\n\n\n<li>File processing<\/li>\n\n\n\n<li>Authentication workflows<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, AWS reports the instance as healthy even though it struggles under real traffic conditions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Improve Health Checks<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Design health check endpoints that:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Verify critical application components<\/li>\n\n\n\n<li>Validate database connectivity<\/li>\n\n\n\n<li>Test essential dependencies<\/li>\n\n\n\n<li>Remain lightweight and efficient<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Additional Recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increase health check thresholds<\/li>\n\n\n\n<li>Adjust healthy and unhealthy target settings<\/li>\n\n\n\n<li>Monitor target response times continuously<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">6. Connection Draining and Instance Deregistration Delays<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Intermittent timeouts often occur during scaling events or infrastructure maintenance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Auto Scaling termination<\/li>\n\n\n\n<li>Instance replacement<\/li>\n\n\n\n<li>Rolling deployments<\/li>\n\n\n\n<li>Manual server maintenance<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If connections are interrupted before requests finish processing, users may experience timeout errors.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Verify<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Auto Scaling events<\/li>\n\n\n\n<li>Deployment activity<\/li>\n\n\n\n<li>Target registration logs<\/li>\n\n\n\n<li>Deregistration delay settings<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended Fix<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Configure an appropriate deregistration delay to allow active requests to complete before the instance is removed from service.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step-by-Step ALB Timeout Troubleshooting Process<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Confirm the Error Type<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Start by reviewing ALB access logs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Look for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>HTTP 504 errors<\/li>\n\n\n\n<li>ELB 504 responses<\/li>\n\n\n\n<li>Elevated target processing times<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pay special attention to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>target_processing_time<\/code><\/li>\n\n\n\n<li><code>request_processing_time<\/code><\/li>\n\n\n\n<li><code>response_processing_time<\/code><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If target processing times are consistently high, the issue likely exists on the backend server or application layer.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Check Target Health<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Navigate to:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Target Groups \u2192 Targets<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Frequent health check failures<\/li>\n\n\n\n<li>Targets entering and leaving service<\/li>\n\n\n\n<li>Slow response times<\/li>\n\n\n\n<li>Recent scaling activities<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If health checks fail repeatedly:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increase the healthy threshold<\/li>\n\n\n\n<li>Reduce health check complexity<\/li>\n\n\n\n<li>Optimize application startup time<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Review ALB Timeout Configuration<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Compare:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ALB idle timeout settings<\/li>\n\n\n\n<li>Application response times<\/li>\n\n\n\n<li>API execution durations<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If legitimate requests exceed the timeout value, adjust the ALB configuration accordingly.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Evaluate EC2 Health and Performance<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Inspect:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU utilization<\/li>\n\n\n\n<li>Memory usage<\/li>\n\n\n\n<li>Disk performance<\/li>\n\n\n\n<li>Network throughput<\/li>\n\n\n\n<li>Process limits<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">CloudWatch metrics can provide valuable insights into resource bottlenecks during timeout events.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Enable Detailed Application Logging<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Application-level visibility is critical when diagnosing intermittent issues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Log:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Request start times<\/li>\n\n\n\n<li>Request completion times<\/li>\n\n\n\n<li>Exception details<\/li>\n\n\n\n<li>Database query durations<\/li>\n\n\n\n<li>External API call latency<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This information helps correlate backend delays with ALB timeout events.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Verify Network Security Configuration<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm that:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ALB Security Groups allow traffic to EC2<\/li>\n\n\n\n<li>EC2 Security Groups allow responses<\/li>\n\n\n\n<li>Network ACLs permit bidirectional communication<\/li>\n\n\n\n<li>No firewall rules block return traffic<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Network misconfigurations can often mimic application performance issues.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Best Practices to Prevent Future ALB Timeout Issues<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">To improve long-term reliability:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Implement Proactive Monitoring<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Monitor:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ALB latency<\/li>\n\n\n\n<li>Target response times<\/li>\n\n\n\n<li>CPU utilization<\/li>\n\n\n\n<li>Memory consumption<\/li>\n\n\n\n<li>Error rates<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Enable Auto Scaling<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Automatically adjust capacity during traffic spikes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Optimize Application Performance<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Reduce:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Database query latency<\/li>\n\n\n\n<li>API response times<\/li>\n\n\n\n<li>Resource-intensive operations<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Improve Logging and Observability<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon CloudWatch<\/li>\n\n\n\n<li>AWS X-Ray<\/li>\n\n\n\n<li>Centralized log management<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">to gain deeper visibility into application behavior.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Regularly Review Load Balancer Settings<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ensure timeout values, health checks, and scaling configurations align with application requirements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Intermittent timeouts between AWS Application Load Balancers and EC2 instances are typically caused by backend performance bottlenecks, idle timeout mismatches, resource exhaustion, health check limitations, or networking misconfigurations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By following a structured troubleshooting approach and monitoring both infrastructure and application behavior, administrators can quickly identify the root cause and improve overall system reliability. Proactive monitoring, optimized application performance, and properly configured ALB settings are essential for delivering a stable and responsive user experience.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a href=\"https:\/\/www.supportpro.com\/requestquote.php\" title=\"\">Experiencing AWS Load Balancer or EC2 Performance Issues?<\/a><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Intermittent timeout errors can impact application performance, customer experience, and business operations. <a href=\"https:\/\/www.supportpro.com\/requestquote.php\" title=\"\">Contact SupportPRO today<\/a> for expert AWS administration, performance optimization, and 24\/7 infrastructure support.<\/p>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile is-vertically-aligned-center has-white-background-color has-background\"><div class=\"wp-block-media-text__content\">\n<p class=\"has-large-font-size wp-block-paragraph\">Facing issues? <\/p>\n\n\n\n<p class=\"has-large-font-size wp-block-paragraph\">Our technical support<br>engineers can solve it. <\/p>\n\n\n\n<!--HubSpot Call-to-Action Code --><span class=\"hs-cta-wrapper\" id=\"hs-cta-wrapper-3350a795-db50-482f-9911-301930d1b1be\"><span class=\"hs-cta-node hs-cta-3350a795-db50-482f-9911-301930d1b1be\" id=\"hs-cta-3350a795-db50-482f-9911-301930d1b1be\"><!--[if lte IE 8]><div id=\"hs-cta-ie-element\"><\/div><![endif]--><a href=\"https:\/\/cta-redirect.hubspot.com\/cta\/redirect\/2725694\/3350a795-db50-482f-9911-301930d1b1be\" ><img decoding=\"async\" class=\"hs-cta-img\" id=\"hs-cta-img-3350a795-db50-482f-9911-301930d1b1be\" style=\"border-width:0px;\" src=\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\"  alt=\"Contact Us today!\"\/><\/a><\/span><script charset=\"utf-8\" src=\"https:\/\/js.hscta.net\/cta\/current.js\"><\/script><script type=\"text\/javascript\"> hbspt.cta.load(2725694, '3350a795-db50-482f-9911-301930d1b1be', {\"useNewLoader\":\"true\",\"region\":\"na1\"}); <\/script><\/span><!-- end HubSpot Call-to-Action Code -->\n<\/div><figure class=\"wp-block-media-text__media\"><img fetchpriority=\"high\" decoding=\"async\" width=\"904\" height=\"931\" src=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png\" alt=\"guy server checkup\" class=\"wp-image-12943 size-full\" srcset=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png 904w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-291x300.png 291w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-768x791.png 768w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-585x602.png 585w\" sizes=\"(max-width: 904px) 100vw, 904px\" \/><\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Intermittent timeouts between an AWS Application Load Balancer (ALB) and EC2 instances can be among the most frustrating infrastructure issues to diagnose. Unlike complete outages, these problems occur sporadically, making&hellip;<\/p>\n","protected":false},"author":37,"featured_media":17460,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[69,332],"tags":[],"class_list":["post-17454","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aws","category-troubleshooting"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/17454","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/comments?post=17454"}],"version-history":[{"count":1,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/17454\/revisions"}],"predecessor-version":[{"id":17456,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/17454\/revisions\/17456"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media\/17460"}],"wp:attachment":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media?parent=17454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/categories?post=17454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/tags?post=17454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}