I think you might need to clarify the situation a bit.
From what I understood you are saying that you have the basic internal and external interfaces on the ASA and also a link to a MPLS network where possinly some remote sites are located?
I am not sure what you are asking of us though? I do see that you have only configured a default route on the ASA. Naturally if there are some remote sites between one of the interfaces you should have static routes configured for those networks pointing to the correct interface and correct gateway IP address.
For traffic between your LAN and MPLS networks will go without NAT by default so you dont have to worry about that.
If your MPLS networks require NAT towards the External networks then you can do a similiar NAT configuration for it like you have for your LAN at the moment.
Your current interface naming is kinda confusing. It seems that the "outside" holds the default route while the "internet" does not have any routes.
So as I said can you please clarify your requirements for the setup.
I am not sure what changes you made so I can't really say anything. If you changed the default route to point somewhere else then that is probably the reason why you lost connectivity to the firewall.
We would really need to know exactly what you are attempting to do and what the interfaces are used for. You have interfaces "outside" and "internet" which both to me hint about an interface directly connected to the Internet.
If the other interface has a connection to some remote networks then that interface needs routes for specific networks only. The interface which is supposed to be used for Internet traffic needs to have the default route.
Ok lets see if this helps, the ASA was the connection from a remote site through an MPLS connection back to the DataCenter. The MPLS connection was not fast enough to handle internal traffic plus internet traffic, so they installed a circuit for internet. The outside connection is for the MPLS traffic to the DC, the Internet connection is for internet only, so I need internal LAN traffic go across the outside interface and all other traffic go across the internet interface. I did a route outside 0 0 126.96.36.199 and route for 188.8.131.52/24 to go to the outside interface but when I do that I can't connect back to the ASA.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :