# Deno Deploy: Warm up failures with architecture specific packages

- Impact (vendor’s label): unknown
- Status: resolved
- Started: 2025-10-20 15:00 UTC · Resolved: 2025-10-20 17:24 UTC · Duration: 2.4 h
- Updates: 2 · Affected components: Console
- [Vendor status page: https://denostatus.com/incident/cmgzciul702qqftk46ugywhrm](https://denostatus.com/incident/cmgzciul702qqftk46ugywhrm)
- [Company: Deno Deploy](https://rewindex.com/company/deno-deploy.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 20, 2025: 141 vendors, 181 incidents](https://rewindex.com/events/2025-10-20-aws-us-east-1)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +7 h 49 min vs AWS’s own post)

```mermaid
flowchart LR
  root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Deno Deploy (this incident)<br/>posted +7 h 49 min"]:::me
  root -.->|"same window"| me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **identified** 2025-10-20 15:00 UTC: We are seeing some failures in the &quot;Warmup&quot; step of builds for some projects. The error message is generally along the lines of \`npm package not found in cache, ..., --cached-only is specified.\` Please report any failures you are seeing to us at deploy@deno.com, or on Discord. We have identified the underlying issue and are rolling out a fix shortly..
- **resolved** 2025-10-20 17:24 UTC: This incident has been resolved. If you are still seeing issues, please reach out to \[deploy@deno.com\](mailto:deploy@deno.com) or get help on the Deno Discord..


---
Canonical: https://rewindex.com/company/deno-deploy/incidents/cmgzciul702qqftk46ugywhrm · Markdown: https://rewindex.com/company/deno-deploy/incidents/cmgzciul702qqftk46ugywhrm.md · JSON: https://rewindex.com/api/v1/companies/deno-deploy/incidents/cmgzciul702qqftk46ugywhrm · Generated 2026-10-20T00:07:11.412Z