Data packet path for upstream and downstream.

[Trex]

I wonder if the route for packets upstream and downstream between two points is the same or different. If I request something from a server, the packets will be routed on the same path as my request packets or it totally depends upon the upstream provider for both ends? @Lolita_Magnum

 

[mreccentric]

It might not be the same. Because, even the data upstream and downstream keep taking different routes during a particular data access.

 

[WieldyBinkie]

Check with their looking glass.

 

[Lolita_Magnum]

Totally depends on the BGP router policies, the upstream and even the data server originator and even your ISP sets.
Compared to smaller transits; very high capacity transits (multi-Gig >100) options usually cost based on whichever transfer is higher. Either upload or download. The interface cost is negligible and often one time only.

Example --> Airtel will uplink their packet to HE to reach point B; seeing it is cheaper and has been less utilized, or it. Similarly, point B might observe that it can reach Airtel via it's peering with its nearest IX.
Now, your question might be. Then why didn't Airtel do the same.
The Answer is:
While, for Airtel, their AS path might look like >> 9498 6939 60048 and via exchange it'd be 9498 6777 60048; their local pref will be higher for HE path and vice versa for point B.

Alternate Example --> Airtel uplinks to HE; since it is buying transit and hence HE will advertise Airtel ASN to their other locally connected ASN; and hence Airtel served its packet to point B.
But point B might be only going for local peering, where either only regional routes are received or only HE AS routes are accepted. In this situation, it will use different path. (Reason for this use case is usually cost or economy)