PDA

View Full Version : The site


BOAC
25th Jul 2010, 08:27
For Saab or any passing guru - for some time now I have had a 'slow' PPRune, requiring frequent refreshes at the 'waiting for ui.ibsrv.net' stage, and some functions eg 'Report this post' do not appear to complete.

What particular function is this call and any ideas why my system hangs there? I have a formidable anti-ad and flash armoury, but this happens on both FF and IE.. Win XP SP3, FF 3.6 and IE8.

Right now I am stuck on 'waiting for pprune.org'..........................

Parapunter
25th Jul 2010, 08:43
Not that I know much of anything, but that sounds like user interface Internet Brands server....net.

Maybe clear out cookies & log out & in again?

Rwy in Sight
25th Jul 2010, 09:06
Had the same issue yesterday early in the morning European time, using the WiFi at a Cafe. Now it seems it is not so much of an issue on cable connected modem.

I did not do anything special to correct it.


Rwy in Sight

BOAC
25th Jul 2010, 11:14
pp - yes, that is what it is, but I do not know why it hangs. Cookies/temp internets all tried several times with no effect.

RIS - mine too is 'sporadic', suggestive either of server limitations or a b/band bottleneck here, although other sites operate normally.

Saab Dastard
25th Jul 2010, 14:33
We mods notice it also, there are delays frequently reported to IB.

Please note that IB do a backup Wednesday night / Thursday morning, so expect delays around 08:00 GMT Thursday morning.

That excepted, if you experience significant delays, please can you let us know:

What url were you on?
What time did it occur?
What were you attempting to do when it occurred?
What did the error message say?
Did it go away when you attempted to refresh the page?
If it stuck around, for how long?

Use this thread to report problems.

Cheers

SD

BOAC
25th Jul 2010, 16:54
What url were you on? pprune.org
What time did it occur? most of the day
What were you attempting to do when it occurred? Post/edit/change pages etc
What did the error message say? No message, just 'waiting for' etc as above
Did it go away when you attempted to refresh the page? After several goes
If it stuck around, for how long? Sometimes until a browser reload.

BOAC
25th Jul 2010, 20:47
For interest - is that a great circle route to LA...............?

tracert pprune.org

Tracing route to pprune.org [67.201.16.181]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 192.168.177.1
2 34 ms 33 ms 33 ms lo99.lon-1-dsl.as9105.net [212.74.111.225]
3 35 ms 33 ms 35 ms Gi1-0-4-28.lon11.as9105.net [212.74.106.154]
4 34 ms 35 ms 35 ms xe-0-2-0-10.lon10.ip4.tinet.net [213.200.77.73]

5 105 ms 104 ms 104 ms xe-3-0-0.nyc32.ip4.tinet.net [89.149.184.198]
6 103 ms 102 ms 103 ms Te-3-4.car3.NewYork1.Level3.net [4.68.110.77]
7 103 ms 106 ms 108 ms vlan99.csw4.NewYork1.Level3.net [4.68.16.254]
8 103 ms 104 ms 105 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]

9 176 ms 175 ms 179 ms ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
10 182 ms 182 ms 182 ms ae-64-64.csw1.SanJose1.Level3.net [4.69.134.242]

11 183 ms 183 ms 193 ms ae-63-63.ebr3.SanJose1.Level3.net [4.69.134.225]

12 192 ms 184 ms 193 ms ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]

13 190 ms 183 ms 182 ms ae-2-70.edge3.LosAngeles1.Level3.net [4.69.144.7
3]
14 193 ms 184 ms 192 ms xe2-0.cr01.lax01.mzima.net [4.71.136.2]
15 190 ms 191 ms 190 ms 67.201.17.150
16 196 ms 200 ms 195 ms pprune.org [67.201.16.181]

Trace complete.

Saab - have you tried Googling ui.ibsrv.net? Looks as if others are having similar problems.

From another forum
I'm escalating this to our network guy who will take a look. I don't know why that sub-domain wouldn't be liked.

FWIW, ui.ibsrv.net is a static content server housed at the same place as the regular FT servers. There should be no difference between downloading from there.

Saab Dastard
25th Jul 2010, 21:13
Good to see you use a non-standard IP address for your home network! :)

I am consistently 160-165ms to pprune.org - the route is different, interestingly, being mzima.net all the way from "landfall" on the US side:

10 99 ms 107 ms 107 ms te1-3.cr01.iad01.us.mzima.net [69.174.120.97]
11 111 ms 110 ms 123 ms te1-3.cr01.atl01.us.mzima.net [69.174.120.53]
12 134 ms 143 ms 143 ms te0-1.cr01.dfw01.us.mzima.net [69.174.120.49]
13 192 ms 161 ms 161 ms te1-1.cr01.phx01.us.mzima.net [69.174.120.37]
14 171 ms 165 ms 176 ms te1-1.cr01.lax02.us.mzima.net [69.174.120.33]
15 166 ms 164 ms 163 ms 67.201.17.150
16 167 ms 165 ms 163 ms pprune.org [67.201.16.181]

That looks like Atlanta, Dallas, Phoenix, LA., so the southern route is quicker, at least for IP packets! ;)

I see frequent problems with static content and other kinds of servers that are linked to on a variety of websites. I just feel that they get hammered - it's a question of where you push the bottleneck to, I guess.

SD

mixture
28th Jul 2010, 13:16
That looks like Atlanta, Dallas, Phoenix, LA., so the southern route is quicker, at least for IP packets!

Probably due to the "Apollo" transatlantic route .... from their marketing speak "Apollo is the world's most advanced transatlantic submarine fibre optic cable system running from London to New York and Paris to Washington D.C. The Apollo system has the greatest capacity of any system in the Atlantic."

Means you end up with results similar to the below :

1 <1 ms <1 ms <1 ms **************************************
2 <1 ms <1 ms <1 ms **************************************
3 1 ms 1 ms 1 ms **************************************
4 1 ms 1 ms 1 ms ldn-bb2-link.telia.net [80.91.250.238]
5 76 ms 77 ms 77 ms ash-bb1-link.telia.net [80.91.246.68]
6 78 ms 77 ms 77 ms level3-113898-ash-bb1.telia.net [213.248.88.86]

7 82 ms 83 ms 79 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190]

8 77 ms 88 ms 90 ms ae-74-74.ebr4.Washington1.Level3.net [4.69.134.1
81]
9 155 ms 145 ms 145 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]

10 200 ms 145 ms 145 ms ae-1-60.edge3.LosAngeles1.Level3.net [4.69.144.9
]
11 145 ms 145 ms 157 ms xe2-0.cr01.lax01.mzima.net [4.71.136.2]
12 156 ms 156 ms 155 ms 67.201.17.150
13 156 ms 157 ms 156 ms pprune.org [67.201.16.181]

John Eacott
29th Jul 2010, 10:41
SD,

Do you think that IB are interested? It's like treacle most days from Australia:

Traceroute has started…

traceroute to www.pprune.org (67.201.16.181), 64 hops max, 52 byte packets
1 10.1.1.1 (10.1.1.1) 4.602 ms 2.878 ms 1.982 ms
2 loopback100.mflinbras08.mel.connect.com.au (210.8.1.243) 31.284 ms 31.928 ms 31.202 ms
3 ge9-1.mflindist02.aapt.net.au (202.10.13.6) 31.424 ms 29.924 ms 35.322 ms
4 * * *
5 te0-3-1-0.mburncore01.aapt.net.au (202.10.12.13) 47.096 ms 47.495 ms 46.886 ms
6 * te0-0-4-0.sclarcore01.aapt.net.au (202.10.10.74) 57.501 ms 52.203 ms
7 * te2-2.sclardist01.aapt.net.au (202.10.12.2) 51.691 ms 50.310 ms
8 * te2-1.sclarbrdr01.aapt.net.au (202.10.14.3) 51.532 ms 41.154 ms
9 xe7-0-0-320.sybr5.global-gateway.net.nz (202.50.238.213) 45.218 ms * 44.042 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 te0-1.cr1.lax1.us.packetexchange.net (69.174.120.85) 237.727 ms 257.041 ms *
16 te4-1.cr1.lax1.us.packetexchange.net (69.174.120.141) 225.227 ms 226.537 ms 228.442 ms
17 67.201.17.150 (67.201.17.150) 235.590 ms 234.399 ms 244.430 ms
18 pprune.org (67.201.16.181) 246.792 ms 236.360 ms 232.151 ms
19 * * *
20 * * *
21 pprune.org (67.201.16.181) 243.214 ms !H 249.002 ms !H 249.925 ms !H

:(

Saab Dastard
29th Jul 2010, 12:29
Do you think that IB are interested?

Honestly?

No.

If you were to highlight a significant delay over other IB co-located websites then possibly.

SD

mixture
29th Jul 2010, 13:30
John,

Your ISP is probably doing rate limiting and/or traffic shaping on its expensive international capacity.

Oceania is probably the most expensive civilised place to get data packets delivered to from the Western world. And,in relation to Australia, if you don't live in Sydney or Perth then you're paying for backhaul accross the desert. :ok: