| Posted by tamouh, 06-01-2006, 05:54 AM | |
Hi,
I've been getting notified from people in California they weren't able to reach our servers which are with iWeb.
Can someone please check from down the states . I did tracert from couple of universities in California and confirmed iWeb network unreachable:
traceroute from www.net.berkeley.edu to 209.172.38.230
1 inr-211-inr-203--128-32-206-1.HSRP.Berkeley.EDU (128.32.206.1) 0.686 ms 0.571 ms 0.529 ms
2 g3-1.inr-201-eva.Berkeley.EDU (128.32.255.1) 0.558 ms 0.590 ms 0.598 ms
3 ge-1-2-0.inr-002-reccev.Berkeley.EDU (128.32.0.36) 0.518 ms 0.567 ms 0.804 ms
4 oak-dc2--ucb-ge.cenic.net (137.164.23.29) 0.800 ms 0.765 ms 1.021 ms
5 dc-oak-dc1--oak-dc2-p2p-2.cenic.net (137.164.22.194) 1.030 ms 0.987 ms 0.826 ms
6 sfo-px1--oak-dc1-ge.cenic.net (198.32.251.227) 2.343 ms 2.485 ms 2.397 ms
7 paix.cogentco.com (198.32.176.131) 3.252 ms 3.509 ms 3.072 ms
8 p13-0.core02.sfo01.atlas.cogentco.com (154.54.1.253) 3.491 ms 3.338 ms 3.344 ms
9 p14-0.core01.ord01.atlas.cogentco.com (66.28.4.186) 49.312 ms 49.325 ms 49.356 ms
10 p15-0.core02.ord01.atlas.cogentco.com (66.28.4.62) 49.373 ms 49.594 ms 50.406 ms
11 p5-0.core01.yyz01.atlas.cogentco.com (66.28.4.214) 63.288 ms 63.532 ms 262.724 ms
12 v3491-mpd01.yyz01.atlas.cogentco.com (154.54.5.78) 92.128 ms 184.957 ms 251.337 ms
13 v3493-mpd01.yyz02.atlas.cogentco.com (154.54.5.86) 63.105 ms 63.358 ms 63.670 ms
14 g11-0-1.core01.yyz02.atlas.cogentco.com (154.54.3.229) 63.016 ms 63.252 ms 62.984 ms
15 g1-1.mtl-hd-core03.cogent.iweb.ca (38.116.204.26) 70.384 ms 70.415 ms 70.395 ms
16 * * *
17 * * *
18 * * *
Thx!
|
| Posted by tamouh, 06-01-2006, 06:13 AM | |
I'm getting same results from Teleglobe line:
1 POD-C-VL4.GW.CMU.NET (128.2.4.1) 0.256 ms 0.180 ms 0.163 ms
2 128.2.255.194 (128.2.255.194) 0.267 ms 0.191 ms 0.182 ms
3 POD-I-CYH-VL942.GW.CMU.NET (128.2.255.205) 0.247 ms 0.209 ms 0.204 ms
4 bar-cmu-ge-4-0-0-1.3rox.net (192.88.115.181) 0.310 ms 0.279 ms 0.334 ms
5 minime-ge-0-1-0-0.3rox.net (192.88.115.5) 0.324 ms 0.344 ms 0.358 ms
6 so-2-1-1.ar3.JFK1.gblx.net (208.50.254.45) 22.257 ms 22.204 ms 22.319 ms
7 so1-2-0-2488M.ar1.DCA3.gblx.net (67.17.67.53) 27.177 ms 27.288 ms 27.130 ms
8 teleglobe-1.ar1.DCA3.gblx.net (208.51.74.2) 27.053 ms 27.059 ms 26.986 ms
9 if-6-3.mcore4.NJY-Newark.teleglobe.net (216.6.63.21) 57.477 ms 57.547 ms 57.600 ms
10 if-10-0.core2.MTT-Montreal.teleglobe.net (216.6.63.14) 57.665 ms 57.589 ms 57.646 ms
11 Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167) 57.575 ms 57.474 ms 57.397 ms
12 g1-2.mtl-hd-core01.teleglobe.iweb.ca (66.198.80.58) 57.660 ms 57.655 ms 57.849 ms
13 * * *
Though internal Cogent traceroute shows it is routing fine:
1 g10-0-224.core01.lax01.atlas.cogentco.com (66.250.4.5) 4 msec 0 msec 0 msec
2 t3-1.mpd01.lax01.atlas.cogentco.com (154.54.2.102) 4 msec 0 msec 0 msec
3 pc15.mpd01.iah01.atlas.cogentco.com (154.54.2.197) 36 msec 36 msec 36 msec
4 g2-0-0.core01.iah01.atlas.cogentco.com (154.54.2.241) 36 msec 36 msec 36 msec
5 p13-0.core01.ord01.atlas.cogentco.com (154.54.2.14) 60 msec 60 msec 60 msec
6 p15-0.core02.ord01.atlas.cogentco.com (66.28.4.62) 60 msec 60 msec 60 msec
7 p5-0.core01.yyz01.atlas.cogentco.com (66.28.4.214) 76 msec 76 msec 76 msec
8 v3490-mpd01.yyz01.atlas.cogentco.com (154.54.5.74) 284 msec 228 msec 212 msec
9 v3492-mpd01.yyz02.atlas.cogentco.com (154.54.5.82) 76 msec 76 msec 72 msec
10 g11-0-1.core01.yyz02.atlas.cogentco.com (154.54.3.229) 72 msec 72 msec 76 msec
11 g1-1.mtl-hd-core03.cogent.iweb.ca (38.116.204.26) 84 msec 80 msec 80 msec
12 g4-31.mtl-hd-core02.iweb.ca (209.172.50.85) 84 msec 80 msec 80 msec
13 ferrari.smallvillages.com (209.172.38.230) 80 msec 80 msec 84 msec
|
| Posted by tamouh, 06-01-2006, 07:10 AM | |
Another tracert to iWeb own site showing it is not reachable from California:
traceroute to 209.172.41.170 (209.172.41.170), 30 hops max, 40 byte packets
1 v253-gw.usc.edu (128.125.253.254) 0.597 ms 0.379 ms 0.462 ms
2 v251-gw-19.usc.edu (128.125.251.155) 0.296 ms 0.278 ms 0.279 ms
3 lax-dc1--losnettos-dc.cenic.net (137.164.23.225) 0.642 ms 0.651 ms 0.58 ms
4 dc-sac-dc1--lax-dc1-pos.cenic.net (137.164.22.127) 10.286 ms 10.232 ms 10.187 ms
5 dc-oak-dc1--csac-dc1-ge.cenic.net (137.164.22.110) 12.157 ms 12.145 ms 12.117 ms
6 sfo-px1--oak-dc1-ge.cenic.net (198.32.251.227) 12.811 ms 12.945 ms 11.195 ms
7 paix.cogentco.com (198.32.176.131) 12.592 ms 12.663 ms 12.593 ms
8 p5-0.core01.sjc04.atlas.cogentco.com (154.54.1.201) 12.453 ms 12.283 ms 12.322 ms
9 p14-0.core01.ord01.atlas.cogentco.com (66.28.4.186) 58.34 ms 58.228 ms 58.519 ms
10 p15-0.core02.ord01.atlas.cogentco.com (66.28.4.62) 58.192 ms 58.307 ms 58.381 ms
11 p5-0.core01.yyz01.atlas.cogentco.com (66.28.4.214) 72.131 ms 83.945 ms 72.416 ms
12 v3490-mpd01.yyz01.atlas.cogentco.com (154.54.5.74) 71.963 ms 72.05 ms 99.887 ms
13 v3492-mpd01.yyz02.atlas.cogentco.com (154.54.5.82) 72.17 ms 72.035 ms 72.094 ms
14 g11-0-1.core01.yyz02.atlas.cogentco.com (154.54.3.229) 72.19 ms 71.965 ms 72.038 ms
15 g1-1.mtl-hd-core03.cogent.iweb.ca (38.116.204.26) 79.31 ms 79.285 ms 79.262 ms
16 * * *
17 * * *
I'm still waiting on the engineers to come onsite to look into this issue!
|
| Posted by tamouh, 06-01-2006, 09:16 AM | |
Finally, it is back online now !
|
| Posted by atchoooo, 06-01-2006, 11:50 AM | |
I am not sure what is the time this thread was posted, but after a Teleglobe issue with the addition of the 2nd Teleglobe GigE in our network yesterday, this morning there was a problem with one of our network providers that caused some routes to be unavailable.
Details have been posted here :
http://blog.iweb.ca/en/2006/06/video...arily/393.html
The problem was related to a weird route problem with one of the providers in our BGP mix. We had to disconnect and shutdown the BGP session with the provider, it is still desactivated and we are waiting for an update from them before bringning the session back up.
Feel free to ask for more details here or on our blog.
Regards,
|
| Posted by Homeblock, 06-02-2006, 08:39 PM | |
Down again or am I crazy?
dan
|
| Posted by tamouh, 06-02-2006, 08:43 PM | |
Ya it just went down again. Their main phone line is either busy or no answer!
|
| Posted by ralexander, 06-02-2006, 08:51 PM | |
Same issue here, no access and i'm in Toronto.
|
| Posted by Homeblock, 06-02-2006, 08:53 PM | |
Popped back up for 30 seconds then died again?
|
| Posted by Isaac.Eiland-Hall, 06-02-2006, 08:58 PM | |
I noticed about 5-10 minutes of outage from around 7:42-7:49pm.... I would assume that they either enabled or disabled something, or it's a glitch from upline from them... heh.
|
| Posted by tamouh, 06-02-2006, 09:03 PM | |
Their site is back up. the word this is a power issue...
|
| Posted by ralexander, 06-02-2006, 09:19 PM | |
My servers are still down. Got ahold of a tech on the phone they're looking into it.
According to the blog at http://blog.iweb.ca/en/2006/06/power...-time/396.html
|
| Posted by atchoooo, 06-02-2006, 09:20 PM | |
More details on http://blog.iweb.ca ... this week is not a good week (teleglobe issues, videotron issues and now power issues). A Hydro-Québec blackout occured near 7h00pm ... generators provided power until around 8h35pm when something occured (we still do not know all the details) and power came back around 8h49. We will post all the details and explainations on our blog.
Regards,
|
| Posted by Isaac.Eiland-Hall, 06-02-2006, 09:48 PM | |
Yeah, I've been watching the blog recently -- lots of fun! :-(
This is the first of the items that I know has impacted me - so I feel fine, even though I feel a little sorry for some others-- but mostly for the iWeb staff. I know you guys are having to work extra hard with all of these problems.
But even with the recent spate of bad luck -- seems like the service is still strong. Extremely quick responses everywhere. My faith is still quite with you guys! :-)
|
| Posted by totos, 09-18-2006, 01:24 AM | |
I know this thread is a bit old, but afterall it seems that iWeb dont provide 100% uptime as they advertize on yheir site...
|
|
 Add to Favourites
 Print this Article
|
