An Azure managed PostgreSQL database service for app development and deployment.
Hi Patrick Hartley,
Here are few things you can consider:
- Check Server Status:
- Go to the Azure portal and check the server's status in the Overview section. Ensure that it's set to "Running" and not "Stopped" or in any other failed state.
- Review Service Health:
- Check for any active incidents that might be affecting your server by looking at Service Health Notifications.
- Potential Burstable SKU Issues:
- If you’re using a burstable SKU (B-series), consider that performance might drop during peak usage when CPU credits deplete, leading to unresponsive behavior. If applicable, you might want to look at upgrading to a General Purpose or Memory Optimized SKU for more consistent performance.
- Restart Attempts:
- If you have changed any server parameters recently, rolling those back could help. Sometimes, specific settings can prevent the server from starting correctly.
- Restore from Backup:
- If the server continues to fail to start, you may consider restoring it from a backup. You can navigate to Backup and Restore settings in the Azure portal and use a point-in-time recovery.
- Monitoring Performance:
- Set up metrics and alerts under the Monitoring section to keep an eye on performance indicators such as CPU usage, connections, etc.
If you are using east US you can see some issues as there is some ongoing outage in this region, try different region for work around. Please try to set up alerts in service health so that you will get notified if you are having in regional issues or outages.
I hope this information helps, kindly consider upvoting the comment it will help others who are facing similar challenges. Please let us know if you have further queries Happy to help you.
Thanks!
Kalyani