Error code 2002 and 90000

[Raist]

I thought I was seeing issues there, but it turns out it is just an anti-DDoS feature. Want the MTR I am running right now?

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|          Wireless_Broadband_Router.home -    1 | 1060 | 1058 |    0 |    4 |  473 |    2 |

|lo0-100.PRVDRI-VFTTP-306.verizon-gni.net -    0 | 1068 | 1068 |    4 |   10 |  428 |    6 |

|  T0-2-0-9.PRVDRI-LCR-22.verizon-gni.net -    0 | 1068 | 1068 |    4 |   10 |  422 |    8 |

|  xe-1-0-8-0.BOS-BB-RTR2.verizon-gni.net -    0 | 1068 | 1068 |    6 |   24 |  428 |    7 |

|xe-4-1-0-0.NY325-BB-RTR2.verizon-gni.net -    0 | 1068 | 1068 |   17 |   27 |  461 |   21 |

|                0.ae7.BR1.NYC1.ALTER.NET -    0 | 1068 | 1068 |   15 |   21 |  410 |   17 |

|                   No response from host -  100 |  213 |    0 |    0 |    0 |    0 |    0 |

|      ae-11-11.car2.Montreal2.Level3.net -    1 | 1053 | 1049 |   56 |   89 |  652 |  108 |

|      ae-11-11.car2.Montreal2.Level3.net -    1 | 1052 | 1048 |   56 |   89 |  620 |  270 |

|   ORMUCO-COMM.car2.Montreal2.Level3.net -    1 | 1041 | 1034 |   56 |   63 |  534 |   60 |

|                            192.34.76.10 -   13 |  719 |  632 |   68 |   78 |  534 |   72 |

|                          199.91.189.242 -   15 |  682 |  585 |    0 |   78 |  492 |   74 |

|                           199.91.189.33 -   17 |  645 |  539 |    0 |   81 |  503 |   75 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

O M G.

It is staring us right in the face. Practically screaming at you.

Even if you want to write off the massive lag spike and lost packets on your local network (which you shouldn't--it is after all the first link in the chain and can affect everything after)...it looks like jitter may be on the high side with Verizon. Then it goes bonkers at Level3.

Based on the data you have presented, you appear to have networking issues that would have an impact on the most perfectly tuned server.

Even if the 600+ spikes were a once-only fluke spike at each of those hops, Level3 is running 56 to 108 with an average of 89 on one hop, and then 56 to 27-0 with an average of 89 at another. That is NOT acceptable. And imagine that... it is LEvel3's car2 hops in Montreal---notorious for being flakey as all get out. They get reported continuously all over the place for a variety of service issues.

Verizon is keeping you on that troubled route. They can take you off of it, just like Time Warner does for me on a regular basis... as demonstrated in the edit I made in my previous post.

[Alexika]

O M G.

It is staring us right in the face. Practically screaming at you.

Even if you want to write off the massive lag spike and lost packets on your local network (which you shouldn't--it is after all the first link in the chain and can affect everything after)...it looks like jitter may be on the high side with Verizon. Then it goes bonkers at Level3.

Based on the data you have presented, you appear to have networking issues that would have an impact on the most perfectly tuned server.

I fix cars not networks. You might as well speak in Egyptian, because that would mean more to me than anything you just said. Who has networking issues? What kind of issues? How did you determine that? What the heck is jitter? How do I get that fixed? What do I say to the monkey on the phone at Verizon to get them to stop blowing me off?