# Timeout on External Services

**URL:** <https://linkerd.buoyant.io/t/timeout-on-external-services/621>\
**Category:** Linkerd General Discussion\
**Tags:** proxy, configuration\
**Created:** [October 17, 2024, 8:41pm UTC](https://linkerd.buoyant.io/t/timeout-on-external-services/621 "2024-10-17T20:41:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![benbpyle](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/benbpyle/32/206_2.png) [@benbpyle](https://linkerd.buoyant.io/u/benbpyle)\
**Post date:** [October 17, 2024, 8:41pm UTC](https://linkerd.buoyant.io/t/timeout-on-external-services/621/1 "2024-10-17T20:41:44Z")

</div>

I’m trying to set a timeout on a Service defined as an ExternalName. I have some outside of my cluster services that I’d like to have Linkerd timeout if the requests run beyond a timeout. Is this possible?

---

<div class="post-metadata">

**Author:** ![william](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/william/32/5_2.png) [@william](https://linkerd.buoyant.io/u/william)\
**Post date:** [November 22, 2024, 5:06pm UTC](https://linkerd.buoyant.io/t/timeout-on-external-services/621/2 "2024-11-22T17:06:32Z")

</div>

I know we answered this on Slack as well, but since those messages disappear:

It is not possible to use timeouts on ExternalNames. For $reasons, Linkerd looks up client-side policy on the resolved IP address, so for ExternalNames that doesn’t work. However, in the upcoming 2.17 release we will add egress support, which I believe will include this functionality, tho not attached to ExternalNames directly.