Operational Snyk outage dossier
snyk.io · Official status page (Statuspage-compatible JSON)
Official status now
Operational Operational
checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 24 minor
- 1 none
- 4 major
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 6.9 hPartial Degradation of SCA Test Flows (Multi-tenant US-01)minor resolved · Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted Snyk Open Source Degradednone resolved · official notice ↗ · replay & discuss
- → resolved · lasted 6.7 hSnyk EVO Login Issuesminor resolved · Evo by Snyk, Evo by Snyk · official notice ↗ · replay & discuss
- → resolved · lasted 2.3 hSnyk Open Source Degradedminor resolved · Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 0 minSnyk Open Source and Container Degradationminor resolved · Snyk Container, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 2.7 hSnyk Apps - Degraded Functionality for App Managementminor resolved · official notice ↗ · replay & discuss
- → resolved · lasted 19 minSnyk Services Degradedminor resolved · Snyk Code, Snyk Container, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 14.3 hIntermittent failures for Go-based projectsminor resolved · Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 17.8 hIssue Resolving Entitlementsmajor resolved · Snyk Code, Snyk Code, Snyk Code, Snyk Container · official notice ↗ · replay & discuss
- → resolved · lasted 3.5 hBitBucket Cloud Integrations Degradedmajor resolved · Snyk Code, Snyk Code, Snyk Code, Snyk Code · official notice ↗ · replay & discuss
- → resolved · lasted 2.8 daysSnyk Test Down in SNYK-US-01major resolved · Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 6.1 hSnyk Support portal degradationminor resolved · Support Portal · official notice ↗ · replay & discuss
- → resolved · lasted 3.4 daysSnyk Container Degradation in SNYK-US-01major resolved · Snyk Container · official notice ↗ · replay & discuss
- → resolved · lasted 3 hPR Check Invalid Credential Errorminor resolved · Snyk Code, Snyk Code, Snyk Code, Snyk Code · official notice ↗ · replay & discuss
- → resolved · lasted 2.8 daysSnyk Code Performance Degraded in SNYK-US-02minor resolved · official notice ↗ · replay & discuss
- → resolved · lasted 1.1 hPR Checks and Imports Degraded in SNYK-US-01minor resolved · Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 25.4 hGitLab Cloud Integration Degradedminor resolved · Snyk Code, Snyk Code, Snyk Code, Snyk Code · official notice ↗ · replay & discuss
- → resolved · lasted 21.1 hSnyk Open Source and Container Degradationminor resolved · Snyk Container, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 26.6 hSnyk CLI Tests - 504 Gateway Timeoutsminor resolved · Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 1.1 hSnyk CLI SCA Scans Degraded due to Enrichment of Test Failureminor resolved · Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 22 hSnyk CLI Tests - 504 Gateway Timeoutsminor resolved · Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 4.7 daysIssues API V3 Service - Degradedminor resolved · Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source · official notice ↗ · replay & discuss
- → resolved · lasted 2.9 daysSnyk CLI Scans Degradedminor resolved · Snyk Open Source, Snyk Secrets · official notice ↗ · replay & discuss
- → resolved · lasted 4.4 hSnyk CLI Scans Degradedminor resolved · Snyk Open Source, Snyk Secrets · official notice ↗ · replay & discuss
- → resolved · lasted 3.4 hSnyk Code Services Degraded in MT-US-01minor resolved · Snyk Code · official notice ↗ · replay & discuss
Related services
- OperationalGitHubOperational→
- no official feedGitLabno official feed→
- OperationalBitbucketOperational→
- OperationalnpmOperational→
- OperationalPyPIOperational→
- OperationalDocker HubOperational→
- OperationalCircleCIOperational→
- OperationalTravis CIOperational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.