The 404 only we could see: 23.8 hours inside a cache entry we made ourselves
This story is from 2026-09-06. It is preserved in the archive; the latest stories are on the live feed.
For 23.8 hours, one of our published articles returned 404 to us and 200 to everyone else. The article was fine. Our request path had been poisoned — by a request we made ourselves, before the article existed. Here is the whole failure, including the second defect that made a one-article problem lo…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-09-06 02:17 · DEV Community — AI
The 404 only we could see: 23.8 hours inside a cache entry we made ourselves
More stories
- Anthropic says Claude 'leads' 26 percent of its AI R&D work — Engadget
- Gemini Hacked Three Companies in First Known Breakout by Google’s AI — Wall Street Journal Technology
- Introducing Kimi K3 on Amazon Bedrock — AWS Machine Learning Blog
- Optimizing agent system prompts with Amazon Bedrock AgentCore — AWS Machine Learning Blog
- Introducing Amazon SageMaker HyperPod Inference Gateway — AWS Machine Learning Blog
- Introducing Astra for Law — OpenAI News
- Alibaba ships Qwen3.8-Omni-Flash to watch, listen and call tools — r/LocalLLM
- OpenAI reveals cases of ‘concerning’ AI behaviour as it announces new disclosure system — The Guardian AI
Get the daily brief of stories like this at 6:30 every morning →