Ouvertes 2 Résolues 4
Faible Résolu

Analytics showed a brief data gap during migration

During the database migration, real-time analytics went dark for a few hours. No data was lost. The gap only affected live visibility, not historical records.

Résolution :

We backfilled all historical data (260M+ records) and verified per-day consistency. Real-time ingestion came back within hours.

Ouvert 25 mars 2026 · Résolu 26 mars 2026
Moyen Résolu

Safari users hit a login redirect loop on the dashboard

If you used Safari, logging into the dashboard triggered a redirect loop. A WebKit cookie handling quirk caused the session to fail across subdomains.

Résolution :

We fixed cookie attributes for cross-subdomain compatibility. Login works correctly on all major browsers now.

Ouvert 22 mars 2026 · Résolu 23 mars 2026
Moyen Résolu

Stale proxies stayed in the pool during peak hours

During peak usage, the proxy validation pipeline couldn't keep up. Some requests hit recently-failed proxies before the pool evicted them.

Résolution :

We added parallel health checks and faster dead-proxy eviction. The pool now stays fresh even under 10x normal load.

Ouvert 10 mars 2026 · Résolu 12 mars 2026
Élevé Résolu

Browser requests timed out under heavy JS loads

Browser-mode requests were timing out on pages with heavy JavaScript bundles. Headless Chrome didn't have enough shared memory to handle concurrent sessions.

Résolution :

We increased shared memory for browser sessions and added per-request resource limits. Timeout rate dropped from ~8% to under 0.5%.

Ouvert 4 mars 2026 · Résolu 5 mars 2026