High timeouts can cause resource waste and slow user experience.
Setting HTTP timeouts too high can lead to resource wastage, where threads and connections are held for too long, impacting performance. For instance, if an API request to a shipping service is delayed but the timeout is set for several minutes, the user may experience unnecessary waiting, and the server resources remain occupied, potentially affecting other operations.
Additional Notes
What are the trade-offs of setting HTTP timeouts too high?