# What broke July 12 to July 18, 2004

- Incidents: 0; major outages: 0
- Downtime: 0m across providers

## Days
- [Mon, Jul 12](https://down.guide/archive/2004-07-12): 0 incidents, 0 major outages
- [Tue, Jul 13](https://down.guide/archive/2004-07-13): 0 incidents, 0 major outages
- [Wed, Jul 14](https://down.guide/archive/2004-07-14): 0 incidents, 0 major outages
- [Thu, Jul 15](https://down.guide/archive/2004-07-15): 0 incidents, 0 major outages
- [Fri, Jul 16](https://down.guide/archive/2004-07-16): 0 incidents, 0 major outages
- [Sat, Jul 17](https://down.guide/archive/2004-07-17): 0 incidents, 0 major outages
- [Sun, Jul 18](https://down.guide/archive/2004-07-18): 0 incidents, 0 major outages

## The Down Index
[The full table](https://down.guide/rankings/index/2004-W29), worst first.

_Nothing scored yet._

## Other weeks
- [Previous week: Jul 5 to Jul 11, 2004](https://down.guide/archive/2004-W28)
- [Next week: Jul 19 to Jul 25, 2004](https://down.guide/archive/2004-W30)

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=recap-2004-W29), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
