Cable Forum - View Single Post - 50M Think Broadband Ping Monitor Results (POST YOURS)

Chrysalis · 07-11-2012, 10:07

qas I dont know the nature of your testing, you seem to be saying you somehow are able to test specific VM ports. Also that VMs core network has no problems, what exclusive access do you have to determine that?

What I can tell you is the following.

VM confirmed themselves that at least one port was overloaded in the previous instance, they had overloaded it with atroto traffic, when they rerouted that traffic temporarily graphs went back to normal, yet your testing determined there was no such overload. So maybe VM were wrong also?

I have done my own testing using speedtests, as a port overload can slow down speeds without affecting pings, I can affect speeds by rerouting my own traffic and then looking at routes taken for that traffic to determine where congestion is, yes i cannot determine the exact point but I also test with multiple isp's which gives me a reasonable guess.

I have multiple times in the past seen what looks like congestion on VMs core network, the CEO office themselves have even told me of core network issues near my area that they have said have caused me problems. Granted they could have been fobbing me off.

I also have contacts with several isp's they can inform me if their peering point with VM is saturated or not, I have these contacts as I do work for them or have done work for them in the past.

eg. I have had traffic moved from AMS-IX peering point to telia transit and the speed quadrupled (not maxed out tho). The src isp however doesnt have issues sending over AMS-IX to other uk isp's.

Do you also believe there to be no issues in manchester VM connectivity, craig himself has even picked up the performance issues in that area.

Generally when the shared pipe is large eg. 10gigabit, then issues wont show on ping data until its pretty much saturated, it can be at 99% and you will see very little in terms of ping spikes. Its not like a UBR port where it can spike at say 60%.

Now I am trying to understand what you are saying, are you saying you think the local network to tbb has its own congestion, yet that congestion just happens to be affecting VM alone, maybe tbb are sabotaging VM? is that in your thoughts?

07-11-2012, 10:07	#2613
Chrysalis cf.mega poster Join Date: Sep 2003 Posts: 12,047	Re: Think Broadband Ping Monitor Results (POST YOURS) qas I dont know the nature of your testing, you seem to be saying you somehow are able to test specific VM ports. Also that VMs core network has no problems, what exclusive access do you have to determine that? What I can tell you is the following. VM confirmed themselves that at least one port was overloaded in the previous instance, they had overloaded it with atroto traffic, when they rerouted that traffic temporarily graphs went back to normal, yet your testing determined there was no such overload. So maybe VM were wrong also? I have done my own testing using speedtests, as a port overload can slow down speeds without affecting pings, I can affect speeds by rerouting my own traffic and then looking at routes taken for that traffic to determine where congestion is, yes i cannot determine the exact point but I also test with multiple isp's which gives me a reasonable guess. I have multiple times in the past seen what looks like congestion on VMs core network, the CEO office themselves have even told me of core network issues near my area that they have said have caused me problems. Granted they could have been fobbing me off. I also have contacts with several isp's they can inform me if their peering point with VM is saturated or not, I have these contacts as I do work for them or have done work for them in the past. eg. I have had traffic moved from AMS-IX peering point to telia transit and the speed quadrupled (not maxed out tho). The src isp however doesnt have issues sending over AMS-IX to other uk isp's. Do you also believe there to be no issues in manchester VM connectivity, craig himself has even picked up the performance issues in that area. Generally when the shared pipe is large eg. 10gigabit, then issues wont show on ping data until its pretty much saturated, it can be at 99% and you will see very little in terms of ping spikes. Its not like a UBR port where it can spike at say 60%. Now I am trying to understand what you are saying, are you saying you think the local network to tbb has its own congestion, yet that congestion just happens to be affecting VM alone, maybe tbb are sabotaging VM? is that in your thoughts?