Many third-party API outages are announced months in advance. A payment gateway emailed a deprecation notice to an address nobody reads, a courier API started returning a Sunset header that no code looked at, an OAuth provider retired a scope on a date sitting in a changelog. The fix is not vigilance. It is plumbing: detect deprecation signals in code, record every external dependency with its version and owner, and test against the next version before the old one disappears.
I run Loop Origin , a software company that builds and maintains custom web applications, and post-launch maintenance is where this problem lives. I wrote this with help from AI tools and checked every command and claim myself.…