Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tuftedduck]

It is still very slow for me, and I am still getting these error reports...

[UncleUB]

It is still very slow for me, and I am still getting these error reports...

Its fine for me TD......could this be an Opera 10.50 problem?

Have you tried using another browser?

[tuftedduck]

@ unkyUb.

I don't know what the trouble is. It may be the browser, or my system, or virgin.net, or the router, or the phone line.

I only know two things :-
1) It only happens on this site.
2) I am too old and tired to hassle around trying to find a fix.

I keep my posting on here to a minimum.

[silversurfer44]

Tuftedduck if it is only this site that is affected then it could well be a script that is not completing. Have you tried refreshing the cache? It may well be something in there. Tired you may be and feeling a bit down, but never think you are too old. Chin Up.

[tuftedduck]

@ ss44..........I don't think it is the cache..I have that set to clear on browser shutdown and am in and out of the browser frequently. I doubt if the cache gets anywhere near full, but have tweaked the settings in there to make the cache more commodious....will see.

I have, however, just seen this this on the virgin.media webbie.....maybe something to do with the prob.

[silversurfer44]

Yes I see what you mean. The only other thing I can think of is the domain name server for Virgin is suffering stress. Unfortunately there is not a lot you can do but see if it improves. Let's hope so as it really is downer when things like this happen.
 

[kitz]

The server this site resides on is actually one of the fastest in the UK, with the most uptodate equipment on it and costs thousands of pounds just for the processors before starting on anything else.

The problems the other week were DDoS attempts on the server 2 hops before mine. (core.misp).  This should be resolved.

This morning was a one off & Vidahost sent me that notification out before I'd even enquired about it.  They are normally pretty damn good and if the fault is with them, they will generally hold their hands up.

Ive just performed a test and its maxing out my connection @ 2.6 MB/Sec (20.8Mbps).
Someone a couple of days ago tested from an educational location and was able to download at 20MB/Sec which was about their limit.

You may be able to identify where any packet loss or slowness is occurring by doing a tracert, as the problem could be anywhere between your home and the site.

[kitz]

hmmm  that notification from virgin doesnt look too good    

A year or so back Virgin went through a similar thing not having enough centrals (BAMs),
That notification would seem to indicate that they havent purchased enough bandwidth for the amount of customers that they have.

Is it only this site?   Could be a routing link or peer point problem.  If you are seeing any slowness, doing a tracert is often a good place to start and may show exactly where the problem is ocuring.

[UncleUB]

Don't really understand it,but here is the tracert I have done.
 

Tracing route to www-fmt.bbc.net.uk [212.58.246.159]
over a maximum of 30 hops:

  1    71 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    26 ms    26 ms    25 ms  93-126-245-83.packetexchange.net [83.245.126.93]

  5    28 ms    26 ms    26 ms  212.58.238.129
  6    28 ms    24 ms    23 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  7    27 ms    27 ms    28 ms  212.58.255.12
  8    24 ms    22 ms    22 ms  fmt-vip02.cwwtf.bbc.co.uk [212.58.246.159]

Trace complete.

[kitz]

Yours is looking very good UB considering your line is interleaved.   It means that data between you and the BBC is transferred in 22 milliseconds.

Hops 2 + 3 hardly ever show up on Be's own network - so dont worry about those.
Hop1 (your router) is high but thats an anomaly of the ST/Thompson routers and they all do that.  It doesnt actually affect throughput and can be ignored.

[UncleUB]

Yours is looking very good UB considering your line is interleaved.   It means that data between you and the BBC is transferred in 22 milliseconds.

 

Thanks Kitz 

Don't really understand all the jargon,but if you say its good....that will do for me.   

[oldfogy]

Just in case any one had problems.....

VM cable was down for about 30 minutes in the early hours of this morning. (About 01:30)

[tuftedduck]

 

[roseway]

Those figures aren't terribly good, TD, but a delay of 50 ms isn't going to have any noticeable effect on your normal internet activities (assuming that you're not an online arcade games player )

It rather looks as though the VM hops may be adding a bit more delay than they should, but it's nothing to worry about.

[waltergmw]

Hi TD and Eric,

I thought you might like to see how the Virgin 20 Mbps service performs now in sunny Surrey !

Kind regards,
Walter

Traceroute has started…

traceroute to 188.65.112.30 (188.65.112.30), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  1.415 ms  1.107 ms  1.093 ms
 2  glfd-cmts-05-lback-20.network.virginmedia.net (xxx.xxx.xxx.xxx)  9.561 ms  10.601 ms  11.926 ms
 3  glfd-core-1a-ge-300-1637.network.virginmedia.net (62.254.207.89)  11.922 ms  12.482 ms  10.910 ms
 4  glfd-bb-1a-ge-200-0.network.virginmedia.net (213.105.175.85)  12.038 ms  10.367 ms  12.072 ms
 5  nrth-bb-1b-ae4-0.network.virginmedia.net (212.43.163.178)  15.152 ms  11.836 ms  11.993 ms
 6  tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2)  14.168 ms  16.964 ms  15.915 ms
 7  114-14-250-212.static.virginmedia.com (212.250.14.114)  74.978 ms  17.054 ms  16.034 ms
 8  213.133.130.78 (213.133.130.78)  16.063 ms  16.275 ms  15.988 ms
 9  euroconnex-1.br1.core.misp.co.uk (217.112.86.107)  16.691 ms  17.237 ms  15.889 ms
10  ge-1-377.captain.core.misp.co.uk (91.198.165.5)  16.543 ms  21.744 ms  19.907 ms
11  * * *
12  * * *
13  * * *
14  * * *



PING 188.65.112.30 (188.65.112.30): 56 data bytes
64 bytes from 188.65.112.30: icmp_seq=0 ttl=51 time=20.619 ms
64 bytes from 188.65.112.30: icmp_seq=1 ttl=51 time=20.148 ms
64 bytes from 188.65.112.30: icmp_seq=2 ttl=51 time=20.425 ms
64 bytes from 188.65.112.30: icmp_seq=3 ttl=51 time=20.134 ms
64 bytes from 188.65.112.30: icmp_seq=4 ttl=51 time=20.527 ms
64 bytes from 188.65.112.30: icmp_seq=5 ttl=51 time=18.123 ms
64 bytes from 188.65.112.30: icmp_seq=6 ttl=51 time=18.488 ms
64 bytes from 188.65.112.30: icmp_seq=7 ttl=51 time=18.356 ms
64 bytes from 188.65.112.30: icmp_seq=8 ttl=51 time=18.208 ms
64 bytes from 188.65.112.30: icmp_seq=9 ttl=51 time=18.363 ms

--- 188.65.112.30 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.123/19.339/20.619/1.045 ms