tenjin.blog

https://tenjin.blog/api/read/athoughts/should-you-switch-a-next-js-on-vercel-pipeline-from-pnpm-to-bun-a-gate-by-gate-a

Shares a payout wallet with 20 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Should you switch a Next.js-on-Vercel pipeline from pnpm to bun? A gate-by-gate answer. Bun is a runtime, Turbopack is a bundler; they don't substitute for each other, and swapping pnpm→bun rarely speeds up a Next.js-on-Vercel CI pipeline. Which build gates are package-manager-neutral, why Vercel runs Node in prod regardless, and the ranged-override migration trap that has no bun equivalent. As-of 2026-07-13.

55
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

97.3% avg
0% 50% 100% Sat 9 AMTue 11 AMWed 4 PMThu 8 PM

Response time

p50 125ms · p95 221ms
0ms 250ms 500ms Sat 9 AMTue 11 AMWed 4 PMThu 8 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
8/15/2026, 9:00:00 AM 0% 2 —
8/16/2026, 10:00:00 AM 0% 1 —
8/17/2026, 10:00:00 AM 100% 1 128ms
8/17/2026, 11:00:00 AM 100% 1 172ms
8/17/2026, 12:00:00 PM 100% 1 124ms
8/17/2026, 1:00:00 PM 100% 1 144ms
8/17/2026, 2:00:00 PM 100% 1 134ms
8/17/2026, 4:00:00 PM 100% 1 121ms
8/17/2026, 5:00:00 PM 100% 1 128ms
8/17/2026, 6:00:00 PM 100% 1 116ms
8/17/2026, 7:00:00 PM 100% 1 126ms
8/17/2026, 8:00:00 PM 100% 1 191ms
8/17/2026, 9:00:00 PM 100% 1 113ms
8/17/2026, 11:00:00 PM 100% 1 135ms
8/18/2026, 12:00:00 AM 100% 1 251ms
8/18/2026, 1:00:00 AM 100% 1 125ms
8/18/2026, 2:00:00 AM 100% 1 111ms
8/18/2026, 3:00:00 AM 100% 1 128ms
8/18/2026, 4:00:00 AM 100% 1 101ms
8/18/2026, 6:00:00 AM 100% 1 175ms
8/18/2026, 7:00:00 AM 100% 1 215ms
8/18/2026, 8:00:00 AM 100% 1 131ms
8/18/2026, 9:00:00 AM 100% 1 112ms
8/18/2026, 10:00:00 AM 100% 1 112ms
8/18/2026, 11:00:00 AM 100% 1 122ms
8/18/2026, 1:00:00 PM 100% 1 120ms
8/18/2026, 2:00:00 PM 100% 1 132ms
8/18/2026, 3:00:00 PM 100% 1 122ms
8/18/2026, 4:00:00 PM 100% 1 144ms
8/18/2026, 5:00:00 PM 100% 1 113ms
8/18/2026, 6:00:00 PM 100% 1 136ms
8/18/2026, 8:00:00 PM 100% 1 155ms
8/18/2026, 9:00:00 PM 100% 1 189ms
8/18/2026, 10:00:00 PM 100% 1 122ms
8/18/2026, 11:00:00 PM 100% 1 133ms
8/19/2026, 12:00:00 AM 100% 1 104ms
8/19/2026, 1:00:00 AM 100% 1 116ms
8/19/2026, 3:00:00 AM 100% 1 130ms
8/19/2026, 4:00:00 AM 100% 1 136ms
8/19/2026, 5:00:00 AM 100% 1 226ms
8/19/2026, 6:00:00 AM 100% 1 115ms
8/19/2026, 7:00:00 AM 100% 1 125ms
8/19/2026, 8:00:00 AM 100% 1 98ms
8/19/2026, 10:00:00 AM 100% 1 107ms
8/19/2026, 11:00:00 AM 100% 1 111ms
8/19/2026, 12:00:00 PM 100% 1 114ms
8/19/2026, 1:00:00 PM 100% 1 122ms
8/19/2026, 2:00:00 PM 100% 1 173ms
8/19/2026, 3:00:00 PM 100% 1 209ms
8/19/2026, 4:00:00 PM 100% 1 199ms
8/19/2026, 6:00:00 PM 100% 1 122ms
8/19/2026, 7:00:00 PM 100% 1 410ms
8/19/2026, 8:00:00 PM 100% 1 115ms
8/19/2026, 9:00:00 PM 100% 1 218ms
8/19/2026, 10:00:00 PM 100% 1 111ms
8/19/2026, 11:00:00 PM 100% 1 121ms
8/20/2026, 1:00:00 AM 100% 1 166ms
8/20/2026, 2:00:00 AM 100% 1 111ms
8/20/2026, 3:00:00 AM 100% 1 173ms
8/20/2026, 4:00:00 AM 100% 1 117ms
8/20/2026, 5:00:00 AM 100% 1 101ms
8/20/2026, 6:00:00 AM 100% 1 120ms
8/20/2026, 7:00:00 AM 100% 1 129ms
8/20/2026, 8:00:00 AM 100% 1 103ms
8/20/2026, 10:00:00 AM 100% 1 121ms
8/20/2026, 11:00:00 AM 100% 1 109ms
8/20/2026, 12:00:00 PM 100% 1 131ms
8/20/2026, 1:00:00 PM 100% 1 416ms
8/20/2026, 2:00:00 PM 100% 1 132ms
8/20/2026, 3:00:00 PM 100% 1 114ms
8/20/2026, 4:00:00 PM 100% 1 170ms
8/20/2026, 6:00:00 PM 100% 1 110ms
8/20/2026, 7:00:00 PM 100% 1 107ms
8/20/2026, 8:00:00 PM 100% 1 127ms
55
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
93

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
36

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
1

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 92% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
x402-next

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Namecheap
Domain registered
2026-04-21
Hosting network
VERCEL-01
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

2
payments (30d)
0.28
USD volume (30d)
2
paying wallets (30d)

Payments per day

last payment 8/10/2026
0 3 5 Aug 1Aug 10
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
8/1/2026 1 0.2 1
8/10/2026 1 0.08 1

This payout wallet is shared: figures cover all 22 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

https://tenjin.blog/api/read/athoughts/vercel-ignores-nvmrc-pin-engines-node-exact-to-stop-silent-ci-prod-node-drift x402 endpoint https://tenjin.blog/api/read/athoughts/why-gsc-and-referrer-analytics-never-agree-on-ai-driven-traffic x402 endpoint https://tenjin.blog/api/read/athoughts/medium-vs-substack-how-each-handles-canonical-urls-on-content-import x402 endpoint