Network maintenance completed: CO-R10
Published on June 18, 2009 at 11:45 pm by iWeb-SLee in: StatusThe maintenance has been successfully completed. Every thing went well as expected.
Comments
Leave a comment
About the iWeb blog
The iWeb Blog covers web hosting, web development, web design, Internet marketing and just about every announcement concerning iWeb.
Highest Rated
- iWeb again in the top 10 ten of most reliable networks in November





- Top 9 Reasons why Web Hosting is Awesome





- Who has the coolest costume?





- 4 Tools to Create A Website Quickly & Easily





- Season’s Greetings from iWeb!





- Securing Wordpress against hackers and bots





- Beware of the squirrel!





- iWeb on site for HostingCon 2009 in Washington DC





- iWeb Time Contest





- Customer experience : Why Level 5 management matters





Recent Comments
- Portable And Affordable Optical Fiber Identifier From Gao | Used Test Equipment on Communications infrastructure Failure – Resolved
- Luisa on Maintenance Panelbox Server Maintenance (S701) – resolved
- Luisa on Update: Delay to send email – Sebulba – Resolved
- Luisa on Update: Delay to send email – Sebulba – Resolved
- Gatorbait on Reacting to illegal or questionable content on servers
Recent Posts
Tags
adwords
analytics
blogging
canada
colocation
community
controlpanel
datacenter
dedicated
dns
email
events
exploit
facebook
google
iWeb
iweb-airconditionning-11092009
iwebnetwork-ddosattack-05092009
iwebtechnewshighlights
linux
management
marketing
montreal
mysql
netcraft
network
nuns-island
panelbox-s007-20081118
panelbox-s035-20091028
php
power
press
problems014_010810
revenues
security
server
shared
spanish
support
twitter
video
video-games
Web Development
windows
wordpress

Blog
Forum
Status
June 19th, 2009 8:36 am
But there is still a problem with a link from these routers:
11. te8-3.v0705.cl-core04.mtl.iweb.com
12. te8-1.v0709.hd-core01.mtl.iweb.com
while te8-4.cl-core06.cogent.mtl.iweb.com works fine…
June 19th, 2009 9:30 am
What is the issue? The maintenance did not affect the routers mentionned. You can open a ticket so that we can check it further.