Skip to main content
Opsgenie

Reported issues with OEC functionality

Partial outage Lasted 59m · started · Opsgenie's page

Level
confirmed
Worst impact
Partial outage
Components
Outgoing Integration Flow, Outgoing Integration Flow
Down Index
28of 100

What to do

  • Check whether you use Opsgenie Outgoing Integration Flow, Outgoing Integration Flow. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 59m it lasted.

    Anything that failed between 2024-09-24 19:55 UTC and 2024-09-24 20:54 UTC may need a replay.
  • Subscribe to Opsgenie's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=opsgenie works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Opsgenie 5

  1. investigating

    We've been notified that a number of OEC clients have been failing to create Jira tickets. We're currently investigating the issue.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

    We've identified a recent change that has broken some endpoint routing configurations and caused OEC endpoint requests to be directed to wrong service. We're reverting that change on production at the moment.

    provider

  4. monitoring

    We reverted the faulty routing configuration change and started getting traffic on OEC endpoints

    provider

  5. resolved

    We've verified that OEC endpoints are back online.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-704682ce63

Is Opsgenie still down?

No, this incident was resolved 2024-09-24 20:54 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.

How long did it last?

59m, from 2024-09-24 19:55 UTC to 2024-09-24 20:54 UTC, by the times Opsgenie posted.

What was affected?

Opsgenie named Outgoing Integration Flow, Outgoing Integration Flow.

What caused it?

Opsgenie hasn't published a root cause. If it does, it shows here.

Where does this come from?

Opsgenie's official status page, https://opsgenie.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.