Error 90000 (90k) and others relating to it

[Kazzera]

Looks like whatever this "iweb.com" datacenter is the one having the issues. Here's my pathping:

3 24ms 0/ 100 = 0% 0/ 100 = 0% te-9-1-ur01.longmont.co.denver.comcast.net [68.85.107.225]

4 25ms 0/ 100 = 0% 0/ 100 = 0% te-0-10-0-5-ar02.denver.co.denver.comcast.net [68.86.103.154]

5 28ms 0/ 100 = 0% 0/ 100 = 0% te-0-4-0-1-ar02.denver.co.denver.comcast.net [68.86.179.154]

6 29ms 0/ 100 = 0% 0/ 100 = 0% te-1-1-0-4-cr01.chicago.il.ibone.comcast.net [68.86.95.205]

7 30ms 0/ 100 = 0% 0/ 100 = 0% xe-4-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.82.178]

8 28ms 0/ 100 = 0% 0/ 100 = 0% 173.167.58.162

9 49ms 0/ 100 = 0% 0/ 100 = 0% if-4-0-1-0.tcore1.CT8-Chicago.as6453.net [209.58.57.130]

10 52ms 0/ 100 = 0% 0/ 100 = 0% if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]

11 76ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]

12 --- 100/ 100 =100% 95/ 100 = 95% 66.198.96.58

13 --- 100/ 100 =100% 95/ 100 = 95% te7-3.dr9.mtl.iweb.com [67.205.127.214]

14 75ms 6/ 100 = 6% 1/ 100 = 1% 72.55.128.44

15 78ms 5/ 100 = 5% 0/ 100 = 0% 184.107.107.176

Trace complete.

[Xruptor]

Looks like whatever this "iweb.com" datacenter is the one having the issues.

It sure seems that way. It can't be coincidence that everyone is getting massive data loss at those two hops.

12 --- 100/ 100 =100% 95/ 100 = 95% 66.198.96.58

13 --- 100/ 100 =100% 95/ 100 = 95% te7-3.dr9.mtl.iweb.com [67.205.127.214]