Google Antigravity outage history

Google Antigravity users worldwide faced a disruptive outage as AI model services became unavailable and performance degraded. It appears the impact began around 5:15 PM UTC and intensified through 6:15 PM UTC, with a surge of reports describing slow responses, failures, and unresponsiveness. The Gemini models, including gemini-3.8-flash-medium, were repeatedly cited in complaints across regions.

StatusGator issued an Early Warning Signal at 6:23 PM UTC for model unavailability and high traffic, ending at 7:45 PM UTC. Even without an official public status page, users experienced widespread issues such as invalid model responses and internal errors (500) as the service struggled under load. The incident persisted for roughly two and a half hours, with impact continuing through the late evening as reports continued to surface.

Geographically, the disruption appeared across multiple regions including Europe, North America, the Middle East, and parts of Asia and Africa, indicating a global impact on AI model usage and related tasks.

Users experienced slow or failed responses from the Google Antigravity model service, with some requests not loading and others returning repetitive answers. Reports came from multiple regions, including Ho Chi Minh City, Istanbul, and Antwerp, clustering around 2:30 PM UTC. The issue began at 2:45 PM UTC and was resolved by 3:28 PM UTC. The model endpoint experienced degraded performance, affecting interactive prompts and generation results.

StatusGator detected the degradation ahead of any provider notice. An Early Warning Signal indicated slow or failed responses, giving users advance awareness before official updates. Google Antigravity has no official status page, and the incident noticeably affected user experience for about 44 minutes before resolution.

Users worldwide experienced degraded performance on Google Antigravity, including sign-in problems, slow responses, and agent execution errors. The incident appears to have begun in the early morning UTC, with initial user reports around 5:30 AM UTC. StatusGator detected an Early Warning Signal at 6:39 AM UTC describing agent execution errors and service interruptions. Access to Gemini models was affected, with reports that users could only access lower model versions or faced frequent retries. The disruption persisted for most of the morning, with the Early Warning window ending at 9:43 AM UTC and continued user reports through the late morning.

Users around the world experienced degraded performance on Google Antigravity starting in the early afternoon, with symptoms including failure to load past chats, license checks prompting errors (e.g., license required err 3501 for free tier accounts), and failed data fetches. Reports intensified through the afternoon, with several users noting issues around 2:45 PM UTC and continuing later into the day, indicating a broad impact across regions.

Google Antigravity experienced a global disruption that affected authentication and AI agent access. Users reported repeated login failures, verification-required prompts, and account setup problems, with several notes of model and browser automation services being unavailable. The incident appeared to start around 4:30 PM UTC and escalated through the evening, with activity concentrated in the 18:00–19:00 UTC window and continuing until around 7:30 PM UTC. Symptoms spanned multiple regions, including places like Pakistan, the United Kingdom, the United States, Bangladesh, Egypt, Italy, and Vietnam, indicating a widespread impact.

Users worldwide encountered verification required errors when trying to access Google Antigravity, causing sign-in and chat features to be intermittently unavailable. The disruption began at 12:02 PM UTC and persisted for about an hour, affecting authentication flows and initial user interactions.

StatusGator detected the issue at 12:02 PM UTC, ahead of any provider acknowledgment. There were no public status updates from Google Antigravity since the service does not maintain a public status page, and the window of verification problems appears to have closed by 1:17 PM UTC.

Users of Google Antigravity faced verification errors when attempting to access the service, leading to authentication-related issues for a portion of users. The incident appeared to begin around 4:00 AM UTC as reports of verification failures increased, with spikes in reported problems through the morning. StatusGator logged an Early Warning Signal at 5:01 AM UTC indicating errors during access, and the signal remained in effect until 5:35 AM UTC. A report from Banda Aceh noted a 403 error around 5:35 AM UTC, illustrating the type of access disruption some users experienced. Since Google Antigravity does not publish a public status page, there were no official updates from the provider during the event, and reports began to taper off after the early morning window.

From 2:37 PM UTC to 4:09 PM UTC, Google Antigravity experienced degraded performance with slow responses and intermittent eligibility-check errors. Users in multiple regions reported backend issues and difficulty using features like eligibility checks and the Antigravity IDE, indicating a broad impact beyond a single user or region.

StatusGator detected the issue via an Early Warning Signal at 2:37 PM UTC, and there were no public updates from Google Antigravity during the window. By 4:09 PM UTC performance appeared to improve as the incident was resolved.

Users worldwide reported Gemini models were not responding or performing slowly, affecting chat, coding, and other AI-assisted features. The incident began to surface in user reports around 9:30 AM UTC and grew more pronounced as more users joined in. StatusGator detected an Early Warning Signal at 10:21 AM UTC describing Gemini models not responding or experiencing slow performance, signaling a broader service disruption.

Google Antigravity does not maintain an official status page, so formal updates were not published. As a result, the situation was inferred from user observations and the early warning signal. Many users in India, Europe, and North America reported extremely slow responses, with some devices stuck on loading screens or conversations failing to progress. The activity expanded through late morning, peaking between 10:45 AM UTC and 11:30 AM UTC, and the early warning signal concluded at 12:36 PM UTC, suggesting the issue was gradually improving thereafter.

Impact appeared broad but with a notable concentration in India, with other regions reporting degraded performance or intermittent outages across multiple Gemini-powered features. Overall, the incident caused noticeable disruption to workflows relying on Google Antigravity AI models for chat, coding assistance, and IDE tasks, lasting most of the late morning into early afternoon.

Users across multiple regions reported slow performance and some AI models unavailable starting around 6:30 AM UTC. The issue persisted into the morning, with observations from Hyderabad, Hong Kong, Poissy, Pune, Ahmedabad, and Dubai describing slow responses and inaccessible models. StatusGator issued an Early Warning Signal at 7:27 AM UTC based on ongoing user reports, with the signal ending at 8:20 AM UTC.

Google Antigravity had no official status page updates during the incident. The impact was characterized by degraded performance and partial outages affecting model access, impacting workflows that rely on the platform. Reports spanned regions including India, France, Hong Kong, and the United Arab Emirates, indicating a broadly distributed issue rather than a single locale. The situation appeared to stabilize after the Early Warning Signal period, with user reports tapering off and conditions improving around 8:20 AM UTC.