API degradation causing slow responses

API performance has returned to normal and instance health looks stable.

We believe the degradation was triggered during autoscaling: two API instances failed health checks, delaying scale-out until they recovered. Capacity has since been added and we’re continuing to monitor progress.

We’ve added additional API capacity and are monitoring instance health. Current instance health looks good and performance is improving; we’ll continue to monitor closely.

We’re investigating degraded performance and elevated error rates. Some API instances are down, causing slow responses. Database appears healthy. We’re working to restore normal service.