DuckDuckGo was down

Original Article ↗ Hacker News Discussion ↗

An extended outage at DuckDuckGo exposed how heavily it and many “alternative” search engines depend on Microsoft’s Bing, which was experiencing its own problems at the same time. Commenters report widespread search failures across DDG, Ecosia, Qwant and others, note the lack of clear status communication, and question how “independent” or privacy-preserving DDG can be while relying on Bing’s infrastructure and ads. The incident prompts a broader look at search-engine centralization, with some users experimenting with more independent options like Brave Search, Kagi and Mojeek, and debating the trade-offs between privacy, reliability and cost.

Outage symptoms and scope

  • Many users report DuckDuckGo (DDG) loading but failing to show web results, with generic error messages.
  • Bing.com shows its own outage message in many regions; Ecosia, Qwant, and some Startpage functionality are also affected.
  • Some report partial/intermittent functionality or regional differences (works for some, down or sluggish for others).
  • DDG’s HTML/non-JS interface and most !bang redirects continue to work, since they just forward queries elsewhere.
  • Later in the thread, people note that Bing recovers first; DDG takes significantly longer but eventually comes back.

Bing dependency and “wrapper” search engines

  • Multiple commenters connect the dots: any engine relying on Bing’s API (DDG, Ecosia, Qwant, many niche engines, some image search) breaks when Bing does.
  • DDG’s own docs are cited: traditional links and images are “largely sourced from Bing”, with DDG adding ranking, instant answers, and UI.
  • The outage is viewed as a live demonstration of how many “alternative” engines are effectively Bing frontends.

Perceptions of DuckDuckGo’s independence and privacy

  • Some express surprise or disappointment, feeling DDG’s marketing overstates independence; others note DDG has long acknowledged using Bing heavily.
  • Criticism includes: hosting on Azure, using Microsoft/Yahoo ad infrastructure, Amazon affiliate links, and a past incident where its browser exempted some Microsoft trackers.
  • Others argue DDG still adds value as a privacy-ish proxy and via features (bangs, cleaner UI), and that many sites track users regardless of search engine.

Alternative search engines and indexes

  • Frequently recommended: Kagi (paid, uses multiple sources including independent indexes), Brave Search (claims fully independent index), Mojeek (independent index), Searx/SearxNG, Metager, Marginalia, Yep, Yandex, you.com, Startpage (Google-backed), and Google with special parameters.
  • Debate over paying for search: some find Kagi/Brave worth it for quality and low spam; others reject subscriptions or dislike tying searches to accounts/PII.
  • Clarifications: many engines blend own indexes with Google/Bing APIs; full independence is rare and often partial or evolving.

Centralization, resilience, and distributed-systems talk

  • The outage is used as an example of systemic fragility when a few providers (Bing, Google, Cloudflare, large clouds) underpin much of the web.
  • Extended discussion on whether distributed systems are “naturally” more resilient, the role of redundancy vs coupling, and the value of technological diversity vs monoculture.

User experience: bangs, configuration, and search quality

  • DDG’s !bang system receives strong praise; some note browsers can implement similar keyword searches, but bangs are preconfigured, portable, and proxied.
  • Several report declining DDG/Bing quality, especially for technical or niche topics, and prefer Kagi, Brave, or others that surface blogs/forums/“small web”.
  • Some share Firefox tips for adding custom engines and note that DDG’s outage pushed them to experiment with new defaults.

Communication and status transparency

  • Users complain that Bing, DDG, Ecosia, and others lack clear status pages and were slow or vague in acknowledging the issue, often via Reddit/X posts rather than dedicated status sites.
  • Some speculate providers may be reluctant or contractually constrained to name Bing as the underlying cause; this remains unclear.