# What broke June 27 to July 3, 2016

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

## Days
- [Mon, Jun 27](https://down.guide/archive/2016-06-27): 1 incident, 0 major outages
- [Tue, Jun 28](https://down.guide/archive/2016-06-28): 0 incidents, 0 major outages
- [Wed, Jun 29](https://down.guide/archive/2016-06-29): 0 incidents, 0 major outages
- [Thu, Jun 30](https://down.guide/archive/2016-06-30): 0 incidents, 0 major outages
- [Fri, Jul 1](https://down.guide/archive/2016-07-01): 0 incidents, 0 major outages
- [Sat, Jul 2](https://down.guide/archive/2016-07-02): 0 incidents, 0 major outages
- [Sun, Jul 3](https://down.guide/archive/2016-07-03): 0 incidents, 0 major outages

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

- **RubyGems.org**: [Elevated response times](https://down.guide/DWN-86b9002a53) (Degraded; lasted 3h 16m; started 2016-06-27 18:47 UTC)

## Other weeks
- [Previous week: Jun 20 to Jun 26, 2016](https://down.guide/archive/2016-W25)
- [Next week: Jul 4 to Jul 10, 2016](https://down.guide/archive/2016-W27)

---
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-2016-W26), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.