12/31/2002 5:06:00 PM — We were experiencing some difficulties with a circuit that provides network connectivity between Newton and Jersey City. In trying to troubleshoot the issue, our virtual circuit that provides all transport between Newton and Jersey City was bounced and would not come back up. We believe this was due to a bug in our router's operating system. A forced reload of our core router in Newton was required. All systems are now functioning as they should once again. We apologize for any inconvenience this may have caused.
12/31/2002 — The staff of Tellurian Networks wishes our customers and their families a happy and successful New Year. Our holiday hours are as follows:
- New Years Eve, December 31st: Office is open 8am-4pm. Technical Support will be available from 8am-4pm
- New Years Day, January 1st: Office and Technical Support will be closed.
- Businesses with dedicated access have 24/7 emergency response as always.
We will resume normal hours on January 2nd.
Note: If you are experiencing a "Type Mismatch" error with Tellurian Webmail, please click here.
12/30/2002 — If you are experiencing a "Type Mismatch" error with Tellurian Webmail, please click here.
12/24/2002 — The staff of Tellurian Networks wishes our customers and their families Happy Holidays. Our holiday hours are as follows:
- Christmas Eve, December 24th: Office is closed. Technical Support will be available from 8am-6pm
- Christmas, December 25th: Office and Technical Support will be closed.
- Businesses with dedicated access have 24/7 emergency response as always.
We will resume normal hours on December 26th.
Note: If you are experiencing a "Type Mismatch" error with Tellurian Webmail, please click here.
12/23/2002 2:25:00 PM — The server our webmail system is on has undergone a complete hardware upgrade. We have reinstalled our webmail software from scratch on this new machine. Everything appears to be working properly. Please let us know if you experience any problems as a result of this upgrade. Thank you!
NOTE: If you receive a "Type Mismatch" error using Webmail since we performed this upgrade, you will need to delete the Webmail cookie from your system.
- Close Microsoft Internet Explorer
- Go to "Start" then select either "Find" or "Search" depending on your version of Windows.
- In the Find/Search window, select "All files or folders", then in the text box for "All or part of the file name", type: *webmail.tellurian*
- Next click "Search"
- When search is complete, delete any files with "webmail.tellurian" in the file name and that end in "txt".
- Start Microsoft Internet Explorer and go back to webmail.tellurian.com - the previous login information should be erased and you will need to re-enter both the username and password to log back into Webmail.
If you need assistance with this, please call support at 973-300-9561.
12/16/2002 11:21:00 PM — We have updated the DNS server software on our primary DNS server (gate.tellurian.net). Extensive testing was done before this change was put into place. Please let us know immediately if you suspect any problems or have issues resolving any domain name that we are hosting. Thank you!
12/15/2002 12:10:00 PM — Due to a configuration error made by one of our engineers, network connectivity was interrupted for a brief period late this morning. A restart of our core router in Newton was required to fix the problem. Some parts of our network and the Internet were unreachable as a result. Total downtime was approximately 10 minutes. We apologize for the interruption in service.
12/5/2002 — Our engineers are aware of and currently working on an issue with our primary mail server which may result in the inability for some customers to send and/or receive e-mail on an intermittent basis. We hope to resolve this situation shortly and will post additional information as it becomes available. 5:14PM UPDATE: We have isolated the cause of the mail problems. A spamming network was sending a flood of email LARGER than the typical amount of email our servers process from the entire Internet! We have blocked the offending network and are looking into why the flood of mail was able to easily criple our mail servers when we had plenty of resources available.
11/26/2002 — Our primary authentication server required an emergency restart resulting in the inability for some customers to connect to the Internet and/or retrieve their e-mail for a period of approximately 10 minutes. As of 11:30 AM, all systems are back up and fully operational.
11/1/2002 11:57:00 AM — We are currently experiencing a problem with our webmail system. Engineers are working on the problem and hope to have it resolved shortly. We will post more information shortly. UPDATE: As of 12:15PM we have the problem corrected. We have reinitialized our webmail application in an attempt to correct the problem. It turns out that there was a problem on our primary mail server with a process that crashed. This process is required for webmail to function properly. Once we were able to restart this service, webmail started working again. You will notice that the current webmail screens look different. We are re-cusomizing the original software manufacturer's HTML pages back to how we had webmail setup. Things may look a little odd for the next hour while we update some code. Webmail is functioning properly once again though. Please contact us if you have any questions or problems.
10/27/2002 10:50:00 AM — In an effort to further reduce the quantity of spam that our customers receive, we have implimented several new blacklists. Some of these block known spamming companies while others block confirmed sources of spam. Still others block improperly configured or "open" proxy servers. These spam fighting tools compliment our already existing set of blacklists that block known open relays as well as our own in house spam filtering systems. Senders that are listed will get their message rejected with an error message specifying the list that their mail server is currently listed on. Providing these blacklists work out well for us and our customers within the next week, we will update our mail policy on our web site additionally listing details of what are now checking for and blocking. We expect there to be little side effect from these additional spam fighting tools but will always prefer to receive legitimate mail than block spam. Please let us know if you experience any problems as a result of the new blacklists we are using. Thank you.
10/27/2002 12:40:00 AM — We believe the problem with dial-up access from Sussex County has been resolved. Most people are now able to log into us again with no problem. We will be monitoring this issue closely with our carriers.
10/26/2002 — 7:00PM - We are currently experiencing a telco equipment issue that is preventing people having an exhange number of 875, 702 and 209 (Primarily Sussex) from connecting into us. We have a trouble ticket open and are working to resolve this issue as soon as possible. 7:34PM - This problem is now starting to affect other exchanges in Sussex County, including Newton, Branchville and Hamburg. We are working closely with the telco's involved to get this resolved ASAP.
10/24/2002 — We have discovered and isolated a packet loss issue between our network and Sprint's Redback router. This affects all Sprint ADSL customers and is causing intermitent packet loss. It currently appears to be an ATM issue in the Newton, NJ central office based on our testing with three different publicly accessible ATM circuits that terminate there. We have a ticket opened with Sprint and their ATM group is currently looking into the issue. We will post more information as we receive it. UPDATE: Sprint appears to have resolved the packet loss issue. Tests show that there is no longer packet loss occuring between us and their Redback. Please contact us if you still have any issues.
10/21/2002 9:03:00 PM — We are currently having a problem with our access numbers in the greater sussex county area. We have contacted the telephone company and are currently working with them to resolve the problem. **UPDATE*** The access numbers are now working properly, the outtage lasted about 15 minutes.
10/13/2002 — Due to a problem with a DS3 mux at our Newton, NJ datacenter this morning, most connectivity going to our datacenter from the rest of our network and the Internet was interrupted shortly before 11:00 AM. We isolated the cause of the problem and corrected it however a restart of two core routers was required to completely restore network connectivity. Our network was completely restored and fully operational again at approximately 12:05 PM. We apologize for any inconvenience this may have caused and are taking steps to insure this type of problem does not re-occur.
10/11/2002 6:01:00 PM — Our Sussex county hunt group had a problem which was resolved within 10 minutes. All numbers rang busy while we had hundreds of free lines available. A reboot of our RAS equipment cleared the problem.
10/1/2002 — Our Sparta/Lafayette DSL POP is currently down due to power problems. It appears that many people in parts of Sparta, Lafayette, Andover and Newton are currently without power. We will post an update once power has been restored. UPDATE:Our Sparta/Lafayette POP is back in service as of 11:52PM. All systems are normal.
9/30/2002 — Verizon has repaired our circuits that comprise half of our backbone between Newton and Jersey City. We are no longer seeing any errors on the lines. We have restored them to full service. All network traffic should be normalized now. Please contact us if you have any problems.
9/29/2002 1:26:40 AM — We have isolated a problem with a few Verizon circuits that provide backbone connectivity between our Newton, NJ and Jersey City locations. Users were experiencing noticeable packet loss because of this issue. Due to the fault tolerant design of our network, we were able to shut off these problem circuits while Verizon works on correcting the issue. The circuits we are currently routing over are the other half of our backbone between Newton and Jersey City and are with a completely different carrier, making them unaffected by this issue. All packet loss issues are currently resolved. Users may experience slightly sub-optimal routing as a result, but much more reliable connectivity. We are working with Verizon to restore the original circuits to a fully operational and reliable status. Please contact us if you have any questions.
9/26/2002 — We have added a new Clinton, NJ access number: 908-730-6461 It supports K56Flex, v.90, and ISDN.
9/23/2002 6:20:00 AM — To improve routing performance for Sprint area Tellurian ADSL customers, we have made some routing changes between our router at our datacenter and our router located in Sprint's central office. As always, please contact us if you require any assitance. Thank you.
9/8/2002 12:15:00 AM — We are rebooting our mail server. It should be down for 5 minutes or less.
9/5/2002 — We currently have a trouble ticket open with Focal Communications in response to several customer complaints of disconnections and low connect speeds. We will post updates as they become available. Thank you for your patience as we assist Focal in isolating and correcting the problem.
9/5/2002 — UPDATE 9/5/02: Focal has not seen any problems on the affected lines for 48 hours. We have closed the trouble ticket. Please contact us if you experience any continued difficulties.
9/3/2002 7:40:00 AM — The mail issue has been resolved. Users were unable to check email this morning from 7:03:00 AM until 7:33:00 AM. We are still investigating the cause.
9/3/2002 7:20:00 AM — It looks like a spammer is performing some type of DOS against our mailserver. We are investigating now.
9/3/2002 — We currently have a trouble ticket open with Focal Communications in response to several customer complaints of disconnections and low connect speeds. We will post updates as they become available. Thank you for your patience as we assist Focal in isolating and correcting the problem.
8/28/2002 4:30:00 PM — We have added additional lines to our NJ/NY GNAPs hunt group. This adds capacity to all NJ numbers ending in 8355 and all NY numbers ending in 2121.
8/28/2002 3:00:00 AM — We are performing emergency disk management on our mail server. We expect to be completed by 6AM. UPDATE: Maintenance has been completed. All services are functioning normally.
8/27/2002 10:47:00 AM — Our core router in Newton, NJ spontaneously rebooted this morning at approximately 10:41AM due to a bus error. We are currently investigating the cause of this and what corrective actions are required. Everything is up and running at this time as of 10:43AM.
8/22/2002 8:19:00 PM — Our electrical power cutover has been completed. We will be doing more work in the datacenter during the next week to install new A/C units to provide additional cooling capacity. Our new automatic switchgear and redundant UPS units are in place and have power. We will be switching service to the new power system over the next few weeks.
8/22/2002 1:28:00 AM — As we previously announced, GPU/JCP&L will be cutting power to our building Thursday morning August 22, 2002 at 9AM to switch our AC service over to our new service entrance facility. Our datacenter and customer services will not be affected. Our telephone system will be operational, but the office will not have AC power so our staff's ability to help will be limited for a fews hours during the changeover. We will post a message here when the change has been completed.
8/17/2002 — JCP&L has replaced the power transformer on the pole and we are once again running on primary AC power.
8/16/2002 8:05:00 PM — The circuit breaker on the JCP&L power transformer on the pole which provides our primary AC power to our Newton datacenter has tripped. PCP&L will be replacing the transformer sometime tonight. In the meantime, we are using our secondary AC power source to run everything in the datacenter. We will post updates as they happen. No services are affected in any way by this power issue.
8/12/2002 8:33:00 PM — On August 22, 2002, we will be switching to our new AC power system in Newton, NJ. The upgrade should be transparent since we will be running on our secondary AC feed during the cutover. Over the following weeks, we will gradually transition all colocated equipment onto the new power directly and remove all the existing smaller UPS units from customer racks. We will post updates as they occur.
8/7/2002 2:40:00 AM — After making changes to the spool directory on the old mail server, we were able to get it to work reliably until our maintenance window. The new mail server is now live and operational. All old mail files including address books and calendars are being copied. This copy process will be finished by 7AM. Please let us know if you experience any issues as a result of the mail server upgrade. The new server is a dual Athlon 2000+ with 1GB RAM and a RAID 10 volume on 10k rpm U160 SCSI drives with dual hot spare drives. The performance of the mail server should be significantly better now. UPDATE 8/7/02, 9:25 AM: The mail server upgrade is complete. All files, messages, address books, etc. have been copied onto the new server. Please contact us if you have any questions or problems. Thanks for your patience as we upgrade our network.
8/6/2002 4:27:00 PM — We are still having issues with the data disk on our primary mail server. We will be replacing the server and all drives this afternoon. Some messages will be delayed as we make this change. No mail will be lost. We expect the upgrade to be completed by midnight. We appreciate your understanding while we resolve this problem. Thank you.
8/6/2002 8:43:00 AM — Our primary mail server is currently running an emergency disk repair operation to fix errors on one of the hard drives. As of 8:43AM, this process should take 3 to 4 hours to complete. We apologize for the inconvenience. Outgoing mail may be sent via smtp-forward.tellurian.net in the meantime. UPDATE: As of 12:00PM all mail services are back online and functioning normally. Our secondary mail server is now delivering all mail it had queued up during this outage. Some mail may be slightly backlogged while our SMTP delivery agent processes all of the previous mail.
8/3/2002 — We have isolated the mail problem our users were experiencing. It was due to a denial of service attack from a spammer in CA. We are working with our mail software vendor to determine why the messages they were attempting to send caused problems with our SMTP receive process. We will post more information when we have it. We have adjusted our firewall filters to stop this attack.
7/31/2002 12:00:00 PM — We are currently still experiencing random failures with our mail servers' SMTP services. The services themselves do not fail or shut down, but they briefly and randomly refuse a connection at times. This is happening on both our primary and backup mail servers. After doing some testing and working with the manufacturer of our mail software, we believe that this is being caused by either legetimate mail that is bringing out a bug in our mail server software or it's a deliberate denial of service attack although we have yet to find concrete evidence of that. We are doing more in depth testing and isolation to determine what is causing the random failures. If you are trying to send mail and get a message that your mail client couldn't connect to the SMTP server, just try again until the mail goes through. We are working with our vendor to fix this problem as quickly as possible and are sorry for the inconvenience this issue is causing any of our customers.
7/30/2002 4:38:00 AM — All maintenance has been completed successfully. All systems are online and 100% operational.
7/30/2002 12:57:00 AM — We will be taking our new SQL server offline for about 15 minutes to upgrade the RAM at 1:30AM tonight. We will also be running a disk check on our mail server to fix disk errors which are causing intermittent send errors.In the meantime, mail may be sent via smtp-forward.tellurian.net. The mail server disk task will be completed by early morning.
7/29/2002 10:20:00 PM — AT&T (AS7018) and FocalData (AS18984) are currently experiencing routing issues between their networks. We have filtered alll announcements from FocalData which are originiating in or passing through AS7018. This fix has solved the AT&T connectivity issues experienced by our clients when traffic bound for AT&T left our network via FocalData. Focal and AT&T continue to work to isolate the problem and repair it. Once they have fixed their problem, we will remove the filters from our BGP session and outbound traffic to AT&T may take FocalData to the destination network again if that is the best route.
7/29/2002 5:00:00 AM — Our primary SQL server has been upgraded. The upgrade was completed by 4:00AM EST. Clients should not notice any changes or difference due to this upgrade. This server is used to store dialup and DSL authentication information as well as other Tellurian information databases.
7/25/2002 2:03:00 PM — After feedback from our customers, we have switched back to the old news server setup. If you want to use the local caching server for binaries or fast downloads, use news2.tellurian.net For best retention and most complete newsgroup coverage, continue to use news.tellurian.net We tried to improve performance, but we found that people prefer retention to performance.
7/22/2002 5:43:00 PM — News server update: Tellurian Networks is now running a caching NNTP server running DNews. We are still using Giganews for our feed, but the server in our datacenter will allow for much faster connections for those with broadband connectivity. You may need to refresh the groups list and some articles may be out of sequence compared to the old server, but these changes will quickly pass. The new server only "subscribes" to groups when requested to enable better retention and disk utilization, but there is a short delay when subscribing to a new newsgroup.
7/4/2002 12:12:00 AM — Tellurian Networks will be closed on July 4th and 5th for Independence Day. We will reopen on Monday, July 8th at 8:00AM. Support will be available as usual over the holiday weekend. Have a great 4th of July and remember the importance of this holiday and what it meant to those who pledged their lives, their fortunes, and their sacred honor. The US PATRIOT Act restricts our rights in the name of protection and safety. Restricting our freedoms does not make us safe, it just makes us less free. Read more here and here.
Our founding fathers gave up everything for the freedoms and rights we enjoy today, all you need to do is write or call your elected representatives and insist that they protect our Constitutional rights and freedoms.
Have you ever wondered what happened to the 56 men who signed the Declaration of Independence?
Five signers were captured by the British as traitors, and tortured before they died. Twelve had their homes ransacked and burned. Two lost their sons serving in the Revolutionary Army, another had two sons captured. Nine of the 56 fought and died from wounds or hardships of the Revolutionary War.
They signed and they pledged their lives, their fortunes, and their sacred honor. What kind of men were they?
Twenty-four were lawyers and jurists. Eleven were merchants. Nine were farmers and large plantation owners; men of means, well educated. But they signed the Declaration of Independence knowing full well that the penalty would be death if they were captured.
Carter Braxton of Virginia, a wealthy planter and trader, saw his ships swept from the seas by the British Navy. He sold his home and properties to pay his debts, and died in rags.
Thomas McKeam was so hounded by the British that he was forced to move his family almost constantly. He served in the Congress without pay, and his family was kept in hiding. His possessions were taken from him, and poverty was his reward.
Vandals or soldiers looted the properties of Dillery, Hall, Clymer, Walton, Gwinnett, Heyward, Ruttledge, and Middleton.
At the battle of Yorktown, Thomas Nelson, Jr., noted that the British General Cornwallis had taken over the Nelson home for his headquarters. He quietly urged General George Washington to open fire. The home was destroyed, and Nelson died bankrupt.
Francis Lewis had his home and properties destroyed. The enemy jailed his wife, and she died within a few months.
John Hart was driven from his wife's bedside as she was dying. Their 13 children fled for their lives. His fields and his gristmill were laid to waste. For more than a year he lived in forests and caves, returning home to find his wife dead and his children vanished. A few weeks later he died from exhaustion and a broken heart.
Norris and Livingston suffered similar fates.
Such were the stories and sacrifices of the American Revolution. These were not wild eyed, rabble-rousing hippie guru's or professional protesters. They were soft-spoken men of means and education. They had security, but they valued liberty more. Standing tall, straight, and unwavering, they pledged: "For the support of this declaration, with firm reliance on the protection of the divine providence, we mutually pledge to each other, our lives, our fortunes, and our sacred honor."
They gave you and me a free and independent America. The history books never told you a lot of what happened in the Revolutionary War. We didn't just fight the British. We were British subjects at that time and we fought our own government! Some of us take these liberties so much for granted... We shouldn't.
So, please take a couple of minutes while enjoying your 4th of July holiday and silently thank these patriots. It's not much to ask for the price they paid.
(Thanks to Ron from the 356 list for this history lesson and thoughts)
7/3/2002 11:53:00 PM — We have lost connectivity to our Sparta/Lafayette POP. This POP feeds SDSL customers out of this area. The POP is down due to a power issue. Our battery backup has been exhausted and we are waiting for utility power to be restored at this site. We will post more information when it becomes available. UPDATE: This is really just a FYI announcement since all customers served out of the Sparta/Lafayette POP are also without power.
7/3/2002 — Tellurian Networks will be closed on July 4th and 5th in celebration of Independence Day. Engineers will continue to monitor the network, and customers with dedicated connections can contact support using the escalation procedures. Dial up support will resume normal hours on Saturday, and the office and all departments will resume normal hours on Monday. The staff of Tellurian Networks wishes everyone a safe and happy holiday!
7/1/2002 — 2:00 AM - Maintenance on our mail server has now been completed.
6/30/2002 — We will be performing disk maintenance this evening on our mail server starting at 11PM. During this maintenance window customers will not be able to send or receive mail until this is completed. The estimated down time while this is being performed is 3-4 hours. We apologize for any inconvenience this may cause. We will update as soon as this has been completed. Thank you.
6/29/2002 11:50:00 PM — We will be performing some disk maintenance this evening from 12AM to 2AM on our users web server and on our web1 server. 12:40AM 6/29/02 UPDATE: Maintenance has been completed.
6/27/2002 11:30:00 PM — We experienced a brief power interruption this evening to some customer colo machines and one of our switches. The transformer on the pole from which we obtain our electrical power feed was hit with lightning or a surge which blew the breaker. We ran from UPS when the power failed, but the generator would not start immediately. This issue was resolved and we ran on generator power for about an hour until switching to our alternate source of utility power. We ran from the alternate utility power for about 2 hours until returning to our normal power after JCP&L restored service. As many of you know, we are in the process of a major electrical upgrade which includes a set of huge fault-tolerant UPSes and a diesel genset and automatic switchgear. When the electrical upgrades are completed within the next two weeks, the problem encountered will have no effect on any customer's services.
6/26/2002 2:18:00 AM — Several weeks ago, we changed the IP address of our mail server: mail.tellurian.net from 188.8.131.52 to 184.108.40.206
As of 2:30AM, gate.tellurian.net will be 220.127.116.11 and mail services will no longer be available on this IP address. This message is informational only. No users should be affected by this change since all DNS entries were changed several weeks ago. If there are any issues as a result, please feel free to contact us. Thank you.
UPDATE- To ensure you will not be affected by changes we have made, please make sure you are using the correct, most updated mail server names. You should use pop3.tellurian.com as your incoming mail server, and smtp.tellurian.com as your outgoing mail server. For information on checking and changing this information in your mail program , please see http://www.tellurian.com/connect.
6/25/2002 5:39:00 PM — A major fiber cut has occurred in Cambridge, MA. Verizon Fiber was cut by the MWRA (Mass Water Resource Authority). The MWRA was digging outside 2 Verizon Tandems, and hit "Several" Conduits in the street. Most of Verizon's network in Cambridge, South Boston, Dorchester, Hyde Park and Boston, as well as some outlying cities and towns, is down. Along with their internal network of trunks, 911, and Sonet, Several main Customer fiber rings also originated from these Tandems. One of our telephone companies, GlobalNAPs has had a small portion of their fiber rings affected. Fortunately they remain mostly intact. For those customers in the Boston and Cambridge areas who can dial out, there will be significant problems getting from Verizon to Tellurian access numbers in the area. We will update you with any new information that we obtain. At this time there is no ETA. There are many, many fibers that will need to be respliced and a timeframe is not available at this time. This outage affects a VERY limited number of Tellurian customers in the greater Boston, MA area, but we are posting it since it will may also cause reachability problems to sites which are hosted with providers in MA. Tellurian's network is 100% operational. This is a Verizon fiber cut.
6/21/2002 10:56:00 PM — Another new anti-spam measure is now in place. We now perform lookups on all inbound from addresses. If the from address is in a domain which does not have a valid way to deliver mail to that domain (no MX/A records) then the message will be refused. We have also updated our anti-virus software which should prevent most viruses from passing through our mail server. Some viruses did manage to bypass the filters before these changes were made. Mail will now be held up to 2 minutes to scan for viruses. Prior to this change, the limit was 30 seconds and scanning was skipped on large messages or if the server was very busy.
6/20/2002 — Fight back against spam! We have recently been made aware of a new and free plug-in from Cloudmark for Outlook 2000 & Outlook XP (support for Outlook Express coming soon) called Spamnet that can help reduce the amount of spam that you receive. Give it a try!
6/18/2002 2:46:45 PM — We have patched our mail servers to a point release that fixes DNS lookup issues for reverse lookups and blacklists. This now enables us to do reverse lookups on all IP addresses that send mail through our server making our server more RFC compliant. We have also reinstated previous blacklists: ordb and spamcop. Please let us know if you experience any problems as a result of this new patch.
6/6/2002 11:37:00 AM — The DS3 card in core1-nyny has been replaced and all circuits are operational again. Several of the ports on the DS3 card provided the connectivity to the rest of our backbone. We will be reengineering new circuits to connect our Newton location to NYC via a different card and a different carrier as an additional redundancy step. We will also be storing a spare DS3 card onsite as a hot spare to minimize downtime in the future.
6/6/2002 9:30:00 AM — We currently have a DS3 card failure on our NYC router. One of our staff is enroute with a new replacement card.
6/6/2002 12:35:00 AM — The router upgrades have been completed. Total downtime was less than 5 minutes.
6/5/2002 5:08:00 PM — We will be upgrading our core1-nwtnj and our core1-jcnj routers IOS version tonight at 12:30AM to add SNMP functionality and to resolve an EIGRP bug. Downtime should be less than 10 minutes.
6/5/2002 12:50:00 AM — We have upgraded our core1-jcnj to core1-nyny backbone link. The upgrade was transparent and happened with zero downtime.
6/4/2002 6:50:00 AM — All NY and NJ numbers ending in 2121 are operating normally now.
6/4/2002 4:05:00 AM — There is currently a problem with our NY and NJ numbers ending in 2121. They are showing as busy, but there are no users online. This should be resolved by early morning and is due to a phone company upgrade during the night.
6/4/2002 1:03:00 AM — The upgrade has been completed. NY customers should see better performance when connecting to the Internet. We have turned up additional BGP connections and restored full-mesh BGP connectivity to the rest of our backbone.
6/3/2002 4:30:00 PM — At midnight tonight we will be upgrading a processor card in our core router in New York City. Downtime shouldn't be longer than 10 minutes. This will affect all services out of the New York City area including point to point T1's, ADSL, and dial-up.
5/30/2002 11:09:00 AM — A newer BETA version of our dialer is available. One of our customers pointed out a mistake with one of our Canada numbers. In examining the phonebook, we have added a few additional numbers which were missing from the previous distribution and removed a few old numbers. If you have any comments about or problems with the new dialer, please send a message to email@example.com. Thank you for your feedback and support.
5/27/2002 1:42:00 AM — A new BETA version of our dialer is available. This new version includes all current numbers and is made for Windows 95/98/ME/NT/2000/XP. This dialer includes completely NEW numbers for VT, NH, MA, RI, southern NJ, PA, DE, MD, DC, and VA. If you call the old numbers in ANY of these regions, please update your dialer and use the new access numbers today. If you have any comments about or problems with the new dialer, please send a message to firstname.lastname@example.org. Thank you.
5/23/2002 10:10:00 PM — In a few minutes we will be applying a point release update to our primary mail server. The update process only takes a couple of minutes. Downtime will be minimal. Please let us know if you experience any problems as a result of the upgrade. An update will be posted here when the upgrade has been completed. UPDATE: 5/23/2002 10:15:00 PM - The update has been completed. All mail services are functioning normally.
5/16/2002 — We have added or updated 367 numbers in VT, NH, MA, RI, Southern NJ, PA, DE, MD, DC, and VA. View the entire list here. Update your access number today for better performance. All Tellurian static IP addresses starting with 216.182.x.x or 66.97.x.x will work with ANY of these new numbers. All customers in these areas must use the new numbers ending in 2322.
5/6/2002 11:50:00 PM — We will be adding many new access numbers over the next few weeks. We will also make a new dialer build available with all the new numbers included.
5/6/2002 1:05:00 PM — We are currently experiencing a problem with our primary mail server. Engineers are working to correct it. We apologize for the inconvenience. **Update** The issues with the mail server have been resolved.
5/4/2002 — We will be performing maintenance on our phone system this evening beginning at 8PM. This maintenance is to improve functionality of our phone system and to allow us to serve our customers better. During this maintenance period, you may receive an all circuits busy message or just a busy signal when calling our office. We expect the maintenance to last no longer than two to three hours.
5/3/2002 — We have increased the timeout for a Webmail session from 20 minutes to 60 minutes.
5/1/2002 — Our Newton portmaster rebooted at 4AM, but OSPF failed to start. One of our engineers started the service manually at 6:30am. Between 4-6:30, customers dialing our 973-300-4966 access number would have been able to connect, but not pass any traffic. We apologize for the inconvenience.
4/30/2002 — There was a problem with our Adelphia Portmaster this morning which caused many of our dial up customers calling xxx-xxx-8355 numbers to receive errors. A reboot of the portmaster took care of this.
4/24/2002 3:47:00 AM — The mail server maintenance has been completed successfully.
4/23/2002 8:30:00 PM — We will be taking our mail server offline for maintenance at 1:00AM EDT on 4/24/2002. We expect to be completed by 4:00AM EDT 4/24/2002.
4/19/2002 9:24:00 PM — JCP&L has restored the power to our Newton datacenter. All equipment is operating on utility power again.
4/19/2002 6:20:00 PM — Our Newton location is now operating on generator power. We do not have an ETR for utility power.
4/19/2002 12:34:00 PM — Everything in NYC at GlobalNAPs is operating normally again at this time.
4/19/2002 12:01:00 PM — Global NAPs is experiencing an outage at their Quincy, MA location. They are currently looking into it trying to restore connectivity. This affects customers out of our New York City POP. We will post more information as we receive it. UPDATE: GlobalNAPs has restored connectivity. We are currently working to prevent future problems if this situation occurs again.
4/15/2002 8:35:00 AM — All systems are 100% operational and the new mail server software's increased functionality is now online!
4/15/2002 7:29:00 AM — The mail server disk check has not completed yet. It should be completed by 8:00AM. This procedure is important to protect customer mail data. All messages will be queued in the meantime. Anyone who needs to send mail may use smtp-forward.tellurian.net.
4/15/2002 6:50:00 AM — We are running an emergency filesystem check on the mailserver after major maintenance and the upgrade. It should be completed by 7:30AM.
4/15/2002 — We have upgraded our mail server to the latest version software. The new version adds new features including: a webmail calendar, spell-check, and draft save mode. All accounts are also protected with the F-Secure anti-virus scanning engine.
4/14/2002 6:00:00 PM — Sunday afternoon, a bad power supply triggered a UPS to fail which tripped a sub-panel circuit breaker, which tripped the circuit breaker on our feeder panel for the datacenter. We were immediately alerted and dispatched a team to work on the problem. Power was restored within 10 minutes. However, the following failures kept some systems offline for an extended time: filesystem checks on our mail and dns server (gate), failed nvram on a switch supervisor card which caused a loss of configuration data, a DS3 protect circuit which would not fail back over to the working connection. The following actions are being taken to ensure these issues will not arise again.
1. As we have grown, upgraded power facilities have been planned over the past 6 months. The design was finalized this month and we ordered some of the equipment last week. The balance of the equipment will be ordered early this week. We will announce when the service upgrade will take place in the future. We expect the new service and UPS/GenSet installation to be completed within 4-6 weeks. We do not anticipate any overall downtime as a result. Some non-redundant power systems may need to be taken offline one at a time during standard maintenance intervals after the new service is installed. All routers, switches, and many servers have redundant power and will not be affected. More details will be announced as we proceed.
2. Today, we built two new servers to offload DNS and storage responsibilities. We have maintained the combined DNS/Mail infrastructure as it was in the beginning in 1995. We have changed software several times and upgraded hardware every 6-12 months, but the IP addresses have not changed. We need to split these functions. It will take time and some people may experience configuration issues as a result, but this must be done. We have put it off in the interest of backward compatibility, but the time has come to make this change.
3. We have scheduled the install of another supervisor module during the maintenance window next Saturday morning. During this time, we will also switch encapsulation to dot1q from the current ISL encapsulation.
4. The DS3 Mux has been reconfigured to not fail/protect the DS3 circuit connected to our router.
4/11/2002 1:16:00 PM — The new access number for Newton is: 973-300-5261 Sussex, Franklin, and Blairstown all point to this number now as well. If you currently call 973-300-4966 and you experience a busy signal, please call 973-300-5261. We will send out a notice with new primary and backup number preferences in a couple of weeks after the number realignment is completed.
4/11/2002 — Sprint is still working to allocate and assign the number correctly. All 28 new PRI lines are installed and operational, but we are waiting for the numbers to be assigned correctly. We expect this should happen sometime today. We'll post updates here when we have them. Thanks!
4/10/2002 — Our NEW Newton number is being turned up today. We anticipate it will be ready for use sometime this evening. As of 6:40PM, they are still working on it. We will post the new number after it is working and tested. Thank you.
4/9/2002 — There is currently a Sprint Internet outage, we will post more information as it becomes available. UPDATE The problem as been resolved.
4/1/2002 — In an effort to drastically reduce the amount of junk email, otherwise known as SPAM, we have configured our mail servers to listen to two blacklists: ordb.org and spamcop.net. This should dramatically reduce the amount of SPAM our users receive. Please send any comments regarding this change to email@example.com. We believe the overall reduction in SPAM is well worth the effort.
3/29/2002 — We have just received a confirmed date from the telephone company regarding the installation of new access lines for the Sussex County Area. The lines are to be installed on April 10. This should help alleviate capacity issues in this area.
3/19/2002 11:40:00 AM — Verizon has fixed the T3 line in NYC. They claim they didn't do anything, but it is fixed and working normally now.
3/19/2002 11:00:00 AM — We have a channelized DS3 in NYC which is currently down. This affects all T1 customers served out of 32 Old Slip in New York City. We have opened a trouble ticket with Verizon and they are currently working on the problem. It appears to be SONET related at this time. Customers with ISDN backup are operational. This does not affect dialup. There is no ETR at this time.
3/19/2002 6:50:00 AM — Our Portmaster in Newton, NJ rebooted at 5:50AM. OSPF didn't restart when the Portmaster rebooted. This resulted in routing problems for customers dialing Newton, NJ from 5:50AM to just before 7:00AM. Thanks to Bob Dugan for alerting us of the problem.
3/9/2002 8:02:00 AM — Check disk procedure on our mail server was successfully completed.
3/9/2002 — We will be running a check disk procedure on our mail server for about two hours from 3:00AM to 5:00AM. The procedure MAY take longer than 2 hours.
3/6/2002 6:43:00 PM — The Akamai servers in our datacenter started sending massive traffic to our router which caused an internal denial of service attack. It took about 10-15 minutes to isolate the source of the attack. We have taken all Akamai servers offline until they determine the cause and fix it. Our network is operating normally at this time.
3/6/2002 7:44:00 AM — Verizon has fixed the problem for now, but we are still seeing errors. They will be monitoring the circuit throughout the day to determine the root cause of this outage and fix it. This affects T1 frame relay customers in New Jersey. All customers are currently 100% operational.
3/6/2002 5:40:00 AM — We are currently experiencing a Verizon DS3 outage in Jersey City. Verizon is working on the problem. This affects T1 frame relay customers in New Jersey.
3/3/2002 — Verizon is having SONET problems between NJ and NY. We are having problems with a DS3 connecting NJ and NY as a result. They are working on the problem. We are using a slower speed link while they fix the problem.
2/26/2002 — We have upgraded the FTP server software on the following FTP servers on our network: Tellurian Public FTP, FTP for Users personal web sites, all commercial Web servers. Everything appears to be functioning normally, but please let us know if you experience any difficulties as a result.
2/22/2002 — The Google search engine (www.google.com) is having intermittant problems, where the site becomes unreachable for a few minutes at a time. This appears to be an issue with their provider. This information is provided to inform our users, this is not a problem with Tellurian or with any setup on your personal computer.
2/20/2002 — Our connectivity to our Mohawk POP which serves Mohawk DSL customers was down briefly today beginning at approximately 1:20PM. We found the T1 that provides connectivity to the POP was in alarm. After resetting the smart jack on the Newton side, the circuit came back up. Service is restored as of 1:34PM. We apologize for any inconvenience this may have caused.
2/11/2002 — We have unexpectedly taken our primary mail server offline for emergency maintenance. We have discovered some corrupt files and have decided to shut down all mail operations and repair the file system to prevent any further problems. Sending and receiving mail will not work until the emergency maintenance is completed. More information will be posted as we continue through the repair process. UPDATE: Shortly after 5AM this morning, 2/12/2002, the repair process was completed. Everything looks corrected so we brought all mail services back online. Please contact our technical support department if you have any problems.
2/6/2002 7:07:22 PM — 95% of our Verizon area T1 Frame Relay customers were moved today to our new DS3. We will be changing our BGP route announcements over the next 24-48 hours for better traffic flows.
2/5/2002 9:35:29 AM — On Wednesday February 6, 2002, throughout the night we will be moving all T1 frame relay customers from one T3 to another. Each customer outage should only last only 10-20 minutes.
2/4/2002 1:04:00 PM — We are currently experiencing power problems at our Sussex, NJ POP. All DSL customers out of this location are affected. We will post more information as it becomes available. - UPDATE: Power has been restored to the Sussex POP. All services are functioning normally once again.
2/4/2002 8:40:00 AM — Adelphia, one of our phone carriers, in Parsippany, NJ had some type of power problem/failure this morning February 4th. This affected all lines in NJ ending with 8355 at 8:00AM. AC power to our equipment was interrupted for 8 minutes. Everything is working normally now. We do not have any info on the cause of the disruption from Adelphia at this time. We will post more information when we get it. All systems are normal.
2/1/2002 10:14:00 AM — The new version of the Tellurian Networks website has been launched! Please email firstname.lastname@example.org with any comments or suggestions. Thank you.
1/31/2002 10:40:27 PM — All Verizon area DSL customers have been moved to our new ATM DS3 and the network is 100% operational again.
1/30/2002 5:17:16 PM — On Thursday, January 31st at 9PM technicians will begin grooming our ATM circuit PVCs from one DS3 to another. This is outside our normally scheduled maintenance window, but it is the only time knowledgeable Verizon technicians are available outside of business hours. This will only affect Verizon DSL customers in NJ.
1/23/2002 1:46:39 PM — All issues with MegaPOP access numbers have been resolved at this time.
1/23/2002 11:31:09 AM — We are currently experiencing authentication problems with access numbers we have served by MegaPOP. These numbers vary in the way they are identified, but are mostly all outside of New York and New Jersey. We have a ticket opened with MegaPOP and they are working on the issue. We will post more information as it becomes available.
1/23/2002 3:06:24 AM — We will be taking our web1 server offline at 3:30AM to upgrade the RAM to 1.5GB. If your website is hosted on an IP address of 216.182.12.x, you will be affected by the 20 minutes of downtime.
1/22/2002 10:12:50 AM — A Sprint maintenance worker disconnected power to our Newton DSLAM while waxing the floors this morning. We have reconnected power and asked him to be careful in the future.
1/14/2002 — We found a malfunctioning board this evening in our access server that serves dial-up access numbers in Sussex County. We were short 92 lines and thus caused busy signals at many access numbers in the area. We unfortunately could only resolve this by rebooting the entire access server. All lines are now functioning again and we apologize for any inconvenience this may have caused.
1/8/2002 — Global NAPs will be performing some software upgrades to equipment on Wednesday, January 16, 2002 between the hours of 2AM to 6AM. This maintenance should not interrupt any services. Our POP served by Global NAPs is in NYC and serves all NJ and NY XXX-2121 access numbers as well as dedicated access customers in NYC.
1/4/2002 — This morning we identified an error in the configuration of a new router at our Focal POP. This error prevented route distribution from our RAS boxes that customers dial into. The only people that would have experienced a problem were customers with static addresses or routed blocks of addresses dialing into this POP (any number ending in 9835). The problem has been resolved. We apologize for any inconvenience this may have caused.
1/3/2002 — We have turned up an additional two T1's to Sprint adding 3Mb to our existing 6Mb pipe now for a total of 9Mb. Users should notice an increase in performance.