Upstream returns empty response

On-call incidentMedium35 min

Your task

Your product page calls an upstream catalog service for pricing and availability. Starting 13:10, customers report pages rendering with blank prices and 'unavailable' badges on items that are in stock. Your service treats this as a soft success, no errors thrown, page still renders. Dashboards: upstream catalog calls return HTTP 200, latency is actually slightly LOWER than normal, your error rate is flat. The upstream team deployed a caching-layer change at 13:05. How do you triage and mitigate, and what would you change in your client?

It covers

  • Empty body
  • 200 ok
  • Content validation