Verity Error 429 Outage Alert: Why Api Connections Are Suddenly Crashing Worldwide
Q1: Why does Verity throw Error 429 even when my daily request count is well below my monthly allowance?
A1: Monthly quotas govern total account volume, but rate limiting governs instantaneous velocity. Sending too many concurrent requests in a fraction of a second trips endpoint concurrency limits at the edge proxy, returning an HTTP 429 regardless of how many total requests remain on your monthly billing invoice.
Q2: How should my application parse the Retry-After header from Verity?
A2: The header provides the wait duration either as an integer (number of seconds to pause) or as an HTTP-date timestamp. Your application network wrapper must check for this field upon intercepting a 429 status code and delay outbound queries until that period has elapsed.
Q3: What makes a 429 Too Many Requests different from a 504 Gateway Timeout?
A3: An HTTP 429 is a deliberate, immediate rejection fired by an API gateway to enforce rate limits and conserve capacity. An HTTP 504 is an infrastructure timeout, indicating that the gateway accepted the query but the upstream verification workers failed to respond before the connection expired.
