Ask HN: Is ChatGPT down?

Hacker News Discussion ↗

Outage reports and scope

  • Many commenters report ChatGPT being down across web, desktop, and mobile for about an hour or more.
  • UI partially loads for some, but histories and responses fail.
  • Downdetector and similar services show spikes for OpenAI and other services.
  • Some note the OpenAI status page initially showed all green, later updated to acknowledge a major outage caused by an “upstream provider.”

Status pages, SLAs, and incentives

  • Strong skepticism about official status pages: often slow to reflect reality, sometimes technically inaccessible during outages.
  • Discussion that updating a status page can have contractual/SLA implications, creating incentives to delay acknowledging issues.
  • SLAs mainly refund service fees, not business losses; several point out the mismatch between tiny credits and potentially huge downtime impact.
  • Some argue this is standard for commodity services; real compensation requires expensive, negotiated contracts.

Azure / infrastructure incident

  • Multiple users observe concurrent issues on Azure, Microsoft 365, Xbox Live, and large retailers, suggesting an Azure-related problem.
  • Later, Azure’s status page cites a “power incident” in a South Central US availability zone, impacting multiple services, including OpenAI.
  • Commenters debate how power failures happen despite redundancy, sharing anecdotes of failed generators, transfer switches, flooding, fires, and maintenance lapses.
  • Language like “may experience a degraded experience” is criticized as evasive corporate/legalese.

Monitoring tools and early-warning services

  • A status-aggregation service (StatusGator) is mentioned as detecting outages minutes before official acknowledgments from OpenAI, AWS, and Azure.
  • One user describes a slightly confusing email/onboarding flow with that service.

Alternatives and over-reliance on LLMs

  • Several people temporarily switch to other models: Claude, Google Gemini, Grok 2, local models via Ollama (e.g., mistral-nemo), or API-based usage that remains functional.
  • Mixed views on Grok and Gemini: some praise capability, others worry about provider bias or ethics.
  • A few emphasize not putting “all eggs in one basket” and keeping multiple AI options.
  • Others question how developers now feel unable to work without ChatGPT, contrasting this with older workflows based on docs and Stack Overflow.
  • Some warn that heavy reliance on LLMs may erode foundational understanding; others argue it’s just another productivity tool if you can spot and correct hallucinations.

ChatGPT Pro / higher tiers

  • One detailed account argues the $200/month “Pro-Mode” is worth it for:
    • Much larger context window (e.g., 128K vs ~32K),
    • Fewer prompt limits,
    • Better handling of complex, multi-file firmware and hardware contexts.
  • Example: using Pro-Mode to analyze datasheets and code to diagnose power-draw issues, dramatically improving battery life of a product.
  • Others ask how context is practically uploaded (code, datasheets, etc.) and compare with Google’s large-context models.
  • Some skepticism remains about how well long-context models truly “use” very large inputs.

Cultural and ethical side-discussions

  • Debate over which AI providers are more “biased” or ethical (e.g., Musk’s products vs Google), including concerns about ideology in training data and corporate behavior.
  • Reflections on corporate language around outages and layoffs as shifting responsibility away from decision-makers.
  • Light humor about outages marking the end of the workday and the modern equivalent of “is the Wi-Fi down?”