Personne ne devrait être on-call en 2026.
Des agents qui lisent ton code, surveillent ton infra et réparent la production avant ton réveil.
· Accès anticipé en cours de déploiement.
Polylane trouve les issues dans ton application et les répare pour toi, automatiquement.
Il apprend tout ce que tu fais tourner. Chaque cloud, chaque dépôt, chaque dépendance : un seul graphe en direct.
Topology Share
Search your cloud resources...
Filter Galaxy Flow Table
checkout-edge Worker Critical Critical to your architecture.
Issue hotspot: 4 issues in the last 7 days
Change hotspot: 12 changes in the last 7 days
Cloudflare · coreplane · earth · Compute
hd-prod Hyperdrive Critical Critical to your architecture.
Change hotspot: 7 changes in the last 7 days
Cloudflare · coreplane · earth · Databases
ingest-events Lambda function Standard Important to your architecture.
Issue hotspot: 2 issues in the last 7 days
AWS · coreplane-prod · us-east-1 · Compute
payments-db Database Critical Critical to your architecture.
Issue hotspot: 1 issue in the last 7 days
Change hotspot: 3 changes in the last 7 days
PlanetScale · coreplane · us-east · Databases
Il ne cesse jamais de chercher des problèmes. Les issues remontent toutes seules, y compris celles sur lesquelles personne n'a pensé à alerter.
Issues Critical latency degradation in checkout-edge worker Overview
Critical latency degradation in checkout-edge worker
Incident critical Polylane ·Detected 3 hours ago ·Last seen 4 minutes ago ·2 occurrences
OverviewInvestigationMetricsTimelineProperties
checkout-edge › Cloudflare Worker Critical latency degradation detected in checkout-edge worker: 18x+ P99 latency spikes sustained for 12 minutes
Causal metrics All metrics
Request Duration
414 ms ▲ 43.1σ
Wall Time
416 ms ▲ 43.0σ
CPU Time
14 ms ▲ 2.6σ
Blast radius edge-gateway Cloudflare Worker ··· checkout-edge Cloudflare Worker ··· hd-prod Hyperdrive ··· payments-db PlanetScale ··· cart-svc Cloudflare Worker ···
Search your cloud resources...
5 resources Graph Table
edge-gateway Cloudflare Worker ··· checkout-edge Cloudflare Worker ··· hd-prod Hyperdrive ··· payments-db PlanetScale ··· cart-svc Cloudflare Worker ··· Analysis Copy
Deploy 9f3c2a1 shrank the Hyperdrive pool
hd-prod from 50 connections to 5. Under checkout load,
requests queue on connection checkout and P99 rises 18× against the 30-minute baseline. Restoring the pool size restores latency.
Tags
service · checkout-edgeprovider · cloudflaredeploy · 9f3c2a1signal · wall_time_p99
Il écoute chaque alerte que tu as déjà. Chaque alerte triée, les vraies enquêtées et corrigées.
Issues
Issues
Problems detected by Polylane and alerts from your monitoring tools, triaged automatically.
IncidentsNo incidentAll Search issues... Filter
Title Detected by Impact Severity Status Occurrences
Critical latency degradation in checkout-edge worker 
Polylane checkout-edge Cloudflare Worker critical Incident 2
Polylane checkout-edge Cloudflare Worker critical Incident 2 checkout-edge P99 latency above 2s for 5m 
Datadog checkout-edge Cloudflare Worker critical Incident 118
Datadog checkout-edge Cloudflare Worker critical Incident 118 TypeError: cannot read 'region' of undefined in checkout handler 
Sentry 
cart-svc Deployment medium Triaging 41
Sentry cart-svc Deployment medium Triaging 41 edge-gateway 5xx ratio above 1% for 5m 
Grafana Cloud 
edge-gateway Fly Machine medium No incident 6
Grafana Cloud edge-gateway Fly Machine medium No incident 6 orders-db CPUUtilization above 80% 
CloudWatch 
orders-db Aurora cluster low No incident 1
CloudWatch orders-db Aurora cluster low No incident 1 payments-api webhook retry queue depth above 5,000 Datadog payments-api Cloudflare Worker high Resolved 3
Datadog payments-api Cloudflare Worker high Resolved 3 Il répare les problèmes, pas les symptômes. Il trouve la cause racine de chaque issue qu'il détecte et soumet des PR pour la corriger.
github.com/coreplane/payments-api/pull/491
Cap retries on the checkout webhook worker #491
polylane Open polylane wants to merge 1 commit into
main from polylane/autofix/chat/k3x9f2-4e7d21a Conversation 1 Commits 1 Checks 1 Files changed 2
polylane bot commented 6 minutes ago ···
Retries on the checkout webhook worker were unbounded: a failing delivery re-queued itself forever and amplified load on payments-api. This caps delivery at 5 attempts with exponential backoff and dead-letters the payload after the last one.
What changed
worker/deliver.ts gains MAX_DELIVERY_ATTEMPTS = 5 and backoff between attempts; exhausted payloads land in checkout-webhooks-dlq instead of re-queueing.
Validation
npm test — 214 passed. A forced failing delivery stopped after 5 attempts and appeared in the dead-letter queue.
Root cause · Why it's safe · Out of scope
polylane added commit 4e7d21a Verified
Review required At least 1 approving review is required
ci / test Successful in 3m 12s Details
Review required Waiting on your review: Polylane never merges on its own
Merging is blocked
Il répond aux questions que l'on-call reçoit. Qui est responsable, qu'est-ce qui a changé, est-ce nous : la réponse arrive dans le thread, avec les preuves.
# incidents
Messages
Add canvas
Files & links
Polylane Agent 2:14 AM
Critical latency regression on checkout-edge: Wall Time P99 is 18× baseline, sustained since 2:02 AM, and checkout requests are queuing. I'm investigating.
boris 2:15 AM
probably the Hyperdrive change in tonight's deploy?
👀 1 Polylane Agent 2:16 AM
Working on it
- ✓ Pulled the last 30 minutes of checkout-edge metrics
- ✓ Correlated with the change records
- ◐ Testing the Hyperdrive pool hypothesis
- ○ Draft the fix
status as of 2:17 AM UTC
Polylane Agent 2:19 AM
You're right. Deploy 9f3c2a1 shrank the
hd-prod connection pool from 50 to 5,
and checkout requests queue behind connections. Confirmed against the pool metrics and the change record.
Fix is drafted, coreplane/checkout-edge#142 restores the pool.
CI is running; I'll report back here.
Open in Polylane Configure
Il fait entrer la production dans ton terminal. Ton agent de codage voit ce qui tourne avant de changer quoi que ce soit.
claude — ~/checkout-edge
> make region a required field on the checkout request schema
●polylane · searchcallers of POST /checkout
●polylane · runToolqueryLogs · request shapes
⏺ Hold on: cart-svc and edge-gateway still send region-less requests, 41,200 in the last 24h. Requiring it now would 400 them both. Safer: default it, migrate the two callers, then require. Are you okay with this plan?
Waiting for your reply…
Il se souvient de chaque incident. Le suivant ne part jamais de zéro.
Settings Memories
Memories
Institutional knowledge from investigations and observations.
All Mine Search memories... Filter 7 memories
Name Source Created by Created
hd-prod must keep 50 connections: at 5, checkout-edge requests queue and P99 rises 18x Investigation P System 3 hours ago
Deploys that touch checkout-edge's Hyperdrive binding need the pool size checked in review Change analysis P System 3 hours ago
cart-svc and edge-gateway still send region-less checkout requests; region stays optional until they migrate Investigation P System yesterday
payments-api webhook retries are capped at 5 with backoff since #491; dead-letters land in checkout-webhooks-dlq Change analysis P System 2 days ago
payments-db connection spikes follow cart-svc retries, not checkout traffic Observation P System 6 days ago
checkout-edge P99 sits at 1.4-1.8s on weekday evenings; the Sunday 02:00 UTC bump is the analytics backfill Observation P System 2 weeks ago
edge-gateway returns 502 for 40s after every deploy while its Fly machines drain; not an incident Change analysis P System 3 weeks ago
