Vendor Status Watch

← all vendors

Rubrik status history

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

0incidents, last 30 days
1incidents, last 90 days
6incidents on record
Incidents per week, last 12 weeks:
Get Rubrik alerts in your Slack — free templateRSS for Rubrik

How long do Rubrik incidents last?

73 minmedian incident duration6 measured
84 min90th percentile1 in 10 ran longer
72 minmedian, major/critical only1 incident

From 6 incidents with a vendor-posted start and resolve time. Longest on record: Error Accessing RSC UI — 45.1 h (2026-08-06 13:51 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 (6)

StartedIncidentStatusImpactDuration
2026-08-06 13:51 UTCError Accessing RSC UIresolvedminor45 h 05 min
2026-02-27 23:09 UTCError Accessing RSC UIresolvedminor1 h 24 min
2025-11-30 22:23 UTCRSC Degraded Availabilityresolvedminor1 h 15 min
2025-11-19 09:49 UTCError Accessing RSC UIresolvedminor1 h 00 min
2025-10-20 09:48 UTCCloud Native Protection for AWS Experiencing Degraded Availabilityresolvedmajor1 h 12 min
2025-09-30 15:28 UTCError Accessing RSC UIresolvedminor1 h 08 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 Rubrik with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "rubrik"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}