PowerSync incident

Invalid TLS certificate for some new instances in US region

Notice Resolved View vendor source →

PowerSync experienced a notice incident on March 22, 2026, lasting 1d 7h. The incident has been resolved; the full update timeline is below.

Started
Mar 22, 2026, 02:00 AM UTC
Resolved
Mar 23, 2026, 09:45 AM UTC
Duration
1d 7h
Detected by Pingoru
Mar 22, 2026, 02:00 AM UTC

Update timeline

  1. resolved Mar 23, 2026, 09:51 AM UTC

    Since 2026-03-22, some new instances in the US region failed to configure the correct TLS certificate. These instances instead received the `Kubernetes Ingress Controller Fake Certificate`, which causes all connections to the instance to fail. This specifically affected some new instances, as well as some instances that were previously stopped/deprovisioned, then deployed again. Running instances were not affected. The issue is resolved, and all instances should be served using the correct TLS certificate now.