Quote:
Originally Posted by Chrysalis
I do know all the previous bumps had negative affect on my services tho. I remember you saying last time as well you seem to mysteriously think it only affected tbb and you was wrong.
|
The previous bump was a problem with their capacity on paths through LINX and could be clearly seen affecting many different routes to VM via LINX.
The current bump didn't affect any of the 5 LINX paths I tested, or two private peering paths. That largely rules out a generic problem through LINX.
That leaves two possibilities, a problem specific to TBB or a problem affecting VM's network in general. Since zero out of 7 paths into VM were affected, that rules out a generic VM problem. That leaves one possibility.
I'm yet to see any evidence it affected anything other than TBB, so if you have anything sensible to suggest to the contrary, please do.
Quote:
Originally Posted by Chrysalis
Do you think VM dedicate a port just for tbb traffic?
|
What evidence do you have that the fault lies with a port on VM?
---------- Post added at 09:41 ---------- Previous post was at 09:32 ----------
Quote:
Originally Posted by Chrysalis
bear in mind I did that tracert after the bump ended for your post request.
|
Seeing as the ping monitors go through LINX and your Tesco traffic does not, unless there's a generic problem with VM's core network (which there isn't) problems with the two are completely unrelated.