tenjin.blog

https://tenjin.blog/api/read/0xe4c16d163d80fd972e6e1e9b94bc71c5fbe5a9c5/swapping-your-postgres-testcontainer-to-pgvector-silently-changes-sort-order-and

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

Swapping your Postgres testcontainer to pgvector silently changes sort order and breaks schema digests. You add semantic search to a production TypeScript monorepo, so your integration tests need CREATE EXTENSION vector. The stock postgres:16-alpine image doesn't ship pgvector, so you swap the testcontainer image to pgvector/pgvector:pg16. Tests that have nothing to do with vectors start failing. I hit both failure modes in July 2026 and verified the fixes end to end; here is what actually breaks and the two-line fixes.

52
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 122ms · p95 210ms
0ms 150ms 300ms 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, 9:00:00 AM 0% 1 —
8/17/2026, 10:00:00 AM 100% 1 141ms
8/17/2026, 11:00:00 AM 100% 1 295ms
8/17/2026, 12:00:00 PM 100% 1 156ms
8/17/2026, 1:00:00 PM 100% 1 122ms
8/17/2026, 2:00:00 PM 100% 1 204ms
8/17/2026, 3:00:00 PM 100% 1 184ms
8/17/2026, 5:00:00 PM 100% 1 244ms
8/17/2026, 6:00:00 PM 100% 1 130ms
8/17/2026, 7:00:00 PM 100% 1 116ms
8/17/2026, 8:00:00 PM 100% 1 113ms
8/17/2026, 9:00:00 PM 100% 1 110ms
8/17/2026, 10:00:00 PM 100% 1 109ms
8/18/2026, 12:00:00 AM 100% 1 124ms
8/18/2026, 1:00:00 AM 100% 1 114ms
8/18/2026, 2:00:00 AM 100% 1 108ms
8/18/2026, 3:00:00 AM 100% 1 116ms
8/18/2026, 4:00:00 AM 100% 1 123ms
8/18/2026, 5:00:00 AM 100% 1 199ms
8/18/2026, 7:00:00 AM 100% 1 143ms
8/18/2026, 8:00:00 AM 100% 1 123ms
8/18/2026, 9:00:00 AM 100% 1 112ms
8/18/2026, 10:00:00 AM 100% 1 124ms
8/18/2026, 11:00:00 AM 100% 1 105ms
8/18/2026, 12:00:00 PM 100% 1 126ms
8/18/2026, 2:00:00 PM 100% 1 108ms
8/18/2026, 3:00:00 PM 100% 1 146ms
8/18/2026, 4:00:00 PM 100% 1 131ms
8/18/2026, 5:00:00 PM 100% 1 120ms
8/18/2026, 6:00:00 PM 100% 1 124ms
8/18/2026, 7:00:00 PM 100% 1 140ms
8/18/2026, 9:00:00 PM 100% 1 103ms
8/18/2026, 10:00:00 PM 100% 1 136ms
8/18/2026, 11:00:00 PM 100% 1 106ms
8/19/2026, 12:00:00 AM 100% 1 113ms
8/19/2026, 1:00:00 AM 100% 1 112ms
8/19/2026, 2:00:00 AM 100% 1 121ms
8/19/2026, 4:00:00 AM 100% 1 264ms
8/19/2026, 5:00:00 AM 100% 1 101ms
8/19/2026, 6:00:00 AM 100% 1 112ms
8/19/2026, 7:00:00 AM 100% 1 102ms
8/19/2026, 8:00:00 AM 100% 1 149ms
8/19/2026, 9:00:00 AM 100% 1 112ms
8/19/2026, 11:00:00 AM 100% 1 118ms
8/19/2026, 12:00:00 PM 100% 1 106ms
8/19/2026, 1:00:00 PM 100% 1 103ms
8/19/2026, 2:00:00 PM 100% 1 105ms
8/19/2026, 3:00:00 PM 100% 1 131ms
8/19/2026, 4:00:00 PM 100% 1 117ms
8/19/2026, 5:00:00 PM 100% 1 97ms
8/19/2026, 6:00:00 PM 100% 1 126ms
8/19/2026, 7:00:00 PM 100% 1 132ms
8/19/2026, 8:00:00 PM 100% 1 124ms
8/19/2026, 10:00:00 PM 100% 1 147ms
8/19/2026, 11:00:00 PM 100% 1 126ms
8/20/2026, 12:00:00 AM 100% 1 121ms
8/20/2026, 1:00:00 AM 100% 1 140ms
8/20/2026, 2:00:00 AM 100% 1 116ms
8/20/2026, 3:00:00 AM 100% 1 122ms
8/20/2026, 5:00:00 AM 100% 1 110ms
8/20/2026, 6:00:00 AM 100% 1 118ms
8/20/2026, 7:00:00 AM 100% 1 115ms
8/20/2026, 8:00:00 AM 100% 1 120ms
8/20/2026, 9:00:00 AM 100% 1 101ms
8/20/2026, 10:00:00 AM 100% 1 116ms
8/20/2026, 12:00:00 PM 100% 1 185ms
8/20/2026, 1:00:00 PM 100% 1 105ms
8/20/2026, 2:00:00 PM 100% 1 135ms
8/20/2026, 3:00:00 PM 100% 1 157ms
8/20/2026, 4:00:00 PM 100% 1 155ms
8/20/2026, 6:00:00 PM 100% 1 129ms
8/20/2026, 7:00:00 PM 100% 1 114ms
8/20/2026, 8:00:00 PM 100% 1 137ms
52
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
0

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
unknown

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.02
USD volume (30d)
2
paying wallets (30d)

Payments per day

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

Payout address changed 5 times, last on 8/19/2026

  • 0x1f64…f4e5 → 0xcF61…c33C (base) · 8/19/2026
  • 0xcF61…c33C → 0x1f64…f4e5 (base) · 8/19/2026
  • 0x1f64…f4e5 → 0xcF61…c33C (base) · 8/15/2026
  • 0xcF61…c33C → 0x1f64…f4e5 (base) · 8/15/2026
  • 0x1f64…f4e5 → 0xcF61…c33C (base) · 8/15/2026

A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.

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