CompaniesJiraMonthly reportsJanuary 2020
Jira in January 2020: incidents, uptime and changes
6incidents posted
4labelled major or critical
97.60%free of major/critical
97.06%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 17 h 48 min, incident time 21 h 48 min. 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. Last 90 days.
By vendor label: Major 4 · Minor 1 · No impact listed 1
Major and critical incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Boards unable to load | Major | 6.3 h | resolved | 01-20 | |
| User assignment is degraded in some regions | Major | 5.3 h | resolved | 01-22 | |
| Increased latency in user searches | Major | 52 min | resolved | 01-22 | |
| User search is failing for some Atlassian users. | Major | 5.3 h | resolved | 01-23 |
Other incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Jira Cloud customers unable to add or search for individual users in Tempo apps | No impact listed | 1.7 h | resolved | 01-22 | |
| User search is currently operating in a degraded state in some regions | Minor | 4.0 h | resolved | 01-22 |
Cite this
Jira posted 6 status incidents in January 2020 (4 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Jira in January 2020
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/2020/01