Git Integration for Jira incident

Integrations are not indexed or some repositories may appear missing

Major Resolved View vendor source →

Git Integration for Jira experienced a major incident on January 29, 2024 affecting Git Integration for Jira Cloud - Global Region, lasting 17d 1h. The incident has been resolved; the full update timeline is below.

Started
Jan 29, 2024, 03:06 PM UTC
Resolved
Feb 15, 2024, 04:06 PM UTC
Duration
17d 1h
Detected by Pingoru
Jan 29, 2024, 03:06 PM UTC

Affected components

Git Integration for Jira Cloud - Global Region

Update timeline

  1. identified Jan 29, 2024, 03:06 PM UTC

    Only for the Global region, some integrations are reporting indexing issues or repositories may appear missing. This affects specific accounts, it is not a generalized issue. The team is working on a fix and will update here as progress is made. We do expect that for some customers this incident will take up to 2 days to resolve.

  2. identified Jan 31, 2024, 12:01 AM UTC

    Our technical team discovered corrupted files in a number of customer integrations. These files are limited to information about integrations and repositories -- no customer data was lost. While our team is still investigating the root cause behind the corrupted files, they've also identified a path for recovering files from backups. This work is expected to continue through Monday, Feb. 5 before it's fully complete. If you need a resolution earlier than that, please open a ticket with our support team and they will provide specific instructions for manually restoring your integrations: https://help.gitkraken.com/git-integration-for-jira-cloud/gij-cloud-contact-support/

  3. monitoring Feb 02, 2024, 03:03 PM UTC

    We've restored the majority of the affected files for customers and now indexing should proceed as normal for those customers.

  4. monitoring Feb 15, 2024, 04:05 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 15, 2024, 04:06 PM UTC

    The incident has been resolved and all affected customers have been contacted by our team.