This wasn't a server issue or site issue that happened. (It ended just a few minutes ago.)
As far as I'm aware of, it appears to be a switch failure. However, during the outage, I received unconfirmed reports from others in the same DC (Datacenter), that it wasn't just them, that the entire DC was down.
I will post back when I find out the cause.
As of 8:07 EST, 67.43.62.130 (a system operated by EidolonHost, a ShatteredTears subsidary) encountered issues with upstream routing as evident by this traceroute from ST-NOC:
Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert serv1.deaftechsupport.com
Tracing route to serv1.deaftechsupport.com [67.43.62.130]
over a maximum of 30 hops:
1 171 ms 192 ms 177 ms 10.144.76.1
2 * 248 ms 229 ms 66-168-128-169.static.krny.ne.charter.com [66.16
8.128.169]
3 188 ms * 70 ms 66-168-128-1.static.krny.ne.charter.com [66.168.
128.1]
4 176 ms * 176 ms 66-168-128-145.static.krny.ne.charter.com [66.16
8.128.145]
5 135 ms 142 ms 184 ms 12.125.72.73
6 245 ms * 250 ms cr2.sl9mo.ip.att.net [12.122.142.170]
7 260 ms 290 ms 238 ms cr2.cgcil.ip.att.net [12.122.2.21]
8 229 ms 187 ms 172 ms cgcil01jt.ip.att.net [12.122.86.41]
9 * 182 ms 198 ms 192.205.34.166
10 227 ms 201 ms 227 ms ColoGuys.GigabitEthernet6-34.ar2.DAL2.gblx.net [
64.213.23.54]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
As of a few minutes ago, a member in the DS IRC channel hosted on ShatteredTears, Doujinstyle and other affiliated network, responded:
[07:02:20:PM] <14zjhentohlauedy> oh i got back on ds D:
[07:02:47:PM] <14Zak> you did not
[07:03:57:PM] <04Keiro> DS is now back online.
roughly at that time, MST.
Page 1 of 1
Server Downtime Info
#2
Posted 29 January 2010 - 02:43 AM
Keiro, on 28 January 2010 - 07:11 PM, said:
This wasn't a server issue or site issue that happened. (It ended just a few minutes ago.)
As far as I'm aware of, it appears to be a switch failure. However, during the outage, I received unconfirmed reports from others in the same DC (Datacenter), that it wasn't just them, that the entire DC was down.
I will post back when I find out the cause.
As of 8:07 EST, 67.43.62.130 (a system operated by EidolonHost, a ShatteredTears subsidary) encountered issues with upstream routing as evident by this traceroute from ST-NOC:
Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert serv1.deaftechsupport.com
Tracing route to serv1.deaftechsupport.com [67.43.62.130]
over a maximum of 30 hops:
1 171 ms 192 ms 177 ms 10.144.76.1
2 * 248 ms 229 ms 66-168-128-169.static.krny.ne.charter.com [66.16
8.128.169]
3 188 ms * 70 ms 66-168-128-1.static.krny.ne.charter.com [66.168.
128.1]
4 176 ms * 176 ms 66-168-128-145.static.krny.ne.charter.com [66.16
8.128.145]
5 135 ms 142 ms 184 ms 12.125.72.73
6 245 ms * 250 ms cr2.sl9mo.ip.att.net [12.122.142.170]
7 260 ms 290 ms 238 ms cr2.cgcil.ip.att.net [12.122.2.21]
8 229 ms 187 ms 172 ms cgcil01jt.ip.att.net [12.122.86.41]
9 * 182 ms 198 ms 192.205.34.166
10 227 ms 201 ms 227 ms ColoGuys.GigabitEthernet6-34.ar2.DAL2.gblx.net [
64.213.23.54]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
As of a few minutes ago, a member in the DS IRC channel hosted on ShatteredTears, Doujinstyle and other affiliated network, responded:
[07:02:20:PM] <14zjhentohlauedy> oh i got back on ds D:
[07:02:47:PM] <14Zak> you did not
[07:03:57:PM] <04Keiro> DS is now back online.
roughly at that time, MST.
As far as I'm aware of, it appears to be a switch failure. However, during the outage, I received unconfirmed reports from others in the same DC (Datacenter), that it wasn't just them, that the entire DC was down.
I will post back when I find out the cause.
As of 8:07 EST, 67.43.62.130 (a system operated by EidolonHost, a ShatteredTears subsidary) encountered issues with upstream routing as evident by this traceroute from ST-NOC:
Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert serv1.deaftechsupport.com
Tracing route to serv1.deaftechsupport.com [67.43.62.130]
over a maximum of 30 hops:
1 171 ms 192 ms 177 ms 10.144.76.1
2 * 248 ms 229 ms 66-168-128-169.static.krny.ne.charter.com [66.16
8.128.169]
3 188 ms * 70 ms 66-168-128-1.static.krny.ne.charter.com [66.168.
128.1]
4 176 ms * 176 ms 66-168-128-145.static.krny.ne.charter.com [66.16
8.128.145]
5 135 ms 142 ms 184 ms 12.125.72.73
6 245 ms * 250 ms cr2.sl9mo.ip.att.net [12.122.142.170]
7 260 ms 290 ms 238 ms cr2.cgcil.ip.att.net [12.122.2.21]
8 229 ms 187 ms 172 ms cgcil01jt.ip.att.net [12.122.86.41]
9 * 182 ms 198 ms 192.205.34.166
10 227 ms 201 ms 227 ms ColoGuys.GigabitEthernet6-34.ar2.DAL2.gblx.net [
64.213.23.54]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
As of a few minutes ago, a member in the DS IRC channel hosted on ShatteredTears, Doujinstyle and other affiliated network, responded:
[07:02:20:PM] <14zjhentohlauedy> oh i got back on ds D:
[07:02:47:PM] <14Zak> you did not
[07:03:57:PM] <04Keiro> DS is now back online.
roughly at that time, MST.
... >__________________>
Someone NOW tells me about how to do the Announcements. D:
Kinda my fault for not figuring out where things are. >_______> Yes, I'm still learning my way around, and had thought this might be the best way to handle stuff related to DS's server. >_>
Oh Karusune!!!!~ XD
Keiro D.
Systems and Network Administrator, EidolonHost.com CEO

A shattered Warrior... waiting for peace.
Systems and Network Administrator, EidolonHost.com CEO

A shattered Warrior... waiting for peace.
Page 1 of 1

Sign In
Register
Help


MultiQuote