Skip to content

Incident detail

Unable to perform UI Operations

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Jira breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

  2. Investigating

    Atlassian team is actively investigating the issue with UI based Customer interactions.

    Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures.

    We shall keep you informed of the progress in next 2 hours, if not sooner.

  3. Monitoring

    We have recovered from a issue which saw degraded Automation experience.

    Impact

    Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running.

    Current Status

    The incident has been mitigated and we continue to investigate the cause of this incident

    Next Steps

    We are continuing to monitor the service, and will provide further updates in the next two hours

  4. Resolved

    Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira.

    Impact

    Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.

    Current Status

    The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume.

    Next Steps

    We are conducting a root cause analysis of the internal service. A post incident review will be conducted.

Keep exploring

More from Jira

Neighboring incidents on Jira's timeline and the rest of their record on OutageDeck.