From bob at tinkelman.com Tue Apr 14 10:45:33 2020 From: bob at tinkelman.com (Bob Tinkelman) Date: Tue, 14 Apr 2020 10:45:33 -0400 (EDT) Subject: [ispnet-announce] Performance problems Message-ID: <01RJP0RK4G0K8WYW1M@queens.tinkelman.com> A number of ISPnet customers started experiencing performance problems starting this morning, around 6:30 EDT. The symptoms are consistent with intermittent problems on one of the backbone links connecting ISPnet POPs. We expect that once we identify the problem link, we will be able to reroute traffic around the problem while getting the carrier to address the root cause. We will issue additional notices as we have additional information. -- Bob Tinkelman ISPnet, Inc. http://www.ispnet.net +1 (718) 464-4747 office +1 (800) 806-NETS toll free From bob at tinkelman.com Tue Apr 14 13:41:44 2020 From: bob at tinkelman.com (Bob Tinkelman) Date: Tue, 14 Apr 2020 13:41:44 -0400 (EDT) Subject: [ispnet-announce] Performance problems Message-ID: <01RJP6P4TIDU8WY7UO@queens.tinkelman.com> This email is an interim followup regarding the problem that hit around 6:30 this morning. We have identified the problem circuit. It turned out not to be a problem on one of our POP-to-POP backbone circuits, as we had first suspected, but instead a problem on a link to one of our major upstreams. In favor of notifying our customers sooner rather than later, I'm sending this email before we have had a chance to definitively confirm that the intermittent performance problems have cleared. Obviously, we will be monitoring the network closely. If you see problems, the same ones or new ones, please contact us via email or phone. Thanks - Bob Tinkelman > A number of ISPnet customers started experiencing performance > problems starting this morning, around 6:30 EDT. > The symptoms are consistent with intermittent problems on one of > the backbone links connecting ISPnet POPs. > We expect that once we identify the problem link, we will be able > to reroute traffic around the problem while getting the carrier > to address the root cause. > We will issue additional notices as we have additional information. > -- > Bob Tinkelman > ISPnet, Inc. http://www.ispnet.net > +1 (718) 464-4747 office > +1 (800) 806-NETS toll free From bob at ispnet.net Tue Apr 14 13:33:30 2020 From: bob at ispnet.net (Bob Tinkelman) Date: Tue, 14 Apr 2020 13:33:30 -0400 (EDT) Subject: [ispnet-announce] Performance problems In-Reply-To: "My own message dated Tue, 14 Apr 2020 10:45:33 -0400 (EDT)" <01RJP0RK4G0K8WYW1M@queens.tinkelman.com> Message-ID: <01RJP6OXPZJ08WY7UO@queens.tinkelman.com> This email is an interim followup regarding the problem that hit around 6:30 this morning. We have identified the problem circuit. It turned out not to be a problem on one of our POP-to-POP backbone circuits, as we had first suspected, but instead a problem on a link to one of our major upstreams. In favor of notifying our customers sooner rather than later, I'm sending this email before we have had a chance to definitively confirm that the intermittent performance problems have cleared. Obviously, we will be monitoring the network closely. If you see problems, the same ones or new ones, please contact us via email or phone. Thanks - Bob Tinkelman > A number of ISPnet customers started experiencing performance > problems starting this morning, around 6:30 EDT. > The symptoms are consistent with intermittent problems on one of > the backbone links connecting ISPnet POPs. > We expect that once we identify the problem link, we will be able > to reroute traffic around the problem while getting the carrier > to address the root cause. > We will issue additional notices as we have additional information. > -- > Bob Tinkelman > ISPnet, Inc. http://www.ispnet.net > +1 (718) 464-4747 office > +1 (800) 806-NETS toll free