Signature invalid but bot was working: why clock drift breaks auth suddenly

This post was originally published on MatrixTrak.com — the production reliability toolkit for trading bot operators and .NET engineers.

When bot gets signature invalid or 401 after working fine for hours: why clock drift breaks exchange auth suddenly, and the time calibration that prevents it..

If your bot suddenly starts throwing signature invalid or timestamp out of range, it’s tempting to go hunting for a bug in your signing code.

Sometimes that’s correct.

But in production, a surprisingly large share of “signature bugs” are not code bugs at all. They’re time bugs.