PowerSync incident

Invalid TLS certificate for some new instances in US region

Resolved after 1 day 7 hours, on March 22, 2026.

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.

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

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.

Your product runs on more than PowerSync

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.