Uptime.com incident
Delayed check execution in New York (NYC) and Los Angeles (LAX)
Resolved after 6 hours 30 minutes, on September 29, 2026.
### Summary On September 29, we moved the NYC and LAX probe locations to our new monitoring platform. During this migration, some checks ran later than their schedule. ### Impact - **HTTP checks:** execution was delayed from 2:15 PM to 3:15 PM UTC (approximately 1 hour). - **Transaction checks:** execution was delayed from 2:15 PM to 9:00 PM UTC (approximately 7 hours). - Only the NYC and LAX locations were affected. All other locations operated normally. - During the delay, alerts and results from these locations could arrive late. ### Cause The new platform had a higher load in these two locations than we expected. Some components did not have sufficient capacity for this load. This caused a queue of checks that were waiting to run. ### Resolution Our engineering team did these steps: - Corrected a flow-control issue in the HTTP check service. - Added more capacity for Transaction checks in both locations. - Increased the capacity of internal supporting services. - Did an inspection of all servers in NYC and LAX. At 3:15 PM UTC, HTTP checks ran on schedule again. At 9:00 PM UTC, Transaction checks ran on schedule again. ### Next steps This was the last large migration to the new platform. Our team now focuses on the stability of the platform. We will also add more monitoring to find delays in check execution earlier. We apologize for this problem. If you have questions, please contact our support team.
Update timeline
- monitoring Sep 29, 2026, 02:30 PM UTC
### Summary On September 29, we moved the NYC and LAX probe locations to our new monitoring platform. During this migration, some checks ran later than their schedule. ### Impact - **HTTP checks:** execution was delayed from 2:15 PM to 3:15 PM UTC (approximately 1 hour). - **Transaction checks:** execution was delayed from 2:15 PM to 9:00 PM UTC (approximately 7 hours). - Only the NYC and LAX locations were affected. All other locations operated normally. - During the delay, alerts and results from these locations could arrive late. ### Cause The new platform had a higher load in these two locations than we expected. Some components did not have sufficient capacity for this load. This caused a queue of checks that were waiting to run. ### Resolution Our engineering team did these steps: - Corrected a flow-control issue in the HTTP check service. - Added more capacity for Transaction checks in both locations. - Increased the capacity of internal supporting services. - Did an inspection of all servers in NYC and LAX. At 3:15 PM UTC, HTTP checks ran on schedule again. At 9:00 PM UTC, Transaction checks ran on schedule again. ### Next steps This was the last large migration to the new platform. Our team now focuses on the stability of the platform. We will also add more monitoring to find delays in check execution earlier. We apologize for this problem. If you have questions, please contact our support team.
Your product runs on more than Uptime.com
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services