# What broke January 28 to February 3, 2019

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

## Days
- [Mon, Jan 28](https://down.guide/archive/2019-01-28): 0 incidents, 0 major outages
- [Tue, Jan 29](https://down.guide/archive/2019-01-29): 0 incidents, 0 major outages
- [Wed, Jan 30](https://down.guide/archive/2019-01-30): 0 incidents, 0 major outages
- [Thu, Jan 31](https://down.guide/archive/2019-01-31): 1 incident, 0 major outages
- [Fri, Feb 1](https://down.guide/archive/2019-02-01): 0 incidents, 0 major outages
- [Sat, Feb 2](https://down.guide/archive/2019-02-02): 0 incidents, 0 major outages
- [Sun, Feb 3](https://down.guide/archive/2019-02-03): 0 incidents, 0 major outages

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

- **RubyGems.org**: [Unexpected Problem](https://down.guide/DWN-d27f2e8d06) (Partial outage; lasted 33m; started 2019-01-31 10:42 UTC; Application, Dependency API, Gem Index API)

## Other weeks
- [Previous week: Jan 21 to Jan 27, 2019](https://down.guide/archive/2019-W04)
- [Next week: Feb 4 to Feb 10, 2019](https://down.guide/archive/2019-W06)

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