Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#9,239 1 comentário 2 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
56/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
nextjs, typescript
Domínio
backend, observability

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
TypeScript
Estrelas
6.9k
Forks
6.5k
Merge médio
2d 1h
PRs com merge (30d)
48

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nodejs/nodejs.org

Todas as issues de nodejs/nodejs.org

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.