Incidentsby GlyphBitBucket Cloud Integrations Degraded
Oct 29, 10:44 UTCOct 29, 14:16 UTC
Duration
3h 32m
Impact
Major
Root cause
Not disclosed
Snyk, 90 days
27 incidents
Affected
Snyk CodeSnyk ContainerSnyk IaCSnyk Open SourceSnyk API & WebSnyk SecretsSNYK-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-01 (app.snyk.io) - Snyk SecretsSNYK-US-02 (app.us.snyk.io) - Snyk CodeSNYK-US-02 (app.us.snyk.io) - Snyk ContainerSNYK-US-02 (app.us.snyk.io) - Snyk IaC
Final update
Bitbucket Cloud integrations are working as expected across all Snyk environments, and no further impact has been observed throughout our monitoring period. The Snyk Incident Response has been stood down.
Timeline
- Resolved · Oct 29, 14:16 UTC
Bitbucket Cloud integrations are working as expected across all Snyk environments, and no further impact has been observed throughout our monitoring period. The Snyk Incident Response has been stood down.
- Monitoring · Oct 29, 12:25 UTC
Our Engineers have implemented a fix, and we're observing improvements in success rates. We are now monitoring to ensure services remain stable.
- Investigating · Oct 29, 10:44 UTC
We are investigating degradation affecting Bitbucket Cloud integrations across all Snyk environments. Customers may observe that their Bitbucket Cloud integrations are showing the error 'could not connect'. This will affect all Bitbucket Cloud actions, such as PR Checks, Importing and Recurring Tests, among others. The Snyk Incident Response has been invoked.