Sat Aug 12 14:18:30 PDT 2000 — We will be shutting down our T3 to UUNet to migrate from the current SMDS link to a new point to point on our new SONET OC-12 fiber facility. The new circuit offers greater reliability, less latency and more room to grow. The SONET OC-12 fiber entrance is a full sized seven foot tall telco cabinet with fiber running at 655Mbps offering capacity to terminate twelve T3/DS3 45Mbps circuits or six T3/DS3 and one OC-3 155Mbps circuit. We will be provisioning four of the six T3 circuits here into the OC-12 in the next few weeks. The fiber is connected in a dual ring configuration with fiber leaving our building and going South on Third, and also East on 5th Streets. This prevents the possibility of a fiber cut taking Sonic.net’s huge data circuits offline. -Dane and Scott
Month: August 2000
Our T1 to our San Rafael POP went down again…
Fri Aug 11 11:30:06 PDT 2000 — Our T1 to our San Rafael POP went down again we rebooted the CSU/DSU and it came back up. Due to the fact this has happened 2 times in the past 4 days we are going to replace this hardware. Sorry for any problems this may have caused. -Steve
Our T1 to our San Rafael POP went down; a…
Wed Aug 9 12:03:46 PDT 2000 — Our T1 to our San Rafael POP went down; a quick reset of the CSU/DSU on the T1 fixed the issue. We’ll work with the equipment manufacturer to see if they have any ideas about what might have caused this, as it’s something we’ve seen a couple times before. Of course, all customers in all areas have at least two different dialup numbers available, see our POP finder in the support section of the home page to find your primary and backup phone numbers. Downtime was about four minutes. -Dane and Kelsey
We will be rebooting some of the dialup gear…
Wed Aug 9 16:48:33 PDT 2000 — We will be rebooting some of the dialup gear on the 707-522-1003 modem pool tomorrow in the early am (12:00am) this will cause some disconnects and may cause a few minutes of ‘ring no answer’. -Steve
A few minutes ago, Cable & Wireless suffered…
Sun Aug 6 00:28:43 PDT 2000 — A few minutes ago, Cable & Wireless suffered grave instability within their network, enough that we were going to shut down that T3. However, they recovered before the shutdown — downtime was two minutes. -Scott
BroadLink is having some network issues…
Sat Aug 5 13:31:30 PDT 2000 — BroadLink is having some network issues related to upgrades on their downtown facilities, and some customers are experiencing intermittent performance issues. BroadLink is working on the troubles. -Dane
Our T3 to Cable & Wireless went down…
Fri Aug 4 23:52:23 PDT 2000 — Our T3 to Cable & Wireless went down unexpectedly a few minutes ago. All traffic shifted to our UUNet T3, which was more than capable of handling the load. The circuit came back up at 23:58. I am attempting to contact CW’s NOC now, which is busy — I suspect we aren’t the only ones who saw a problem. -Scott
Our T3 to Cable & Wireless went down…
Fri Aug 4 00:10:32 PDT 2000 — Our T3 to Cable & Wireless went down unexpectedly a few minutes ago. All traffic shifted to our UUNet T3, which was more than capable of handling the load. The circuit came back up at 23:59. Cable and Wireless has no explanation for why the T3 went down. We have opened a medium-priority ticket to determine a reason for outage, which will include inspection of CW’s router to ensure it is operating properly. -Scott
UUNet’s latency and loss are all better, it…
Thu Aug 3 14:49:23 PDT 2000 — UUNet’s latency and loss are all better, it looks like it was just impact from the session clearing. They were unable to find a reason for the session clear on their end – it didn’t actually go down, but the BGP session cleared, probably due to loss of the heartbeat. There’s no indications on either end about why the heartbeat couldn’t make it, so we’ll call this an anomaly. -Dane
Our T3 to UUNet bounced a few minutes ago,…
Thu Aug 3 13:52:39 PDT 2000 — Our T3 to UUNet bounced a few minutes ago, causing some network slowdown. We’re currently seeing greater than average latency and packet loss on that link, and we are opening a trouble ticket with UUNet’s network operations center to get their feedback. -Dane and Scott