[qasdfdsaq]

This is exactly the kind of idiotic far fetched speculation that's ******** me off these days.

You have slow access to Tesco. Other people have a bump on their ping charts. They have nothing to do with each other.

You see one bump now. You saw another bump a few weeks ago. Again, they have nothing to do with each other.

You complain of congestion on VM's core network yet somehow nobody else has seen it and all you can demonstrate is congestion in your local area. They have nothing to do with each other.

The ping bumps everyone is seeing has nothing to do with you, your Tesco shopping speeds, or anything in your area.

Basic network troubleshooting 101:


What is the problem?
High latency

What is it affecting?
Traffic from A to B

Is it affecting anything else going to or from A?
No

Is it affecting anything else going to or from B?
No

Is it affecting anything else going through a common midpoint between A and B?
No

Conclusion:
The problem is localized and probably specific to traffic between A and B.


This ping spike has nothing to do with Speedtest, nothing to do with AMS-IX, nothing to do with previous problems with Atroto, nothing to do with Manchester core and nothing to do with link speed. I don't give a rats arse if pigs are chewing up the cables in Amsterdam or sabotaging VM, they have nothing to do with the issue being discussed. Quit clutching at straws and stop banging on about irrelevant stuff that has nothing to the issue at hand.

Oh and some basic logic on the stuff you've come up with:

You say previously VM confirmed there was a port overloaded due to Atroto traffic.

Are any the symptoms the same as the previous incident with Atroto?
No.

Conclusion: It is not the same problem

You say something about a port being overloaded in a way that affects speedtests but not pings.

Does the problem affect pings?
Yes

Conclusion: It is not the same problem

You say you've seen multiple times congestion on VM's core network.

Is the problem affecting anything else on VM's core network?
No

Conclusion: The problem is not with VM's core network.

You say you have contacts with other ISPs that can inform you if their peering point is saturated or not.

Is the problem affecting anything going through a peering point with another ISP?
No

Conclusion: That has nothing to do with the problem.

You say moving traffic from AMS-IX in the past has caused your speed to quadruple in the past.

Is the problem anything to do with your speed?
No

Does the problem affect anything going through AMX-IX in any way shape or form?
No

Does the problem solely affect traffic not going through AMS-IX?
Yes

Conclusion: That has nothing to do with the problem.

You say something about Manchester connectivity and performance issues there.

Does the problem affect any other traffic going to, from or through Manchester?
No

Does the problem affect any traffic not going through Manchester?
Yes

Is there any difference in the problem's effects between traffic going through and not going through Manchester?
No

Conclusion: That has nothing to do with the problem.

You say something about large shared pipes not showing issues on ping data until its pretty much saturated, and it could be running at 99% without you seeing any ping spikes.

Is the problem a ping spike?
Yes

Conclusion: That has nothing to do with the problem.