I am encountering persistent platform-wide errors when trying to generate content or speech in Google AI Studio. The system frequently throws internal error, permission denied, 403 Forbidden, and 401 Unauthorized status codes during audio generation and API calls.
Observed Behaviors:
These issues appear randomly and seem related to platform-wide disruptions rather than project-specific code.
The interface frequently gets stuck in error loops during generation tasks.
Standard API keys fail with authorization and permission blocks despite correct configurations.
Is there an ongoing backend disruption affecting the speech and content generation APIs, or is there a specific project configuration required to bypass these authorization loops
Hi @Mohammed9
Can you share more details about the request
What prompts are you using for which you are encountering these issues ?
Which model are you using ?
Hi @Mustan_lokhand,
Thank you for looking into this! Here are the specific details of what I am experiencing:
Models Used: I primarily encounter this when using the Gemini 3.5 Flash models (experimental and stable versions), especially when experimenting with multimodal and speech capabilities.
Prompts / Use Case: The issue happens across a range of regular prompts—from text-based developer queries and code building requests to testing audio generation features. It is not limited to any specific phrase or safety-triggering prompt.
Failure Modes:
Live/Voice Conversation Interface: When trying to interact via the live audio feature, it fails completely to connect or process speech, throwing internal error loops.
Normal Text Messaging/Prompts: Even standard text messages in the chat interface fail randomly. The UI completely blocks out, presenting 403 Forbidden, 401 Unauthorized, or generic platform permission blocks.
Consistency: The key factor is that these authorization and permission loops trigger on standard, working API keys and accounts without any configuration changes on my end, acting like a backend disruption or project-level auth block.
Let me know if you need any specific correlation IDs or logs from the console when this occurs
Hi
It would be helpful to get some logs as well the all the error message from the api
Can you DM those to me ?
Hi Mustan,
Thank you for offering to take a closer look at this via DM.
Since the errors completely block my interface and break the live session, I pulled the network and console details directly from my browser’s Developer Tools during the failure loop. I am experiencing this primarily on the new Gemini 3.5 Flash model.
Here is what the API responses look like:
1. Live/Voice Chat Endpoint Failure (WebSockets/Streaming)
Model: gemini-3.5-flash (via Live API protocol)
Error Message / Closed Code: The connection terminates abruptly during initialization. The console prints a WebSocket connection handshake failure with an Unexpected response code: 403 or a generic platform Internal Error (500).
Behavior: It completely fails to initialize or stream any audio payload, getting stuck in an infinite reconnection loop.
2. Normal Text Messaging Endpoint Failure (REST)
HTTP Status Codes Encountered: 401 Unauthorized and 403 Forbidden
Response Payload Body