Jira Integration Degraded
May 19, 14:19 UTCMay 20, 10:51 UTC
Duration
20h 32m
Impact
Minor
Root cause
Not disclosed
Snyk, 90 days
18 incidents
Affected
Snyk CodeSnyk ContainerSnyk IaCSnyk Open SourceSNYK-US-01 (app.snyk.io) - Snyk CodeSNYK-US-01 (app.snyk.io) - Snyk ContainerSNYK-US-01 (app.snyk.io) - Snyk IaCSNYK-US-01 (app.snyk.io) - Snyk Open SourceSNYK-US-02 (app.us.snyk.io) - Snyk CodeSNYK-US-02 (app.us.snyk.io) - Snyk ContainerSNYK-US-02 (app.us.snyk.io) - Snyk IaCSNYK-US-02 (app.us.snyk.io) - Snyk Open SourceSNYK-EU-01 (app.eu.snyk.io) - Snyk CodeSNYK-EU-01 (app.eu.snyk.io) - Snyk Container
Final update
We are no longer observing any impact affecting Jira integration workflows. The Snyk Incident Response has been stood down.
Timeline
- Resolved · May 20, 10:51 UTC
We are no longer observing any impact affecting Jira integration workflows. The Snyk Incident Response has been stood down.
- Monitoring · May 19, 19:47 UTC
A fix has been deployed to production, and we are monitoring the impacted Jira integration workflows to confirm the issue is fully resolved.
- Identified · May 19, 15:35 UTC
Snyk engineers have identified the root cause of the Jira integration issue and are actively developing a fix.
- Investigating · May 19, 14:19 UTC
We're currently investigating an issue affecting the Jira integration. Users will be unable to manage Jira integrations, view associated Jira tickets on Snyk issues, or create new Jira tickets through the platform. The Snyk Security In Jira Cloud integration is unaffected. The Snyk Incident Response has been invoked.
More from Snyk
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2114:43 UTC | Snyk Code Services Degraded in MT-US-01 | minor | 3h 24m |
| Sep 1806:40 UTC | Snyk Daily Recurring Tests Delayed | minor | 2d 23h |
| Sep 914:37 UTC | Imports and PR Checks Degraded | minor | 2h 25m |
| Aug 3014:32 UTC | Partial Broker Service Degradation | minor | 2d 16h |
| Aug 3012:20 UTC | Partial Broker Service Degradation | minor | 1h 12m |
| Aug 2012:42 UTC | Snyk Code Degradation | none | 0m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.