Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

How to resolve: Amazon RDS database in an incompatible-network state

by | Aug 12, 2021

Wondering how to resolve issues with an Amazon RDS database that is in an incompatible-network state? We can help you!

Here, at Bobcares, we often receive similar queries from our AWS customers as a part of our AWS Support Services.

Today, let’s see the steps followed by our Support Techs to help our customers to fix the issues with an Amazon RDS database that is in an incompatible-network state.


Amazon RDS database in an incompatible-network state

The Incompatible-network is a terminal status. Therefore, it is impossible to modify or reboot the instance when it gets into this state. But in most cases, it might still be accessible at the database level. That means we can connect to the database even though the instance is in incompatible-network state.

The incompatible-network state occurs due to the following reasons:

  • The AWS subnet where the RDS DB instance is present has no enough IP addresses.
  • Reaching the service quota for Elastic Network Interfaces in the AWS Region can cause incompatible-network issue.
  • The subnet mentioned in the RDS DB subnet group no longer exists in the Amazon VPC.
  • If the RDS DB instance is set to publicly accessible and the DNS hostnames and the DNS resolution options are disabled, the issue may occur. So make sure to enable both options for an RDS DB instance to be publicly accessible.
  • The original elastic network interface of the RDS DB instance was deleted while the instance was stopped. When the RDS DB instance was restarted, the elastic network interface wasn’t found.
  • While stopping the RDS DB instance, the original elastic network interface was deleted. It wasn’t found after restarting the DB instance.

The following actions can cause the incompatible-network state:

  • By modifying the RDS DB instance to use a Multiple Availability Zones deployment.
  • By modifying the RDS DB instance’s class.
  • Replacing of the host due to any maintenance event.
  • Restore from the snapshot.
  • Restarting of RDS Db instance.
  • Replacement of RDS DB instance.


How to fix incompatible-network state issue

As we already said we can’t modify or reboot the RDS DB instance in incompatible-network state. So it is always better to have a snapshot backup to be sure that we can restore the data to another RDS DB instance.

  1. Log in to the AWS Management console and then open the Amazon RDS console.

2. Select Databases.

3. Select the RDS DB instance that is in incompatible-network state.

4. Then from the Connectivity & Security, note the VPC ID and subnet IDs.

5. Now open the Amazon VPC console, and then select the VPCs.

6. Select the previously noted VPC, select Actions, and then select Edit DNS hostname and Edit DNS resolution.

7. Make sure to enable DNS hostnames and DNS resolution.

8. Then elect Subnets and then make sure that all subnets noted previously are listed and have available IP addresses.

9. Now open the Amazon EC2 console, and make sure that we haven’t reached the quota for elastic network interfaces.


To resolve an RDS DB instance that is already in an incompatible-network state, and there are previously enabled automated backups for the DB instance, we need to temporarily stop any writes to the database, and then do a point-in-time recovery (PITR).

If we didn’t enable the automated backups already, we need to create a new RDS DB instance. After creating, we can migrate the data by using any backup and restore tools like mysqldump.

[Need help with more AWS queries? We’d be happy to assist]


To conclude, today we discussed the steps followed by our Support Engineers to help our customers to fix the issues with an Amazon RDS database that is in an incompatible-network state.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.