Vendor Status Watch

← all vendors

Readme status history

Current state: operational — “All Systems Operational” per https://www.readmestatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
3incidents, last 90 days
30incidents on record
Incidents per week, last 12 weeks:

How long do Readme incidents last?

2.3 hmedian incident duration30 measured
8.8 h90th percentile1 in 10 ran longer
2.9 hmedian, major/critical only13 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-08 16:04 UTCAdmin interface outageresolvedcritical11 min
2026-08-21 16:36 UTCSlow search within customer hubsresolvedminor1 h 45 min
2026-07-24 12:22 UTCDegraded performance due to third-party infrastructure issuesresolvedminor1 h 15 min
2026-06-17 15:28 UTCAPI Reference Degradationresolvednone2 h 41 min
2026-05-28 13:40 UTCRefactored Hubs Downresolvedmajor4 d 4 h
2026-05-27 13:51 UTCReadMe Refactored Outagepostmortemcritical8 h 46 min
2026-05-26 17:41 UTCSlow performance across customer hubsresolvedmajor10 h 13 min
2026-05-26 13:39 UTCDegraded performance across Admin Hubsresolvedmajor1 h 58 min
2026-05-12 14:15 UTCDegraded performance across Admin Hubsresolvedminor6 h 55 min
2026-05-11 15:43 UTCDegraded performance across Admin Hubsresolvedminor2 h 51 min
2026-05-07 23:43 UTCIssues Creating New Changelogsresolvedcritical3 h 34 min
2026-04-28 18:38 UTCCreating branches is resulting in 500 errorsresolvedminor52 min
2026-04-24 12:17 UTCService disruptionresolvedcritical2 h 53 min
2026-04-22 14:35 UTCAdmin downtimeresolvedmajor2 h 00 min
2026-04-22 02:59 UTCSlow performance, increased 500 errors upon page loadresolvedminor44 min
2026-04-20 20:05 UTCIncreased Admin Response Timesresolvedminor1 h 15 min
2026-04-16 16:07 UTCSlow performance / 500 error pagesresolvedminor3 h 18 min
2026-04-15 17:18 UTCSlow page performanceresolvedminor6 h 15 min
2026-04-08 18:11 UTCDiscussion posts throwing 500 errorsresolvedmajor3 h 35 min
2026-03-31 21:32 UTCReadme high response times.resolvedmajor24 min
2026-03-30 14:53 UTCIssues with saving MDXresolvedminor5 min
2025-12-20 01:40 UTCReadMe Hub Downresolvedminor1 h 23 min
2025-12-05 09:27 UTCDash and Hub Outageresolvedmajor42 min
2025-11-18 13:27 UTCCloudflare outageresolvedmajor1 h 41 min
2025-10-30 15:24 UTCCreating a branch returns a 500 errorresolvednone31 min
2025-09-19 16:31 UTCReadMe docs producing 404 errors after reordering and branch mergeresolvedminor7 h 44 min
2025-09-18 17:14 UTCReadMe editor is unresponsive / blankresolvedmajor3 h 59 min
2025-09-16 13:31 UTCOwlbot AI service outageresolvedminor15 min
2025-09-09 16:47 UTCOwlbot AI service outageresolvedminor46 h 06 min
2025-09-08 17:04 UTCE-mail notifications are not being sentresolvedminor3 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
}