rewindex

CompaniesGitHub CopilotUptime

GitHub Copilot uptime

From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.

97.38%free of major or critical incidents, last 30 days
97.18%free of major or critical incidents, last 90 days
92.42%free of any incident, last 90 days
58incidents started, last 90 days

Last 90 days, by UTC day

Aug 7 (UTC day): 2 h 5 min with a major or critical incident open, 2 h 5 min with any incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): 0 min with a major or critical incident open, 2 h 8 min with any incident open, 2 incidents startedAug 11 (UTC day): 0 min with a major or critical incident open, 5 h 16 min with any incident open, 1 incident startedAug 12 (UTC day): 1 h 18 min with a major or critical incident open, 1 h 43 min with any incident open, 2 incidents startedAug 13 (UTC day): 0 min with a major or critical incident open, 3 h 10 min with any incident open, 3 incidents startedAug 14 (UTC day): no vendor-reported incident openAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): 7 h 36 min with a major or critical incident open, 7 h 36 min with any incident open, 1 incident startedAug 18 (UTC day): 47 min with a major or critical incident open, 4 h 2 min with any incident open, 2 incidents startedAug 19 (UTC day): no vendor-reported incident openAug 20 (UTC day): 9 h 17 min with a major or critical incident open, 9 h 17 min with any incident open, 1 incident startedAug 21 (UTC day): 37 min with a major or critical incident open, 37 min with any incident openAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): 47 min with a major or critical incident open, 1 h 24 min with any incident open, 2 incidents startedAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): 2 h 50 min with a major or critical incident open, 3 h 56 min with any incident open, 4 incidents startedAug 27 (UTC day): 2 h 8 min with a major or critical incident open, 19 h 44 min with any incident open, 1 incident startedAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): 0 min with a major or critical incident open, 42 min with any incident open, 1 incident startedSep 1 (UTC day): 0 min with a major or critical incident open, 1 h 1 min with any incident open, 1 incident startedSep 2 (UTC day): no vendor-reported incident openSep 3 (UTC day): 0 min with a major or critical incident open, 2 h 54 min with any incident open, 1 incident startedSep 4 (UTC day): 1 h 48 min with a major or critical incident open, 1 h 48 min with any incident open, 2 incidents startedSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): no vendor-reported incident openSep 9 (UTC day): no vendor-reported incident openSep 10 (UTC day): no vendor-reported incident openSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): 1 h 29 min with a major or critical incident open, 1 h 29 min with any incident open, 1 incident startedSep 14 (UTC day): 0 min with a major or critical incident open, 55 min with any incident open, 1 incident startedSep 15 (UTC day): 0 min with a major or critical incident open, 2 h 19 min with any incident open, 2 incidents startedSep 16 (UTC day): 10 h 28 min with a major or critical incident open, 10 h 28 min with any incident open, 1 incident startedSep 17 (UTC day): 0 min with a major or critical incident open, 50 min with any incident open, 1 incident startedSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): 0 min with a major or critical incident open, 1 h 9 min with any incident open, 1 incident startedSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): 0 min with a major or critical incident open, 13 h 49 min with any incident open, 1 incident startedSep 24 (UTC day): 0 min with a major or critical incident open, 8 h 45 min with any incident open, 1 incident startedSep 25 (UTC day): no vendor-reported incident openSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): 52 min with a major or critical incident open, 52 min with any incident open, 1 incident startedSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): 0 min with a major or critical incident open, 3 h 30 min with any incident open, 2 incidents startedOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): 3 h 50 min with a major or critical incident open, 3 h 50 min with any incident open, 2 incidents startedOct 6 (UTC day): 5 h 16 min with a major or critical incident open, 5 h 16 min with any incident open, 1 incident startedOct 7 (UTC day): 48 min with a major or critical incident open, 48 min with any incident open, 1 incident startedOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): 0 min with a major or critical incident open, 7 h 54 min with any incident open, 1 incident startedOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): 0 min with a major or critical incident open, 24 min with any incident open, 1 incident startedOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): 1 h 8 min with a major or critical incident open, 1 h 8 min with any incident open, 1 incident startedOct 20 (UTC day): no vendor-reported incident openOct 21 (UTC day): 4 h 30 min with a major or critical incident open, 4 h 30 min with any incident open, 1 incident startedOct 22 (UTC day): 0 min with a major or critical incident open, 9 h 31 min with any incident open, 2 incidents startedOct 23 (UTC day): 0 min with a major or critical incident open, 7 h 13 min with any incident open, 3 incidents startedOct 24 (UTC day): 0 min with a major or critical incident open, 24 min with any incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): 0 min with a major or critical incident open, 6 min with any incident open, 1 incident startedOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): 1 h 15 min with a major or critical incident open, 1 h 15 min with any incident open, 1 incident startedOct 29 (UTC day): 0 min with a major or critical incident open, 2 h 28 min with any incident open, 1 incident startedOct 30 (UTC day): 2 h 4 min with a major or critical incident open, 4 h 33 min with any incident open, 3 incidents startedOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): 0 min with a major or critical incident open, 38 min with any incident open, 1 incident startedNov 3 (UTC day): 0 min with a major or critical incident open, 2 h 15 min with any incident open, 2 incidents startedNov 4 (UTC day): no vendor-reported incident open

Aug 7today

no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive

Last 7 days, by hour

now

Numbers

WindowFree of major/criticalFree of any incidentOutage timeIncident timeIncidents
Last 30 days97.38%92.74%18 h 51 min2.2 days22
Last 90 days97.18%92.42%2.5 days6.8 days58

This is what GitHub Copilot itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .

See the incidents: GitHub Copilot status history · last 90 days · GitHub Copilot status page (opens in new tab) · Markdown