Tracking Down problem with PTCL

Hi All,

We would really appreciate it if you can help us in resolving an issue. We are using a server based in the network of 213.248.123.92 , but PTCL (our ISP) did something recently and we are encountering very high latency. Can anyone please tracert 213.248.123.92 and post results here.

Thank you.

You've posted this everywhere EXCEPT under PTCL's section

[quote=", post:, topic:"]

You’ve posted this everywhere EXCEPT under PTCL’s section
[/quote]

Yes, because we KNOW it’s a PTCL issue - this FACT has been established. We have TWO PTCL broadband connections, and both have the same issue. We are now trying to find out if this is ALSO an issue with other ISPs.

[quote=", post:, topic:"]

Yes, because we KNOW it’s a PTCL issue - this FACT has been established. We have TWO PTCL broadband connections, and both have the same issue. We are now trying to find out if this is ALSO an issue with other ISPs.

[/quote]

Neo_x If you need help then you should post it in the right section.

as there are separate sections for each ISP, i see that you also posted it in LDN section, and i think you done it by mistake or you are blind :D

i have problem trace routing your server from my server which is in france meaning that it could be a routing issue with your host

heres the trace route

traceroute 213.248.123.92

traceroute to 213.248.123.92 (213.248.123.92), 30 hops max, 40 byte packets

1 rbx-53-m1.routers.ovh.net (91.121.173.253) 0.529 ms 0.509 ms 0.627 ms

2 91.121.130.1 (91.121.130.1) 2.752 ms * *

3 160g.gsw-1-6k.routers.chtix.eu (213.186.32.225) 4.251 ms * *

4 30g.gblx.gsw-1-6k.routers.chtix.eu (213.186.32.129) 138.925 ms 138.660 ms 138.757 ms

5 prs-b4-link.telia.net (213.248.98.121) 12.673 ms 12.658 ms 12.636 ms

6 prs-bb2-link.telia.net (80.91.251.44) 4.391 ms prs-bb1-link.telia.net (80.91.251.46) 14.482 ms prs-bb2-link.telia.net (80.91.251.44) 4.232 ms

7 ffm-bb1-link.telia.net (80.91.252.230) 17.006 ms 16.950 ms ffm-bb2-link.telia.net (80.91.251.213) 17.598 ms

8 s-bb1-link.telia.net (80.239.147.173) 32.509 ms s-bb2-link.telia.net (80.91.251.146) 30.125 ms s-bb2-link.telia.net (80.239.147.177) 34.399 ms

9 s-b1-link.telia.net (80.91.252.69) 32.660 ms s-b1-link.telia.net (80.91.253.228) 30.139 ms s-b1-link.telia.net (80.91.254.57) 32.801 ms

10 s-hdn-i3-link.telia.net (80.91.251.245) 221.004 ms 220.619 ms 220.748 ms

11 * * *

12 * * *

13 * * *

14 * * *

15 * * *

16 * * *

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 * * *

30 * * *

i think the server is down

cuz mine also stopped at the same place where ruhaan's stopped..

[quote=", post:, topic:"]

i have problem trace routing your server from my server which is in france meaning that it could be a routing issue with your host

heres the trace route

[/quote]

Thank you very much, for this (first) constructive post in the thread. Basically, we need people in Pakistan with Pakistani ISPs to submit tracereports. We have a number of servers in the UK/US/AU, and have direct access using SSH. We know there isn’t an issue with this particular IP from other places in the world. PTCL has been doing some work on the backend (peering with TWA etc), so we suspect this has got something to do with the really bad latency we are having on this route. The hops where you are timing out, is supposed to be like this to hide the traceroute for security purposes. We are only interested in when we get to the telia network. Here is how it looks like when we have lag:

Tracing route to 213-248-123-92.customer.teliacarrier.com [213.248.123.92]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.2.1

2 25 ms 30 ms 34 ms 119.152.24.1

3 27 ms 21 ms 19 ms 203.99.170.186

4 22 ms 21 ms 20 ms rwp44.pie.net.pk [221.120.252.1]

5 51 ms 50 ms 50 ms khi275-P01-pie.net.pk [221.120.254.22]

6 54 ms 50 ms 49 ms static.khi77.pie.net.pk [202.125.128.179]

7 50 ms 49 ms 50 ms khi-drni02-gw2.pie.net.pk [221.120.250.254]

8 169 ms 170 ms 171 ms gigabitethernet5-0.108.gw3.par2.alter.net [194.98.63.141]

9 168 ms 167 ms 168 ms so-3-0-0.XT1.PAR2.ALTER.NET [146.188.9.25]

10 174 ms 173 ms 173 ms POS0-0.BR1.PAR2.ALTER.NET [146.188.2.5] <---- (lag starts on the next hop- keeps on increasing, since the rest of the nodes are hidden, you can’t see that it gets to 700ms eventually)

11 302 ms 303 ms 301 ms prs-b1-link.telia.net [213.248.100.125] <----

12 297 ms 296 ms 297 ms prs-bb2-link.telia.net [80.91.250.250]

13 317 ms 318 ms 316 ms ffm-bb2-link.telia.net [80.91.249.46]

14 338 ms 340 ms 339 ms s-bb2-link.telia.net [80.91.248.58]

15 341 ms 340 ms 327 ms s-b1-link.telia.net [80.91.254.113]

16 344 ms 344 ms 344 ms s-hdn-i3-link.telia.net [80.91.249.69]

17 * * ^C

Here is how it looks like when we DON’T have lag (max 280-320 ms):

Tracing route to 213-248-123-92.customer.teliacarrier.com [213.248.123.92]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.2.1

2 24 ms 29 ms 40 ms 116.71.160.1

3 21 ms 21 ms 20 ms 203.99.170.186

4 21 ms 21 ms 22 ms rwp44.pie.net.pk [221.120.252.1]

5 50 ms 49 ms 49 ms khi275-P01-pie.net.pk [221.120.254.22]

6 45 ms 44 ms 44 ms static.khi77.pie.net.pk [202.125.128.179]

7 45 ms 45 ms 46 ms khi-drni02-gw2.pie.net.pk [221.120.250.254]

8 173 ms 172 ms 173 ms gigabitethernet5-0.108.gw3.par2.alter.net [194.98.63.141]

9 168 ms 166 ms 167 ms so-4-1-0.XT1.PAR2.ALTER.NET [212.157.176.9]

10 168 ms 168 ms 167 ms POS0-0.BR1.PAR2.ALTER.NET [146.188.2.5]

11 172 ms 172 ms 172 ms prs-b1-link.telia.net [213.248.100.125]

12 178 ms 178 ms 178 ms prs-bb1-link.telia.net [80.91.250.254]

13 188 ms 187 ms 189 ms ffm-bb1-link.telia.net [80.91.254.204]

14 217 ms 211 ms 212 ms s-bb1-link.telia.net [80.91.251.144]

15 212 ms 212 ms 213 ms s-b1-link.telia.net [80.91.252.69]

16 214 ms 228 ms 218 ms s-hdn-i3-link.telia.net [80.91.251.245]

17 ^C

We’ve analysed the situation and found out that it has got to do something with ALTER.NET (PIPEX-UUNET/UK) and TELIA not liking each other. I am not sure when PTCL moved to ALTER.NET as their carrier, but we are really stuffed if the situation doesn’t resolve soon.

Would appreciate any help - thanks.

^I dont think it's some thing unlikeness between alter.net and telia.

if you've clearly seen the trace provided by ruhaan, that was from france. and that route is not via ALTER.NET. infect I tested it from my UK and US servers their route was not via ALTER.NET as well but trace response when connecting to TELIA is somewhat same and also some times smooth as your second one on random basis even when connecting from some other than ALTER.NET

I dont see any thing constant with it. this could be just temporary lag, seems to me.

and yes request time out can be because of security reasons.

[quote=", post:, topic:"]

^I dont think it’s some thing unlikeness between alter.net and telia.

if you’ve clearly seen the trace provided by ruhaan, that was from france. and that route is not via ALTER.NET. infect I tested it from my UK and US servers their route was not via ALTER.NET as well but trace response when connecting to TELIA is somewhat same and also some times smooth as your second one on random basis even when connecting from some other than ALTER.NET

I dont see any thing constant with it. this could be just temporary lag, seems to me.

and yes request time out can be because of security reasons.

[/quote]

I am not sure what was not clear in my (very) detailed post about having issues with PTCL, a pakistani DSL provider. If you do not have a DSL provider OTHER than PTCL, your post will not be very useful for us. In fact, we do not want people submitting traceroutes to the IP in question from ANYWHERE in the world except Pakistan (and NOT from PTCL DSL).

PTCL uses different peering/carriers for routing bandwidth to various places in world. E.g. when tracerouting to www.yahoo.com, PTCL uses TELECOM ITALIA (SEABONE). Before the 26th of July, everything was ok w.r.t. latency with our server from Pakistan (using PTCL DSL). After 26th of July, something :

1. Changed in PTCLs communications infrastructure

or

2. Changed in ALTER.NET routing path

^and I am not sure if I couldn't make you understand the similarities and differences with the ISPs what I got other than PTCL.

any ways.

here it is what do u want.

image replaced

trace.jpg

[quote=", post:, topic:"]

[/quote]

And what ISP is this, pray tell ?

^I am sorry image updated (that was wrong to quest)

and the traces are from Nexlinx

Thanks a lot Bellskar. Really stumped at whats going on. We've rebooted our router countless times now, getting different routes to telia like you - but none of them had less than 350ms and above. You've had many routes where you had less than 174ms on different routes. You've had at least one route (s0-04/P0S7) where you had higher lag. But it looks as if nexlinx has better routing in general. If we can get confirmation of this behaviour from some other ISPs, we can make an informed decision to switch ISPs.

^my pleasure.