Bluesky users blame 'vibe coding' for Monday outage
Get the Tech newsletter
Daily tech — startups, AI labs, chips, the launches that shape the next decade. Free.
- Bluesky experienced intermittent service disruptions on Monday (April 6, 2026), which the platform officially blamed on an "upstream service provider" and which coincided with widespread service problems reported at other popular sites like Google and Spotify.
- Bluesky users filled feeds with hundreds of posts blaming the outage on sloppy AI-assisted "vibe coding" by the development team, with one quoted user writing: "Any developer or programmer using 'vibe-coding' or any reliance on AI to code things is clearly too stupid to know how to do the job they are paid to do and should be fired out of a cannon."
- Bluesky founder and Chief Innovation Officer Jay Graber posted in late March that "Bluesky is made with AI, the engineers and even some non-engineers use Claude Code."
- Bluesky Technical Advisor Jeromy Johnson said in February: "In the past two months Claude has written about 99% of my code. Things are changing. Fast."
- Ars Technica frames the backlash as a cultural fault line: even as professional coders grow increasingly enthusiastic about AI coding tools, many end users remain "reflexively repulsed" by their use and ready to blame them for any tech failure.
Why it matters: Bluesky's leadership has been unusually public about its AI-first development approach, which handed critics a ready-made narrative the moment the platform went down. The episode illustrates a widening trust gap: users increasingly interpret any tech failure as evidence of sloppy AI code, forcing AI-forward companies to choose between touting their tools and managing user hostility.
