On 1 October, Anthropic's console and API both ran into a billing problem that lasted 6 hours and 16 minutes. Credit purchases were not reflected in account balances fast enough, so some requests failed as if the account had no funds. The fault sat on Anthropic's side, in how purchases were processed, not in your integration.
Started
16:20 UTC
Duration
Lasted 6h 16m
Source
IsDown
Next time
Anthropic is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: console.anthropic.com, api.anthropic.com
What happened?
Anthropic's status page shows one incident on 1 October, starting at 16:20 UTC and affecting both console.anthropic.com and api.anthropic.com. The first update describes delays in credit purchases being reflected in account balances, which caused some requests to fail for insufficient credit balance. That is a billing and accounting problem, not a model or network outage, but it has the same effect on your product: calls that should succeed get rejected. At 18:23 UTC, roughly two hours after the first update, Anthropic said the issue causing the credit delays had been resolved and that they were monitoring closely to ensure no further issues. The incident was marked fully resolved at 22:36 UTC, giving a total duration of 6 hours and 16 minutes from first report to close. That is three updates across six hours, which is a thin trail for an incident this long, but it is what Anthropic published. No user reports were filed during the window on this record. Anthropic's own history over the past 90 days shows 86 incidents with a median duration of 1 hour and 9 minutes, so this one ran several times longer than a typical incident for this provider. Across all time, Anthropic has logged 833 incidents on its status page. There is no breakdown of how many accounts were affected or what caused the delay in applying credits, so that detail is not on the record.
Learning
This incident shows how a billing-layer fault can look identical to a credentials or capacity problem from where you sit. A request failing for insufficient balance looks the same to your code whether the account is actually out of credit or whether, as here, a purchase simply hadn't been applied yet. Pinging api.anthropic.com from your own monitoring would most likely have returned a healthy response the whole time, because the endpoint itself was up. The fault was in the accounting pipeline behind it, a layer your uptime checks cannot see because it only shows up when a real purchase and a real request collide. Over the last 30 days UptimeRobot's own checks against Anthropic recorded 12 incidents, all resolved, with a median duration of 1 hour 40 minutes, which gives a independent view of how often this provider has problems regardless of what its own status page says. Your monitoring covers your half, the code, the keys, the requests you send, UptimeRobot now watches the provider's half too, so next time something fails you know which side broke without guessing.
