Connectivity issue between India and US?

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Connectivity issue between India and US?

Posted by Yogesh Sarkar, 04-10-2013, 01:45 AM
Large number of our visitors on Airtel are reporting connectivity issue with sites based in US, while the same is also true for MTNL and BSNL users, though in case of different websites eg. Airtel users are having problem accessing my websites and I (MTNL user) am having problem accessing WHT and some other websites, though observing only slight slowness with my own sites.

Any one knows what exactly is the happening?

I dont believe there has been any further undersea cable cut, apart from what happened at the beginning of the month.
Posted by Host4Geeks-Kushal, 04-10-2013, 02:58 AM
Can you paste a Tracert?
Posted by Yogesh Sarkar, 04-10-2013, 03:45 AM
Can only do that for WHT, since I am not facing any issue with my own site. Have asked our members who are using to mail across tracert to our site and I have send an email regarding this to Airtel NOC. In case anyone has contact details of Airtel NOC or anyone else who can possibly help, then please let me know.

Result of WHT tracert from MTNL

Quote:

Tracing route to webhostingtalk.com [69.167.156.26]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * 15 ms 15 ms triband-del-59.180.210.193.bol.net.in [59.180.210.193]
4 * 14 ms 14 ms triband-del-59.180.210.194.bol.net.in [59.180.210.194]
5 * 15 ms 14 ms 125.19.8.161
6 309 ms 354 ms 286 ms AES-Static-122.36.144.59.airtel.in [59.144.36.122]
7 * 272 ms 271 ms te0-0-0-14.ccr22.lax04.atlas.cogentco.com [38.122.147.121]
8 * 271 ms 278 ms te0-3-0-7.ccr22.lax01.atlas.cogentco.com [154.54.43.249]
9 319 ms 318 ms 318 ms te0-2-0-5.ccr22.iah01.atlas.cogentco.com [154.54.27.18]
10 * 315 ms 318 ms te0-2-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.97]
11 * 325 ms 325 ms te0-4-0-7.mpd22.mci01.atlas.cogentco.com [154.54.80.106]
12 334 ms 334 ms 335 ms te0-7-0-33.mpd22.ord01.atlas.cogentco.com [154.54.25.78]
13 * 346 ms 336 ms te0-6-0-2.ccr21.ord03.atlas.cogentco.com [154.54.25.70]
14 * 329 ms 329 ms te0-6-0-1.ccr22.ord03.atlas.cogentco.com [66.28.4.66]
15 * 355 ms 346 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40.182]
16 * 328 ms 329 ms te2-2.ccr01.ord12.atlas.cogentco.com [154.54.86.166]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Slightly better second time around

Quote:

Tracing route to webhostingtalk.com [69.167.156.26]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * 15 ms 15 ms triband-del-59.180.210.193.bol.net.in [59.180.210.193]
4 15 ms 15 ms 15 ms triband-del-59.180.210.194.bol.net.in [59.180.210.194]
5 13 ms 14 ms 14 ms 125.19.8.161
6 * * 329 ms AES-Static-122.36.144.59.airtel.in [59.144.36.122]
7 272 ms 272 ms 273 ms te0-0-0-14.ccr22.lax04.atlas.cogentco.com [38.122.147.121]
8 495 ms 280 ms 288 ms te0-2-0-7.mpd22.lax01.atlas.cogentco.com [154.54.2.237]
9 * 315 ms 316 ms te0-1-0-6.mpd22.iah01.atlas.cogentco.com [154.54.0.246]
10 * 48 ms 271 ms te0-2-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.97]
11 325 ms 326 ms 325 ms te0-4-0-7.mpd22.mci01.atlas.cogentco.com [154.54.80.106]
12 335 ms 334 ms 335 ms te0-7-0-33.mpd22.ord01.atlas.cogentco.com [154.54.25.78]
13 337 ms 345 ms 345 ms te0-6-0-0.ccr21.ord03.atlas.cogentco.com [154.54.2.98]
14 * 338 ms 329 ms te0-6-0-1.ccr22.ord03.atlas.cogentco.com [66.28.4.66]
15 345 ms 136 ms 208 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40.182]
16 328 ms 329 ms 329 ms te2-2.ccr01.ord12.atlas.cogentco.com [154.54.86.166]
17 * 341 ms * ae-2.r20.sngpsi02.sg.bb.gin.ntt.net [129.250.4.142]
18 * 1295 ms * as-3.r20.snjsca04.us.bb.gin.ntt.net [129.250.3.88]
19 * 1385 ms * ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.106]
20 * * * Request timed out.
21 1836 ms * * xe-0-3-0-2-54.r06.chcgil09.us.ce.gin.ntt.net [128.242.180.34]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Yogesh>

Posted by Yogesh Sarkar, 04-10-2013, 04:56 AM
Got a few trace routes from members, all seem fine but slowness is still there.

BCMT-Tracert.jpg

On the other hand, WHT is working fine now for me.
Posted by Maya459, 04-10-2013, 06:39 AM
I'm also facing the same issues and tried to find the reason behind the same but was not able to find the same.
Posted by Vinayak_Sharma, 04-10-2013, 10:13 AM
Same issue here using Airtel, yesterday was worst.

WHT won't load, connectivity to my servers on both sides of USA was toooo slow.

May be its related to "Sabotage of undersea cables to slow down internet speed for 30 days"