Hello! Macomnet (ISP, AS8470, Moscow, Russia) uses world connectivity via Teleglobe. We have a router, managed by us, in NY. The interface pointing to America uses Teleglobe's address and another one, pointing to Moscow - ours. Regullary I see a quite strange heavy delays on Teleglobe to Alternet interconnect point. I traced the route to several destinations with SRC addresses from Teleglobe's and Macomnet's IP blocks. The problem is that packets with SRC from Teleglobe address space passes through with lower delays than packets with Macomnet's SRC addresses. The first thing what people expect is assymetric routing (i.e. route from Alternet goes another way back to us). But it's not possible. Our backup provider (AS8342) plugs into Teleglobe also. So Teleglobe advertises the right route to Alternet and it's quite impossible for Alternet to have another route to Macomnet. I believe it's not a routing problem. I contacted Teleglobe and they said that it could be a temporary congestion. I wonder how could congestion exist for Macomnet addresses and not to appear for Teleglobe itself!!! That is the question. Look at the traces below. The first one uses Teleglobe SRC address, the second - ours. ----------------------------------------- Trace with Teleglobe_SRC_ADDRESS : ----------------------------------------- nyy-1#trace Protocol [ip]: Target IP address: 204.71.127.3 Source address: 207.45.205.14 ^^^^^^^^^^^^^^^^^ Teleglobe's address Numeric display [n]: Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Port Number [33434]: Loose, Strict, Record, Timestamp, Verbose[none]: Type escape sequence to abort. Tracing the route to intrepid.net (204.71.127.3) 1 if-0-1-0.bb6.NewYork.Teleglobe.net (207.45.205.13) [AS 6453] 0 msec 4 msec 0 msec 2 if-6-0-0.bb1.NewYork.Teleglobe.net (207.45.221.67) [AS 6453] 0 msec 0 msec 4 msec 3 Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) [AS 701] 0 msec 4 msec ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Teleglobe goes fine. 157.130.5.217 [AS 701] 4 msec 4 144.ATM2-0.XR2.NYC1.ALTER.NET (146.188.178.150) [AS 701] 4 msec 0 msec 4 msec 5 194.ATM3-0.TR2.NYC1.ALTER.NET (146.188.178.198) [AS 701] 0 msec 4 msec 0 msec 6 104.ATM7-0.TR2.DCA8.ALTER.NET (146.188.138.169) [AS 701] 8 msec 4 msec 12 msec 7 152.63.32.217 [AS 701] 4 msec 8 msec 8 msec 8 192.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.165) [AS 701] 8 msec 8 msec 8 msec 9 intrepid-gw2.customer.ALTER.NET (157.130.36.214) [AS 701] 20 msec 20 msec 32 msec 10 office-shep.intrepid.net (209.190.129.38) [AS 6359] 20 msec 20 msec 28 msec 11 intrepid.net (204.71.127.3) [AS 6359] 20 msec 16 msec 20 msec ---------------------------------------------------- AT THE SAME TIME Trace with Macomnet_SRC_ADDRESS : ---------------------------------------------------- nyy-1#trace Protocol [ip]: Target IP address: 204.71.127.3 Source address: 195.128.65.33 ^^^^^^^^^^^^^^^^^^^ Macomnet's address Numeric display [n]: Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Port Number [33434]: Loose, Strict, Record, Timestamp, Verbose[none]: Type escape sequence to abort. Tracing the route to intrepid.net (204.71.127.3) 1 if-0-1-0.bb6.NewYork.Teleglobe.net (207.45.205.13) [AS 6453] 0 msec 0 msec 4 msec 2 Teleglobe.net (207.45.221.99) [AS 6453] 0 msec 0 msec 0 msec 3 * Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) [AS 701] 1248 msec ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ !!!!!! 157.130.5.217 [AS 701] 1276 msec 4 144.ATM2-0.XR1.EWR1.ALTER.NET (146.188.178.146) [AS 701] 1220 msec 1268 msec * 5 * * * 6 * * 105.ATM6-0.TR1.DCA8.ALTER.NET (146.188.138.121) [AS 701] 1272 msec 7 152.63.32.201 [AS 701] 1284 msec 1288 msec * 8 * 193.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.169) [AS 701] 2716 msec * 9 intrepid-gw2.customer.ALTER.NET (157.130.36.214) [AS 701] 1392 msec * 1356 msec 10 office-shep.intrepid.net (209.190.129.38) [AS 6359] 1244 msec 1244 msec 1328 msec 11 intrepid.net (204.71.127.3) [AS 6359] 1284 msec 1324 msec 1392 msec ---------------- Have a nice day! Esakov Dmitriy, Macomnet Internet Dpt.