Results 1 to 16 of 16
Thread: WebReseller Down??
-
10-07-2002, 11:38 PM #1Junior Guru
- Join Date
- Jun 2002
- Posts
- 234
WebReseller Down??
After just having resolved the latency issue, it appears webreseller is down. I cannot ping or access www.webreseller.net nor my server.
Any information?
-
10-07-2002, 11:42 PM #2Junior Guru
- Join Date
- Jun 2002
- Posts
- 234
Seems to have just went back up..
-
10-07-2002, 11:43 PM #3Web Hosting Master
- Join Date
- Mar 2002
- Location
- Westbury, LI NY
- Posts
- 1,705
Yes, I agree, it was down, but I waited 30 seconds adn tried again and it came back up.
Resetting a router?
-
10-07-2002, 11:46 PM #4Web Hosting Master
- Join Date
- Nov 2001
- Posts
- 852
I didnt notice anything...
-
10-07-2002, 11:55 PM #5Web Hosting Master
- Join Date
- Mar 2002
- Location
- Westbury, LI NY
- Posts
- 1,705
And now its down...
-
10-07-2002, 11:56 PM #6WHT Addict
- Join Date
- Sep 2002
- Location
- Colorado, US
- Posts
- 108
figures...
Rave5 Web Solutions
http://www.rave5.com
-
10-07-2002, 11:58 PM #7Web Hosting Master
- Join Date
- Mar 2002
- Location
- Westbury, LI NY
- Posts
- 1,705
Code:C:\>tracert 66.227.5.137 Tracing route to 66.227.5.137 over a maximum of 30 hops 1 <10 ms 16 ms 15 ms 10.9.128.1 2 <10 ms 16 ms <10 ms 167.206.32.33 3 <10 ms 16 ms 16 ms r1-ge9-1.mhe.hcvlny.cv.net [167.206.32.1] 4 <10 ms 15 ms 32 ms r1-srp1-0.cr.hcvlny.cv.net [167.206.12.38] 5 <10 ms 31 ms 47 ms r1-srp1-0.wan.hcvlny.cv.net [167.206.12.98] 6 <10 ms 16 ms <10 ms r2-srp5-0.in.nycmny83.cv.net [167.206.12.118] 7 <10 ms 16 ms 16 ms so-2-0-0.gar1.NewYork1.Level3.net [167.206.8.62] 8 <10 ms 47 ms 16 ms so-7-0-0.mp1.NewYork1.Level3.net [64.159.1.181] 9 <10 ms 16 ms <10 ms so-0-1-0.mp1.Philadelphia1.Level3.net [64.159.0.141] 10 <10 ms 31 ms <10 ms gige9-0.hsipaccess1.Philadelphia1.Level3.net [64.159.0.146] 11 <10 ms 15 ms 47 ms unknown.Level3.net [63.209.178.162] 12 <10 ms <10 ms 16 ms 66.54.175.194 13 16 ms 15 ms 31 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109] 14 <10 ms 16 ms 15 ms o1-53s11.phl054si01.yipes.com [66.54.144.190] 15 <10 ms 31 ms 15 ms 66.7.139.82 16 * * * Request timed out. 17 * * * Request timed out.
-
10-08-2002, 12:00 AM #8Web Hosting Master
- Join Date
- Nov 2001
- Posts
- 852
now i agree
-
10-08-2002, 12:01 AM #9WHT Addict
- Join Date
- Sep 2002
- Location
- Colorado, US
- Posts
- 108
looks like their internal network was just like...unplugged
Rave5 Web Solutions
http://www.rave5.com
-
10-08-2002, 12:01 AM #10Aspiring Evangelist
- Join Date
- May 2002
- Posts
- 441
back up
-
10-08-2002, 12:07 AM #11Web Hosting Master
- Join Date
- Mar 2002
- Location
- Westbury, LI NY
- Posts
- 1,705
Yes it was, I almost got my email, but now its down...
-
10-08-2002, 12:10 AM #12Disabled
- Join Date
- Apr 2002
- Posts
- 25
I think yipes is the problem.. tracerouting from my cabinet in L3 it looks like yipes is now advertising webreseller on bbn instead of L3?? Maybe it is in response to those peering issues with L3 and ATT??
-
10-08-2002, 12:17 AM #13Junior Guru Wannabe
- Join Date
- Mar 2002
- Location
- Melbourne, Australia
- Posts
- 78
down here also.
http://www.boinghosting.com.au
put the boing back into your site
-
10-08-2002, 12:18 AM #14Junior Guru Wannabe
- Join Date
- Mar 2002
- Location
- Melbourne, Australia
- Posts
- 78
and now i am back up...i spoke to soon 8)
http://www.boinghosting.com.au
put the boing back into your site
-
10-08-2002, 12:53 AM #15Web Hosting Master
- Join Date
- Jun 2001
- Posts
- 960
One of my servers in Webreseller was also down for several minutes. The other server was not. I guess they're not on the same subnet and not sure what happened though.
-
10-08-2002, 07:53 AM #16Disabled
- Join Date
- Sep 2001
- Location
- Pennsylvania
- Posts
- 248
This was posted last night in our forum:
We had experienced a periodic outage due to a DOS attack. We acted as quickly as possible to get the issues resolved. Some segments of the network were out longer than others to help us determine the cause of the problem. We are working with Yipes! over this week to help prevent this type of issue from happening again. The outages spanned a period of about 30 minutes, but most segments were out for only a total of 10 to 15 minutes. I sincerely apologize for any inconvenience this has caused.