eagleAccess Plans • eagle Highspeed • eagle webMail • eMail Filters • Account Renewals

• • • • •

Network Reports

Tuesday October 18, 2010 - 3:50 p.m. - Our primary Internet connection faild at aprox. 2:50 p.m. due to a configuration error in the phone company's network.  The problem was reported to the phone company within minutes and resolved at 3:45 p.m.

• • • • •

Monday September 6, 2010 - 3:40 p.m. - Our primary Internet connection went "down" at aprox. 1:40 p.m. due to a router failure in Toronto.  Our upstream provider was made aware of the situation immediately and restored the connection at aprox. 3:20 p.m.  They are currently trying to establish the cause of hardware failure. During the outage dialup customers would have lost Internet connectivity, while DSL customers may have had difficulty connecting and sending/receiving email.

• • • • •

Sunday September 5, 2010 - 4:00 p.m. - Unexpected maintenance on our eagle.ca mail server will occur this evening at 8:00 p.m. It is anticipated that the maintenance will take two hours.  During this time clients will not be able to send or receive email.

• • • • •

Friday October 23, 2009 - 3:45 p.m. - At aprox. 1:15 Friday afternoon we began noticing significant packet loss with our Internet connection.

Upon investigation we determined that the issue was wide spread through out Bell Canada's network in central and eastern Ontario.

Multiple ISPs who interconnect with Bell at 151 Front Street in Toronto alerted Bell's support staff of the intermittent problem.

The problem affected dedicated connections as well as residential and business DSL services.

While Bell has yet to issue a formal report, technicians have noted that the problem was in Bell's optical Ethernet network. A broadcast storm created by a faulty port in a Nortel Passport 8600 switch was the most likely cause. Once the card in question was eliminated the problem was resolved.

This was one of a series of intermittent failures Bell data customers have experienced in the last two weeks. This is the first that has had a noticeable impact on eagle.ca connections.

• • • • •

Sunday July 12 - 9:00 a.m. -  At 6:10 a.m. our Internet connection went "down". A trouble ticket was opened with the phone company. At 8:56 a.m. the connection was restored. A sub-interface on phone company equipment was reset by a phone company technician to restore connectivity. The root cause of the problem is not known.

• • • • •

Sunday January 18, 2009 - At aprox. 2:35 a.m. our primary Internet connection went down. Several unsuccessful troubleshooting steps were undertaken at our location in Cobourg and at our upstream location in Toronto. 

A trouble ticket was opened with the phone company at 5:15 a.m. By 9:30 a.m. the trouble had been isolated to phone company equipment in Toronto. Several attempts to reconfigure the equipment failed and when a reconfiguration was finally successful restarts of equipment at the phone company's central office in Cobourg and one in Toronto were necessary to re-establish the connection.

As of 10:35 a.m. traffic to and from the Internet was flowing again.

During the outage, dialup customers would not have had access to the Internet. Business high-speed customers and residential high-speed who were online when the problem occurred maintained Internet access but would not have been able to send or receive email through the eagle.ca servers. High-speed users who were not connected at the time would not have been able to login. The eagle.ca website was also unavailable to high-speed users during the outage.

• • • • •

September 13 - At 11:53 p.m. Friday night our connection to the Internet went down. A ticket was opened with the phone company at 1:02 a.m. Saturday. At 3:55 a.m. the connection was restored. An ATM switch at the Bell Central Office in Cobourg had malfunctioned and had to be reset. All systems were returned to normal by 4:00 a.m.

• • • • •

August 18, 2008 - At aprox. 6:46 this morning high-speed customers began having difficulty logging in. A connection to the high-speed network could be made but user authentication could not be achieved. As a result, Internet access was not available.

The problem was due to a faulty line card on part of the phone company's ATM network. The card was restarted several times but the problem was not rectified until the network server it was installed in was rebooted. The problem was resolved at 12:32 p.m.

• • • • •

October 30, 2007 - A water main break in London Ontario caused widespread issues for a variety of telecommunications services.  The break caused a sinkhole 10m x 10m in size at the corner of Wellington and Dundas streets. The Hydro London shut off power to the area to make repairs. Back-up power failed to start automatically at a telephone company office in the downtown area. That office is the location of a portion of eagle.ca's high-speed service. Clients who were online at the time were not affected but anyone attempting to connect was not able to due to authentication problems. The issue began at approximately 8:50 a.m. and was largely rectified by 11:10 a.m.

• • • • •

August 7, 2007 - 3:30 p.m. - Since last Thursday, some high-speed users have been experiencing problems with their connections. Users are able to connect successfully but experience slow speeds and/or are unable to retrieve email or connect with websites.

This problem is widespread within the phone company's high-speed network. It is affecting many ISPs across southern and central Ontario. The last report from the phone company was that they were aware of the problem, and believed it was a Distributed Denial of Service (DDoS) attack however they did not yet know the source and as a result had no estimated time of repair.

The problem appears to be intermittent and is affecting business and residential customers alike. Periodically turning you DSL modem off and then on a gain a few minutes later will reconnect you to the network but at this time we have no way of knowing which customers it will impact or when.

• • • • •

January 11, 2007 - 3:30 p.m. EST - Yesterday our Barracuda spam firewall experienced an unusually high load which caused it to slow its processing speed and queue messages for delivery. Some messages were being delivered normally while others were taking a few minutes to a few hours to reach eagleMembers. In some instances, messages were being returned to the original sender as undeliverable.

The queue diminished to normal levels overnight but has begun to increase again this morning. We are working with Barracuda Networks again this morning to resolve the problem.