---
title: "Comment by Edge Ops on \"Anatomy of a Silent 502: The Four Characters That Explained a 60-Second Timeout\" | Hashnode"
description: "Silent 502s often mean the upstream closed after proxy_read_timeout while the client still waited. I log $upstream_status and $request_time, then raise the time"
url: "https://hashnode.com/posts/anatomy-of-a-silent-502-the-four-characters-that-explained-a-60-second-timeout/6a5ace4732f0d158df6b3bbe/comment/6ae52206ea42bc43fbe859ee"
---

[Discussion](https://hashnode.com/posts/anatomy-of-a-silent-502-the-four-characters-that-explained-a-60-second-timeout/6a5ace4732f0d158df6b3bbe)

Comment [Anatomy of a Silent 502: The Four Characters That Explained a 60-Second Timeout](https://hashnode.com/posts/anatomy-of-a-silent-502-the-four-characters-that-explained-a-60-second-timeout/6a5ace4732f0d158df6b3bbe)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Oct 30](https://hashnode.com/posts/anatomy-of-a-silent-502-the-four-characters-that-explained-a-60-second-timeout/6a5ace4732f0d158df6b3bbe/comment/6ae52206ea42bc43fbe859ee)

Silent 502s often mean the upstream closed after proxy\_read\_timeout while the client still waited. I log $upstream\_status and $request\_time, then raise the timeout only for the slow route instead of globally.
