What is the actual downtime for me-central-1?

Current information regarding the outage is available here: https://health.aws.amazon.com/health/status

You can subscribe for ongoing updates using the RSS link on that page. Many chat applications, such as Slack, allow you to create a channel that automatically pulls from an RSS feed to keep you up-to-date on the latest alerts.

If you're experiencing a regional impairment and need to restore operations in another region, you have a few options:

For Disaster Recovery: If you had AWS Elastic Disaster Recovery configured before the incident, you could perform a cross-region failover. This service provides near real-time data replication to a recovery region and allows you to launch recovery instances in the alternate region. The process involves:

• Verifying your launch settings are correctly configured in the recovery region
• Initiating recovery by launching instances from a point-in-time snapshot
• Redirecting traffic to the new recovery instances once they're running

For Manual Migration: If you don't have disaster recovery configured, you would need to manually recreate your infrastructure in another region using backups, snapshots, or AMIs if available.

Important Considerations:

• There will be downtime during the transition to another region
• You should have a planned failover window as the transition process can cause service interruption
• Once operations are restored in the new region, that becomes your active production environment

For the most current information about regional service status and estimated recovery times, I recommend checking the AWS Service Health Dashboard or contacting AWS Support directly, as they can provide specific details about ongoing incidents and expected resolution times.
Sources
Cross-Region disaster recovery using AWS Elastic Disaster Recovery | AWS Storage Blog