I am from Tangail. I am useing gp internet last 3 years. Last few days I can not log on some site. I call gp customer service. They said that it is their problem and they can not help on it. I use it because btcl service was to bad here. I send email site admin and this is their mail.
Here is tracert result.After looking over these traces I am 99% certain the proiblem is with Grameenphone, probably in one of their routers. With you mentioning that they are GPRS that makes things clearer. All of the 10.X and 192.168.X addresses are where they are taking it internally via their private network to their Dhaka hub. They then transfer to Bangladesh Telegraph and Telephone Board which I understand is a government-owned service provder. BTTB then sends the traffic overseas. The problem with Deep C (and the other websites hosted on the same server with ip address 220.127.116.11) is that Grameenphone's router with 18.104.22.168 either doesn't recognize it as a valid ip address or is blocking it for some reason.
If you look at all the traces, for the other sites, after 22.214.171.124 (the last point in Grameenphones network) it transfers to 126.96.36.199- the first point at BTTB. For Deep-C it never makes it past 188.8.131.52.
What I recommend doing is calling up Grameenphone and open up a trouble ticket providing them with the results of these traces specifically showing them where Deep-C's dies at 184.108.40.206 before it can be handed off to BTTB and how the others all successfully make it through. If there is any way you can have someone else run the traces also, perhaps if you have a friend in Dhaka, it would help a lot to show & prove to them their problem. Ask them to make the same traces from within their network as well as outside.
They may claim 1) That 220.127.116.11 and deep-c-links.com is a bad address. If they do, firmly inform them that this is 100% false and for them to view the site from outside their network (even via a proxy if necessary). 2) They may claim that you have a dns problem. Again that is false and you can prove it because with your traces your dns correctly resolves the galactica.polarwebservices.com server as well as the deep-c-links.com addesss. Any technician with remidial skills will be able to see the problem is in their network with those traces however so hopefully they won't give you a hard time. Please keep me informed as to what happens.
C:\Documents and Settings\Shetu>tracert deep-c-links.com
Tracing route to deep-c-links.com [18.104.22.168]
over a maximum of 30 hops:
1 670 ms 679 ms 695 ms 10.163.145.33
2 553 ms 719 ms 660 ms 10.163.145.34
3 539 ms 645 ms 509 ms 192.168.226.81
4 2544 ms 3041 ms 1143 ms 192.168.250.10
5 668 ms 695 ms 659 ms 10.10.205.14
6 1166 ms 659 ms 697 ms 22.214.171.124
7 520 ms 724 ms 720 ms 126.96.36.199
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.