rewindex

CompaniesJiraIncidents

Jira: 3rd-party apps which integrate with Jira experiencing authentication problems

No impact listedStatus: resolvedStarted Resolved (3.5 h)1 updatejira-software.status.atlassian.com (opens in new tab)

Timeline of updates

  1. resolved

    Between 01:00 Sunday 10th Feb UTC to 08:35 Monday 11th Feb UTC, Jira Cloud was impacted by a change in our 3LO consent flow resulting in users being unable to complete the consent flow. The issue has been resolved and the service is operating normally.

From Jira’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on jira-software.status.atlassian.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Jira, started 2019-02-11 05:53 UTC, resolved after 3.5 h, 1 update(s).

Title
3rd-party apps which integrate with Jira experiencing authentication problems
Vendor
Jira
Date
URL
https://rewindex.com/company/jira/incidents/bdp7ns7jfqw1

Jira profileRecent Jira incidentsAll outages on February 11, 2019Jira in February 2019MarkdownJSON