- Newest
- Most votes
- Most comments
The performance degradation you're experiencing on your Lightsail instance in the Tokyo region during peak hours is likely related to the burstable performance model that Lightsail uses.
Lightsail instances operate with a baseline CPU performance and can burst above that baseline for limited periods. Your instance has both a sustainable zone and a burstable zone for CPU utilization. When your instance operates in the burstable zone (consuming more CPU cycles than the baseline allows), it depletes its burst capacity. Once these burst credits are exhausted, performance drops to the baseline level, which can cause significant slowdowns.
The timing pattern you've observed (poor performance during peak hours and recovery late at night) suggests that:
-
During peak hours (20:00-23:00 JST), your instance may be consuming more resources due to higher traffic or workload, depleting its burst capacity.
-
During off-peak hours (after 01:00-02:00 JST), the lower demand allows your instance to recover its burst capacity, resulting in better performance.
The dramatic difference in download speeds (1.65 Mbps vs. 241 Mbps) is consistent with what happens when an instance exhausts its burst capacity and falls back to baseline performance.
Regarding your specific questions:
-
While there isn't specific information about known peak-hour network congestion in ap-northeast-1, the pattern you're seeing is more consistent with burst capacity depletion than regional network issues, especially since your upload speeds remain relatively high.
-
Yes, burstable instance types can experience significant performance degradation during periods of high usage when they exhaust their burst credits.
To address this issue, you could:
- Upgrade to a larger Lightsail plan with higher baseline performance and more burst capacity
- Optimize your application to reduce resource consumption
- Monitor your CPU utilization and burst capacity using Lightsail's monitoring tools
- Consider scheduling resource-intensive tasks during off-peak hours
- If consistent high performance is required, you might want to consider migrating to EC2 which offers more predictable performance options
If the issue persists after trying these solutions, it would be worth contacting AWS Support for more detailed investigation.
Sources
Identify when your Lightsail instance bursts - Amazon Lightsail
My website hosted on Lightsail goes offline at different times every day. | AWS re:Post
My LightSail Bitnami LAMP is too slow and at times unresponsive | AWS re:Post
Relevant content
- asked 6 years ago
- asked 6 years ago
- AWS OFFICIALUpdated 2 years ago

However, I would like to provide some additional information that may help pinpoint the issue more accurately. My instance runs no CPU-intensive workloads at all: It is only used for a simple proxy service CPU utilization is consistently very low Given that CPU usage remains low and burst credits should therefore not be significantly depleted (the baseline CPU should be more than sufficient), I am still seeing severe download speed drops to ~1.65 Mbps during peak hours (20:00–23:00 JST), with full recovery to 241 Mbps after ~02:00 JST. Additional observations: Upload speeds remain relatively high (~59 Mbps) even during peak hours. The test server is also in the Tokyo region (IPA CyberLab 400G, Amazon-hosted), so the path is entirely local. Since burst credits are not being meaningfully consumed, could this still be caused by the burstable model? Or might it be related to other factors, such as: Shared network egress congestion in the Tokyo region (ap-northeast-1) during peak hours Bandwidth allocation policies for Lightsail instances Potential throttling of network traffic during high regional demand I would greatly appreciate a deeper investigation.