Readme status history
Current state: operational — “All Systems Operational” per https://www.readmestatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Readme incidents last?
From 30 incidents with a vendor-posted start and resolve time. Longest on record: Refactored Hubs Down — 4.2 days (2026-05-28 13:40 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (30)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-08 16:04 UTC | Admin interface outage | resolved | critical | 11 min |
| 2026-08-21 16:36 UTC | Slow search within customer hubs | resolved | minor | 1 h 45 min |
| 2026-07-24 12:22 UTC | Degraded performance due to third-party infrastructure issues | resolved | minor | 1 h 15 min |
| 2026-06-17 15:28 UTC | API Reference Degradation | resolved | none | 2 h 41 min |
| 2026-05-28 13:40 UTC | Refactored Hubs Down | resolved | major | 4 d 4 h |
| 2026-05-27 13:51 UTC | ReadMe Refactored Outage | postmortem | critical | 8 h 46 min |
| 2026-05-26 17:41 UTC | Slow performance across customer hubs | resolved | major | 10 h 13 min |
| 2026-05-26 13:39 UTC | Degraded performance across Admin Hubs | resolved | major | 1 h 58 min |
| 2026-05-12 14:15 UTC | Degraded performance across Admin Hubs | resolved | minor | 6 h 55 min |
| 2026-05-11 15:43 UTC | Degraded performance across Admin Hubs | resolved | minor | 2 h 51 min |
| 2026-05-07 23:43 UTC | Issues Creating New Changelogs | resolved | critical | 3 h 34 min |
| 2026-04-28 18:38 UTC | Creating branches is resulting in 500 errors | resolved | minor | 52 min |
| 2026-04-24 12:17 UTC | Service disruption | resolved | critical | 2 h 53 min |
| 2026-04-22 14:35 UTC | Admin downtime | resolved | major | 2 h 00 min |
| 2026-04-22 02:59 UTC | Slow performance, increased 500 errors upon page load | resolved | minor | 44 min |
| 2026-04-20 20:05 UTC | Increased Admin Response Times | resolved | minor | 1 h 15 min |
| 2026-04-16 16:07 UTC | Slow performance / 500 error pages | resolved | minor | 3 h 18 min |
| 2026-04-15 17:18 UTC | Slow page performance | resolved | minor | 6 h 15 min |
| 2026-04-08 18:11 UTC | Discussion posts throwing 500 errors | resolved | major | 3 h 35 min |
| 2026-03-31 21:32 UTC | Readme high response times. | resolved | major | 24 min |
| 2026-03-30 14:53 UTC | Issues with saving MDX | resolved | minor | 5 min |
| 2025-12-20 01:40 UTC | ReadMe Hub Down | resolved | minor | 1 h 23 min |
| 2025-12-05 09:27 UTC | Dash and Hub Outage | resolved | major | 42 min |
| 2025-11-18 13:27 UTC | Cloudflare outage | resolved | major | 1 h 41 min |
| 2025-10-30 15:24 UTC | Creating a branch returns a 500 error | resolved | none | 31 min |
| 2025-09-19 16:31 UTC | ReadMe docs producing 404 errors after reordering and branch merge | resolved | minor | 7 h 44 min |
| 2025-09-18 17:14 UTC | ReadMe editor is unresponsive / blank | resolved | major | 3 h 59 min |
| 2025-09-16 13:31 UTC | Owlbot AI service outage | resolved | minor | 15 min |
| 2025-09-09 16:47 UTC | Owlbot AI service outage | resolved | minor | 46 h 06 min |
| 2025-09-08 17:04 UTC | E-mail notifications are not being sent | resolved | minor | 3 h 27 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Readme with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"readme"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}