Submission + - Major problems withSprintlink backbone in chicago
An anonymous reader writes: It seems that sprint's backbone in Chicago has been causing havoc for ISPs all over the region today, with packet loss currently at 50%-80% and average ping times at 1700ms. We noticed a problem with this backbone last week, for a short time with pings taking over 2000ms. We awoke this morning to an internet connection that was able to open Google and CNN but little else. A quick trace route and call to our ISP confirmed our thoughts that sprint's Chicago backone was having major issues. The problems seemed to be correcting themselves this afternoon, as packet loss what down and ping times were closer to noral. However again this evening packet loss has sky rocketed and service over the backbone is again degraded. Below is an portion of the output from mtr for anyone in doubt of where the issue lies.
3. sl-gw18-chi-6-1-0.sprintlink.net 0.0% 11.2 11.5 10.6 13.7 1.0
4. sl-bb22-chi-1-0.sprintlink.net 66.7% 1761. 1692. 1624. 1761. 96.9
5. sl-st21-chi-13-0.sprintlink.net 66.7% 2705. 2592. 2478. 2705. 160.5
6. ggr3-p330.cgcil.ip.att.net 83.3% 2752. 2752. 2752. 2752. 0.0
3. sl-gw18-chi-6-1-0.sprintlink.net 0.0% 11.2 11.5 10.6 13.7 1.0
4. sl-bb22-chi-1-0.sprintlink.net 66.7% 1761. 1692. 1624. 1761. 96.9
5. sl-st21-chi-13-0.sprintlink.net 66.7% 2705. 2592. 2478. 2705. 160.5
6. ggr3-p330.cgcil.ip.att.net 83.3% 2752. 2752. 2752. 2752. 0.0