Author: admin

Tue Aug 1 09:18:25 PDT 2000 — This is a test entry. — test — test. -Kelsey

Tue Aug 1 15:49:32 PDT 2000 — The path on CW’s (Cable and Wireless’) network that was exhibiting high latency and packet loss is fine now. We are still awaiting a call from CW to see if this was the same problem we resolved earlier this morning. -Scott

Tue Aug 1 15:12:51 PDT 2000 — While checking paths to various networks today, we discovered another (little-used) path on CW’s network that is showing high latency and packet loss. We have pointed out the problem to CW, and expect a resolution shortly. -Steve, Nathan, Scott

Tue Aug 1 02:07:25 PDT 2000 — Latency and packet loss issue on CW’s network solved. As it turns out, traffic bound for our network from the PAIX router was taking a secondary route to reach us. CW engineers fixed the routing problem by moving our traffic to a more direct circuit. They are now investigating why the other path had a problem — but as far as we are concerned, the problem is resolved. -Scott

Mon Jul 31 23:48:34 PDT 2000 — CW’s NOC is still troubleshooting the packet loss and latency within their network. To facilitate that, I’ve shut down the UUNet circuit. The loss appears to be on one link — an OC3 — which is connected to their Palo Alto Internet Exchange router. There, CW peers with several ISP’s, including Verio. Connectivity to CW’s PAIX peers, will be intermittent and sporadic as we track down this problem. -Scott

Mon Jul 31 20:26:37 PDT 2000 — CW security has confirmed that the packet loss and latency within their network is not a DoS attack. CW’s NOC is troubleshooting. -Scott

Mon Jul 31 19:27:08 PDT 2000 — UUNet has solved the packet loss and latency trouble within their network. They did this by rebooting the OC12 interface on their Cisco 7500 (which doesn’t let know what the problem was, but at least it’s fixed). I just spoke with CW’s NOC, and they are investigating the problem in their network from both a technical and security perspective. Updates as they come in… -Scott

Mon Jul 31 18:55:11 PDT 2000 — More net latency and packet loss. We also found a UUNet link that exhibits high latency and packet loss. Nathan was able to correlate the beginning of the high latency on this link with Sunday morning’s DoS attack. It is possible (though we don’t know yet) that this is an ongoing DoS attack that is being filtered at both CW and UUNet’s border routers. (The traffic is not making it to Sonic.net.) However, we just got off the phone with UUNet security, who says that the DoS would have to be filling an OC12 (the equivalent of 12 T3’s) to be causing this problem — unlikely, but they are checking that out.

Another correlation: the packet loss and latency are manifesting themselves on routers that are directly connected to exchange points, even though the traffic doesn’t necessarily traverse the exchange points. UUNet is also investigating this on their end now. We are still waiting for a call from CW. -Scott, Nathan, Kelsey, Steve

Mon Jul 31 17:01:11 PDT 2000 — Net slowness through the Palo Alto Internet Exchange. We are seeing intermittent high latency and packet loss for some sites we reach across Cable and Wireless. We characterized the problem (a saturated link on CW’s network), and CW is working on it. -Scott

Sun Jul 30 03:37:00 PDT 2000 — Denial of Service attack. Sonic.net suffered a Denial of Service attack this morning that consumed all inbound bandwidth of one of our network providers. The network provider’s security force _almost_ had the attack traced to the source, when the attack stopped. Both they and we are monitoring the situation. -Scott