AWS Direct Connect Virtual Network Interface BGP Status Delay

Last Updated on April 30, 2021

When we were troubleshooting an issue with the BGP status of a Private Virtual Interface (VIF), we encountered that the BGP status in the router was up and we are able to communicate with our resources in AWS while in the AWS console, it was still down.

After some time, the BGP status of our Private Virtual Interface was also changed to up.

I’ve encountered this not just with Private VIF but also with Public VIF and Transit VIF.

As it turns out the BGP status in AWS console is delayed when there is change in status. Around 30 seconds and sometimes up to 3 minutes delayed.

If you’re troubleshooting the BGP session of your Direct Connect, don’t rely on the AWS console for the BGP status. Always use the status in your router.

Leave a Reply

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