|
Discussion Forums
|
Thread: unreachable instance
|
|
|
Replies:
80
-
Pages:
6
[
1
2
3
4
5
| Next
]
-
Last Post:
Apr 8, 2008 12:38 AM
by: Mr Ross Cooney
|
|
|
Posts:
8
Registered:
3/21/08
|
|
|
|
unreachable instance
Posted:
Apr 7, 2008 1:51 AM PDT
|
|
|
Hi at 10.44 (GMT+1) this instance is unreachable i-3ad72453
Message was edited by: dexmachina
|
|
Posts:
4
Registered:
3/21/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 1:53 AM PDT
in response to: dexmachina
|
|
|
We have another 2 or three unreachable instances as well. Is this a repeat of what happened a few weeks ago?
|
|
Posts:
4
Registered:
3/10/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 1:54 AM PDT
in response to: Kyle Daigle
|
|
|
same here - instance i-8927dee0
|
|
Posts:
13
Registered:
7/31/07
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 1:58 AM PDT
in response to: dexmachina
|
|
|
I have about 30 instances down.
|
|
Posts:
1
Registered:
4/7/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 1:58 AM PDT
in response to: dexmachina
|
|
|
i-a2f430cb down as well.
|
|
Posts:
12
Registered:
8/22/07
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 1:59 AM PDT
in response to: dexmachina
|
|
|
We just lost a boatload of instances.
i-a56f9acc
i-4d0df824
i-400df829
i-8951aee0
i-73ba411a
i-72ba411b
i-3643bf5f
i-7e49b117
i-3d43bf54
i-c550afac
Is this a network outage or do I need to start rebuilding my cluster?
Message was edited by: Lucas Chan
|
|
Posts:
9
Registered:
3/31/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:00 AM PDT
in response to: beng21
|
|
|
Looks like there is some problem with the availability zone '
us-east-1a
', our other instances in 'us-east-1c' works fine.
|
|
Posts:
7
Registered:
8/3/07
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:01 AM PDT
in response to: dexmachina
|
|
|
Our inaccessible instances:
i-e2f50b8b, i-7e54aa17, i-db54aab2, i-1ab34873, i-1538fd7c, i-1438fd
This is everything we have in us-east-1c and us-east-1b.
[root@lcf ~]# tcptraceroute ec2-67-202-57-218.compute-1.amazonaws.com 80
Selected device eth0, address 10.0.8.224, port 52834 for outgoing packets
Tracing the path to ec2-67-202-57-218.compute-1.amazonaws.com (67.202.57.218) on TCP port 80 (http), 30 hops max
1 10.0.8.2 0.211 ms 0.186 ms 0.221 ms
2 89.174.39.109 1.487 ms 1.521 ms 1.492 ms
3 217.153.21.73 3.674 ms 4.897 ms 4.326 ms
4 taro-dbp1-so1-0-0.net.ipartners.pl (157.25.3.249) 10.170 ms * 10.003 ms
5 gsr1-pos9-0.net.ipartners.pl (157.25.3.101) 9.455 ms 9.633 ms 9.162 ms
6 195.39.208.157 23.413 ms 23.956 ms 30.349 ms
7 212.73.203.133 23.806 ms 34.988 ms 27.203 ms
8 ae-11-11.car1.Vienna1.Level3.net (4.69.135.29) 28.167 ms 24.830 ms 22.692 ms
9 ae-6-6.ebr1.Frankfurt1.Level3.net (4.69.135.34) 36.969 ms 34.944 ms 36.056 ms
10 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 48.621 ms 50.785 ms 50.915 ms
11 ae-43.ebr2.Washington1.Level3.net (4.69.137.58) 126.884 ms 134.796 ms 126.635 ms
12 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 141.357 ms 135.696 ms 126.845 ms
13 ae-11-79.car1.Washington3.Level3.net (4.68.17.71) 150.326 ms 259.638 ms 209.094 ms
14 AMAZONCOM.car1.Washington3.Level3.net (4.71.204.18) 119.190 ms 121.892 ms 121.810 ms
15 72.21.199.43 128.442 ms 126.893 ms 126.271 ms
16 72.21.199.16 257.968 ms 187.476 ms 292.615 ms
17 othr-216-182-224-93.usma1.compute.amazonaws.com (216.182.224.93) 129.040 ms 128.484 ms 129.302 ms
18 *
Our instances in us-east-1a seem to be fine.
|
|
Posts:
19
Registered:
1/15/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:01 AM PDT
in response to: dexmachina
|
|
|
instance id: i-54ce333d
My instance is also unreachable at the same time i guess. Look like major problem to me at EC2 servers
|
|
Posts:
4
Registered:
3/10/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:01 AM PDT
in response to: vholer
|
|
|
yea...appears to be the same thing here. Anything in us-east-1a or us-east-1b for that matter is unreachable.
|
|
Posts:
10
Registered:
7/2/07
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:02 AM PDT
in response to: dexmachina
|
|
|
i guess this doesn't add any info, but all our instances are down too.
|
|
Posts:
56
Registered:
9/4/07
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:04 AM PDT
in response to: vholer
|
|
|
Ditto here. Over 20 instances unreachable externally, but seem to be reachable from within EC2. All of these externally unreachable instances are in zones us-east-1a and us-east-1b -- us-east-1c seems to be fine.
|
|
Posts:
7
Registered:
7/6/07
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:04 AM PDT
in response to: dexmachina
|
|
|
Sounds redundant but over half of our instances are unreachable from the outside. Internal networking seems to be fine.
|
|
Posts:
147
Registered:
6/20/06
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:05 AM PDT
in response to: Matthew F White
|
|
|
We are investigating this. We have engaged both the service team and the networking team.
We will post to this thread with an updates as soon as we have one.
|
|
Posts:
2
Registered:
3/14/08
|
|
|
|
Re: unreachable instance
Posted:
Apr 7, 2008 2:06 AM PDT
in response to: dexmachina
|
|
|
I'm down as well (i-3f10d756).
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
