yes the whole idea is separate routing. if both services route to the same backbone you could suffer a catastrophic outage. ie one network routes from atlanta to dallas using their backbone but then hands off to another peer - 2ndary service routes from atlanta to D.C. using a separate backbone and does not hand off to the same peer. that way if the peer has issues (goes out of business) you are still up. plus you can divert specific services to WAN1 and others to WAN2 with failover only - like smtp binding - and other services that are not so sticky to balance a little. SSL does not like flip-flopping of ip's for some websites.
