Read the failure scope
Rate limits can restrict requests or token use over time. A response may be specific to one account and workload. It is not sufficient evidence that a provider is unavailable to everybody. AI Fast Now keeps quota and rate-limit outcomes separate from provider service failures.
The monitor can be wrong
Expired credentials, missing model permissions, exhausted credits and parser errors can prevent measurement. A monitor that turns every such error into a red provider light confuses its own health with service health. The raw record retains attribution and does not pretend every error has a known cause.
Retain the first attempt
A retry may recover, but first-attempt reliability matters. Record the original result and link later attempts explicitly. Avoid implicit SDK retries during measurement because they can hide latency and failures inside a seemingly successful request. Repeated attempts also consume additional budget.
Draw a narrow conclusion
An isolated quota response means that request was not admitted under the current conditions. Broader incident claims need additional evidence and clear scope. Check account limits and provider guidance before changing cadence. This site does not infer global traffic, internal utilization or consumer app uptime from its own account quota.