CloudFront edge nodes still showing degraded TLS in some geos
AWS CloudFront is experiencing persistent service degradation on specific edge nodes, causing issues for users. The problem is attributed to an "operational issue" from May 15-16, with some CloudFront edge nodes in the 3.168.86.x IP range exhibiting degraded TLS. Local DNS resolvers are reportedly routing traffic to these affected nodes.
Key Takeaways
- Specific CloudFront edge nodes in the 3.168.86.x IP range have degraded TLS.
- AWS described the underlying problem as a multi-service operational issue from May 15-16.
- Local DNS resolvers are reportedly routing traffic to broken edge nodes.
- The degradation is still affecting specific edges in some geographies today.
Why It Matters
This is a live delivery-path problem, not a generic cloud outage note: some CloudFront users are still hitting edge nodes with degraded TLS, which can interfere with content delivery and connection setup. The issue is tied to specific nodes rather than the full CloudFront service, so the blast radius appears narrower but still operationally real. For streaming teams, the key dependency is the DNS-to-edge path. Watch for AWS to identify the affected edge nodes or for reports that local resolvers stop sending traffic to the 3.168.86.x range.
Read full article at twitter.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source