1 person reported

All time, since Sep 2.

Edge node returns invalid TLS

“Request: Could someone on the edge network/infrastructure team check the TLS termination health for nodes in these ranges, specifically 64.29.17.1?”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/vercel/issues/8994/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 1 a week at the early-September peak.

Edge node returns invalid TLS for custom domain. From one network the domain reaches edge IP 64.29.17.1, which fails TLS; another network reaches a healthy node.

Is this your bug?

File my report
Where
Edge Network
Error text
wrong version number
How bad
Stops work: a core feature can't be used.

Original reports3, newest first

  1. Broken TLS on edge node 64.29.17.1 (marsmedia.cc)#50361
  2. Broken TLS on edge node 64.29.17.1 (marsmedia.cc) — confirmed, needs infra escalation#49262
  3. Update: confirmed the SSL error is caused by one broken edge node, not random flakiness.#48746

Do you work on Vercel?

Claim its RAP Sheet to see what your users report and answer them in one place.