Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Node.js status site doesn't show active Cloudflare incident affecting Node.js downloads

Open
  • Is something wrong?
#9,239 1 comment 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
nextjs, typescript
Domain
backend, observability

Research direction

Start by locating the code that populates the status page’s “Upstream” section and how it selects Cloudflare services or regions. Compare that selection with the active incident linked in the report to find why it is omitted. Done when the Node.js status page reflects relevant active Cloudflare incidents; the payload names no files or tests.

Written by the indexing model from the issue text.

Description

URL:

https://status.nodejs.org/

Browser Name:

Firefox

Browser Version:

N/A

Operating System:

N/A

How to reproduce the issue:
  1. Encounter hundreds of Node.js download failures from https://nodejs.org/download/ due to timeouts and HTTP/2 stream errors when downloading from us-east-1, across multiple hours and EC2 instances. (I'll paste the errors below, but this bug report is more about the broken "Upstream" status section than those.)
  2. Visit https://status.nodejs.org/ expecting to see an incident declared, or something shown under the "Upstream" section on that page such as a Cloudflare incident. But it's all green.
  3. Visit the Cloudflare status page and see there is an active Cloudflare incident after all: https://www.cloudflarestatus.com/incidents/snth5ero95rz

It seems like the "Upstream" section on the Node.js status site might not be correctly showing Cloudflare incidents? Perhaps it's filtered to a too-small subset of the Cloudflare features/regions and so why the active Cloudflare incident didn't show up?

What was shown on the Node.js status site (all green, including the upstream Cloudflare section):

Image

Vs what appeared on Cloudflare's own status page:

Image
Dominant language
TypeScript
Stars
6.9k
Forks
6.5k
Avg merge
2d 1h
Merged PRs (30d)
48

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/nodejs.org

All issues in nodejs/nodejs.org

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.