I can't access my servers @ webreseller., and their main site is down, too. :bawling:
Is this because the move of their DC ?

My server is down too. Please get it back online ASAP :(...

down too, I am hoping that it is the 15 or the 25 minute outage that we are too expect, otherwise not a good sign. But this seems odd since the whole network is down, not just a subnet.

-Steven

my server is down too, AIM to webreseller, but have no response. I have a very important presentation tomorrow, so I hope they can fix the problem very soon!

traceroute to 66.54.216.79 (66.54.216.79), 30 hops max, 38 byte packets
1 gateway (63.208.72.1) 0.381 ms 0.363 ms 0.332 ms
2 gigabitethernet5-1.core2.Chicago1.Level3.net (209.244.8.25) 0.399 ms 0.404 ms 0.344 ms
3 so-4-1-0.mp2.Chicago1.Level3.net (209.247.10.173) 0.582 ms 0.642 ms 0.601 ms
4 so-2-0-0.mp2.Denver1.Level3.net (209.247.9.81) 23.298 ms 23.299 ms 23.271 ms
5 gigabitethernet11-0.hsipaccess1.Denver1.Level3.net (64.159.3.126) 23.490 ms 23.539 ms 23.471 ms
6 unknown.Level3.net (63.211.250.18) 23.596 ms 23.656 ms 23.594 ms
7 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.492 ms 23.567 ms 23.493 ms
8 unknown.Level3.net (63.211.250.18) 23.617 ms 23.659 ms 23.631 ms
9 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.516 ms 37.583 ms 23.613 ms
10 unknown.Level3.net (63.211.250.18) 23.635 ms 23.733 ms 23.706 ms
11 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.805 ms 23.640 ms 26.043 ms
12 unknown.Level3.net (63.211.250.18) 23.720 ms 23.746 ms 23.677 ms
13 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.572 ms 23.640 ms 23.612 ms
14 unknown.Level3.net (63.211.250.18) 23.697 ms 23.760 ms 23.821 ms
15 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.594 ms 23.909 ms 23.634 ms
16 unknown.Level3.net (63.211.250.18) 23.769 ms 23.875 ms 23.723 ms
17 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.623 ms 23.723 ms 23.665 ms
18 unknown.Level3.net (63.211.250.18) 23.795 ms 23.817 ms 23.760 ms
19 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.675 ms 23.816 ms 23.671 ms
20 unknown.Level3.net (63.211.250.18) 23.764 ms 23.967 ms 23.793 ms
21 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.818 ms 23.832 ms 23.710 ms
22 unknown.Level3.net (63.211.250.18) 25.376 ms 23.865 ms 23.884 ms
23 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.697 ms 23.830 ms 23.797 ms
24 unknown.Level3.net (63.211.250.18) 23.840 ms 23.957 ms 23.830 ms
25 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.725 ms 23.852 ms 23.786 ms
26 unknown.Level3.net (63.211.250.18) 23.872 ms 23.987 ms 24.010 ms
27 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.755 ms 23.908 ms 23.756 ms
28 unknown.Level3.net (63.211.250.18) 23.861 ms 24.052 ms 23.885 ms
29 gigabitethernet8-0-515.hsipaccess1.Denver1.Level3.net (63.211.250.17) 23.800 ms 23.873 ms 23.814 ms
30 unknown.Level3.net (63.211.250.18) 23.938 ms 24.551 ms 23.975 ms

I am thinking that the routes to the old datacenter are being configured to go to the new datacenter?? They are in the middle of the process either that or something bad has happend.

I'm having the same issue with level3 routing.

Originally posted by johnallen
I'm having the same issue with level3 routing.
Word from further up the chain from me is that a core router failed in Denver somewhere between Yipes and Level3.

ETA I got was 15 minutes but treat all this with a major pinch of salt because I got it about 4th hand...

*multiplies ETA by 3 and adds and hour* ;)

An hour down now :(

Hi,

My server is also down, verry bad i'have a demonstration today for new customers !

Originally posted by WebSnail.net

Word from further up the chain from me is that a core router failed in Denver somewhere between Yipes and Level3.

ETA I got was 15 minutes but treat all this with a major pinch of salt because I got it about 4th hand...

*multiplies ETA by 3 and adds and hour* ;)


Denver? webreseller is in PA. Yipes doesnt have there own national backbone, at every point of presence that level3 is at they feed off them to the local city etc..

For example:
traceroute yipes.com
traceroute to yipes.com (209.213.209.72), 30 hops max, 38 byte packets
1 gateway (63.208.72.1) 0.398 ms 0.359 ms 0.333 ms
2 gigabitethernet5-1.core2.Chicago1.Level3.net (209.244.8.25) 0.401 ms 0.406 ms 0.427 ms
3 so-4-1-0.mp2.Chicago1.Level3.net (209.247.10.173) 0.613 ms 0.629 ms 0.592 ms
4 so-3-0-0.mp2.SanFrancisco1.Level3.net (209.247.8.90) 55.162 ms 55.209 ms 55.125 ms
5 pos9-0.core1.SanFrancisco1.Level3.net (209.247.10.234) 55.603 ms 55.213 ms 55.126 ms
6 unknown.Level3.net (209.244.14.194) 55.192 ms 55.157 ms 55.134 ms
7 unknown.Level3.net (63.211.150.226) 55.250 ms 55.297 ms 55.241 ms
8 66.7.154.129 (66.7.154.129) 55.693 ms 55.658 ms 55.620 ms
9 209.213.196.205 (209.213.196.205) 55.836 ms 55.721 ms 55.738 ms
10 209.213.209.38 (209.213.209.38) 55.802 ms 55.782 ms 55.808 ms
11 pecos.yipes.com (209.213.209.72) 56.004 ms 56.033 ms 55.936 ms


You are probably right, there must be a router down somwhere but more then likely in PA and not in denver.

Originally posted by globalwebhos
Denver? webreseller is in PA. Yipes doesnt have there own national backbone, at every point of presence that level3 is at they feed off them to the local city etc.. (snip)

You are probably right, there must be a router down somwhere but more then likely in PA and not in denver.
ok, I got that 4th hand but the problem is not WebReseller but the Level3/Yipes connection... Granted no alternate has kicked in which gives cause for concern... but the clue might be found in the traceroute earlier in this thread that stops at Denver.

5 gigabitethernet11-0.hsipaccess1.Denver1.Level3.net (64.159.3.126) 23.490 ms 23.539 ms 23.471 ms
6 unknown.Level3.net (63.211.250.18) 23.596 ms 23.656 ms 23.594 ms

From all the information I got this is a connection provider issue ... But, I digress, probably better coming from the horses mouth.

Originally posted by WebSnail.net

*multiplies ETA by 3 and adds and hour* ;)

Don't do that :(

:D

From France, Webreseller's site is totally down. Maybe they have some problems with the move.

Originally posted by diederik
Don't do that :(

:D
:D Well it could be worse... We could be using my BU**T calculation...

2 hours to get any info + (ETA * 5) + 3 hours.

:stickout

1 ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 4 msec
ge-6-1-0.mp2.Philadelphia1.level3.net (64.159.3.29) 0 msec
ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 0 msec
2 so-2-0-0.mp1.Chicago1.Level3.net (64.159.0.233) 36 msec 36 msec 32 msec
3 pos8-0.core2.Chicago1.Level3.net (209.247.10.166) 32 msec 36 msec 36 msec
4 gige6-0.ipcolo2.Chicago1.Level3.net (209.244.8.46) 36 msec 36 msec 36 msec
5 web2.globalwebhost.com (63.208.72.6) 36 msec 36 msec 32 msec


Well L3 is alive in PA ............ Reason it keeps bouncing to Denver is the BGP kicking in, it keeps trying to find another route but there isnt one so it keeps bouncing..

Like i said before though, they are moving to another location and they are keeping the same network blocks/ip's etc.. so many things could happend, they need to take down the network in the old datacenter and bring it up in the new datacenter ?? Who knows tho, like snail said best if we hear it from the horses mouth! Its 4am here but i cant sleep until i know it is up...

This is the first time ive experienced any downtime with webreseller which is a good thing, im sure they will get us back up in no time..

My server works again many thanks webreseller

And we are backup! ;)

This was sent out July 5th

Dear WebReseller.Net Customer,

Please review the following information for maintenance details:

Date: July 11, 2002
Time: 12:00am to 4:00am EST

Customer Impact:
Might see (3-5) 45 second hits as switching & routing protocols reconverge within this maintenance window.

Yipes is improving its infrastructure with the following maintenance activity: Core architectural design improvements to increase predictability & reliability.

Originally posted by WCSWEB
This was sent out July 5th

Dear WebReseller.Net Customer,

Please review the following information for maintenance details:

Date: July 11, 2002
Time: 12:00am to 4:00am EST

Customer Impact:
Might see (3-5) 45 second hits as switching & routing protocols reconverge within this maintenance window.

Yipes is improving its infrastructure with the following maintenance activity: Core architectural design improvements to increase predictability & reliability.

We never received that email, consider yourself lucky, as we were pulling our hair out.

-Steven

lol, do you have any hair left?

So, where are the new datacenter of Webreseller now ? :) (The new site is not online so the move must not be finish)

Dear WebReseller.Net Customer,

We are approaching the final stages of our move to the new data center. At this point we must work with Yipes! and Level3 to transfer our connection to our new facility. What will be happening is Yipes! will be transferring our Net service from our old location to our new location. The transfer over should take only about 10 minutes to complete. However, there may be some added time to this if there are some unforeseen circumstances. This stage of the move will help eliminate any latency issues that you may be experiencing.


Date: July 12, 2002
Time: 1:00pm to 1:30pm EST


We apologize that this move must be done during normal business hours. There are however a number of reasons why we are taking this route. The first and most important reason; is to ensure that the connection can be moved as quickly as possible. We will also have a full staff to take care of any problems that may arise from this move. We do not expect any problems with the move, but there are always circumstances that can go out of control. Additionally, we will have the full support of Yipes! and Level3\'s support teams to ensure a minimal down time.

Any questions or comments related to this problem should be sent to move@webreseller.net. Also during this downtime our Help Desk and Site will not be accessible.


-WebReseller.Net Support Team

Hi JBIZ718

Is the new Datacentre supporting multihomed lines? Which other providers you are adding other than yipes ?

I need to have a quote for windows server & had left a message at your chat centre ..no reply till now. Can you PM me your prices for current windows special