---
title: "Discussion on \"When TLS 1.3-only broke everything behind Akamai\" | Hashnode"
description: "Discussion on \"When TLS 1.3-only broke everything behind Akamai\". The alert wasn't subtle. Requests just stopped hitting our backend nginx box. Internal traffic from our own domains kept flowing, but anything coming in through Akamai-hosted domains — routed via the"
url: "https://hashnode.com/posts/when-tls-1-3-only-broke-everything-behind-akamai/6a4a052ae542a2412b8b46e7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [When TLS 1.3-only broke everything behind Akamai](https://mriduliti.hashnode.dev/when-tls-1-3-only-broke-everything-behind-akamai?utm_source=hashnode&utm_medium=feed)

The alert wasn't subtle. Requests just stopped hitting our backend nginx box. Internal traffic from our own domains kept flowing, but anything coming in through Akamai-hosted domains — routed via the

Jul 5 · 3 min read · mriduliti.hashnode.dev  
Updated Jul 11  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#tls](https://hashnode.com/tag/tls)
-   [#akamai](https://hashnode.com/tag/akamai)

## Written by

[MRIDUL TIWARI](https://hashnode.com/@MridulTi)

@MridulTi

  
[View profile](https://hashnode.com/@MridulTi)

Learning in public

DevOps Engineer | Delivering Scalable, Reliable Systems | Background in Full-Stack Development (React, Next.js, Node.js, Flask, Django)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.