- Models: GPT Image web and VIP models, plus Nano Banana Pro, Nano Banana 2, and Nano Banana 2.1
- Scope: all keys and token groups combined, not per account
- Times: shown in your browser’s time zone
How to read the board
- Status: based on requests sent roughly 5 to 35 minutes ago. 95% or higher is Normal, 80% to 94% is Degraded, and below 80% is Down. Some requests from the last 5 minutes are still waiting for a result, so they are counted in the next update.
- Last hour: the success rate of requests sent in the hour before that 5-minute cutoff.
- 24-hour bar: one block per hour, colored with the same thresholds. Gray means too few requests that hour to calculate a rate; a dashed outline marks hours before tracking started.
- Below 95%: hours under 95% are listed under each model. Select any block to see that hour’s success rate and its most common errors.
What to do when the rate drops
- Price: the VIP and web route models all cost $0.03 per image, so switching does not change what you pay.
- Token groups: a
defaultgroup key can call both VIP and web route models. AGPT Image VIPgroup key can only call VIP models. - Automatic fallback: for complete code that resends to the web route when VIP fails, see Fall back to the web route when VIP fails.
How rates are calculated
- Success: the request returned HTTP 200.
- Failure: the request returned 429 or a 5xx error such as 500, 502, 503, or 504.
- Not counted: other 4xx errors such as invalid parameters, authentication failures, and moderation rejections, plus requests the client closed before the result arrived. These depend on the request itself and say nothing about whether the model is available.
- One row per product: a product’s release ID and preview ID share a row. For example, the Nano Banana Pro row covers
gemini-3-pro-imageandgemini-3-pro-image-preview.
Get help
- Check your own requests: filter your usage log by model and time to see each request’s result and charge.
- Requests keep failing: note the request ID from the usage log and open a ticket in the console. We check each one.
- Fall back in code: to resend to the web route when VIP fails, see Fall back to the web route when VIP fails. For timeouts, see Request timeouts; for 429 errors and concurrency, see Concurrency and 429.
- Billing questions: see Image API billing and failure rules.
- Incident notices: incidents with a wide impact are posted in Announcements. You can also follow the Telegram channel.
FAQ
Is Nano Banana 2 down right now?
Check the Nano Banana 2 row on this page. A Normal status and green blocks mean requests through LaoZhang API are returning images. Yellow or red means the success rate is dropping, so follow What to do when the rate drops. The row covers bothgemini-3.1-flash-image and gemini-3.1-flash-image-preview; Nano Banana Pro and 2.1 have rows of their own.
Is GPT Image 2 stable right now?
Check the status and last-hour rate in thegpt-image-2-vip row. When VIP is unstable, send 1K and 2K images to gpt-image-2.6-web instead, at the same $0.03 per image. The gpt-image-2.6-web row shows how the web route is doing.
How is this different from the OpenAI or Google status page?
An official status page tells you whether the provider’s own service has an incident. This page measures requests actually sent through LaoZhang API, including our gateway and routes, so the two don’t always move together. To decide whether a model works on LaoZhang API, go by this page and your usage log.Why is my own success rate different from the board?
The board combines every user’s requests. Your own results also depend on your parameters, such as size, quality, reference image size, and concurrency. Filter your usage log by model and time to see each of your requests.My model isn’t on the board. Where do I check it?
The board lists only models with enough steady traffic to calculate a reliable rate. For other models, check your own requests in the usage log. Outages with a wide impact are posted in Announcements.Am I charged for failed requests while the rate is low?
No. Every request the board counts as failed returned 429 or a 5xx error, and requests that get a non-200 response from upstream are not charged. One exception applies to Nano Banana: when Google’s moderation blocks a prompt, it returns HTTP 200, so the request is charged once and counts as a success here. See Image API billing and failure rules for the full rules.The board says Normal but my requests fail. What now?
Check the error code first. 400, 401, 403, and moderation rejections come from the request itself, so fix it according to the error message and send it again. For 429 and 5xx errors, retry after 30–60 seconds. If requests keep failing, find the request ID in your usage log and open a ticket.Related documentation
- GPT Image 2.6 guide: web route, VIP, and official-forwarding parameters, plus fallback code
- Image API billing and failure rules: which failures are charged, timeouts, and retries
- Nano Banana 2.1 guide
- Models and pricing, usage log