Orbiter Main forum on M6 dead ?

[Quick_Nick]

I can't possibly be the only one having problems with the main Orbiter forums!

[harmsway]

Nope. I keep getting an error. Been like that for awhile.

[jarmonik]

Same problem here

[DanSteph]

same here... error...

Dan

[Orbiter Fan]

The forum is back, at least for me.

[DanSteph]

back also...

Dan

[Simonpro]

Is it just me or has someone put a proverbial spanner in m6 again? I blame the chav influx, I do.

[StarLost]

Probably a Scottish curse ... :D :D

[Simonpro]

aye, it be a wee doggie curse on the ol' m6 forum. t'wee bairns and their jiggery pokery.

[Doug Beachy]

The forum was up this morning but went down again about two hours ago.  I contacted Donamy via MSN and he also
couldn't connect anymore.  

Here is the trace route:

>>>
Tracing route to orbit.m6.net [64.34.165.119]

over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  dlink [192.168.1.1]
  2     *        *        *     Request timed out.
  3    18 ms    19 ms     9 ms  ge-1-3-ur01.manassas.va.bad.comcast.net [68.87.135.217]
  4    21 ms    29 ms     8 ms  te-9-2-ur01.reston.va.bad.comcast.net [68.87.129.114]
  5    18 ms    11 ms    11 ms  te-9-3-ur02.arlington.va.bad.comcast.net [68.87.128.161]
  6    11 ms     9 ms     9 ms  te-9-1-ur01.arlington.va.bad.comcast.net [68.87.128.157]
  7    35 ms    12 ms    10 ms  te-9-3-ur02.alexandria.va.bad.comcast.net [68.87.128.141]
  8    10 ms    23 ms    11 ms  te-9-1-ur01.alexandria.va.bad.comcast.net [68.87.128.133]
  9    11 ms    10 ms    10 ms  te-8-1-ur01.capitolhghts.md.bad.comcast.net [68.87.128.138]
 10    11 ms    23 ms    10 ms  te-8-1-ur02.capitolhghts.md.bad.comcast.net [68.87.129.150]
 11    37 ms    10 ms     9 ms  te-9-2-ar01.capitolhghts.md.bad.comcast.net [68.87.129.145]
 12    40 ms    11 ms    12 ms  pos-2-0-cr01.ritchieroad.md.core.comcast.net [68.87.16.153]
 13    23 ms    14 ms    16 ms  12.118.122.5
 14    16 ms    14 ms    12 ms  tbr1-p010401.wswdc.ip.att.net [12.123.8.26]
 15    13 ms    16 ms    10 ms  gar1-p360.ascva.ip.att.net [12.122.80.193]
 16    10 ms    16 ms    14 ms  12.118.44.50
 17    38 ms    12 ms    58 ms  oc48-pos0-0.wdc-sp2-cor-1.peer1.net [216.187.115.234]
 18    13 ms    14 ms    14 ms  oc48-pos6-0.wdc-sbsp2-dis-1.serverbeach.com [216.187.115.238]
 19     *        *        *     Request timed out.
<<<

It looks like it may be a router problem on an oc48 backbone rather than a server problem on the M6 end.  I emailed
a heads-up to Radu and Martin just in case the problem is on the M6 end.

[Simonpro]

Radu and Martin are not really in control of M6, so there's not much they can do.

For the record, I cannot connect from Denmark - not sure if that tells you anything (i don't know what the oc48
backbone is, but it sounds important )

[Sunhillow]

When coming from Germany, the last answer comes from 208.173.10.194, so I don't think oc48 is to blame.

Routenverfolgung zu orbit.m6.net [64.34.165.119]

  1    17 ms     5 ms     4 ms  192.168.2.1
  2     *        *        *     Zeitüberschreitung der Anforderung.
  3    65 ms    64 ms    65 ms  G4-0.sgt2-g2.mcbone.net [62.104.198.34]
  4    71 ms    68 ms    67 ms  lo0-0.ffm4-j.mcbone.net [62.104.191.203]
  5    68 ms    67 ms    65 ms  f-226-9.frankfurt.ipgprs.viaginterkom.de [62.180.226.9]
  6    69 ms    68 ms    65 ms  t2c1-ge10-1.de-fra.eu.bt.net [166.49.172.105]
  7    86 ms    86 ms    83 ms  t2c1-p2-0.uk-glo.eu.bt.net [166.49.195.109]
  8    89 ms    86 ms    83 ms  t2c1-p9-1.uk-eal.eu.bt.net [166.49.208.125]
  9   165 ms   161 ms   162 ms  t2c1-p4-0.us-ash.eu.bt.net [166.49.164.110]
 10   162 ms   161 ms   163 ms  cpr2-pos-0-0.VirginiaEquinix.savvis.net [208.173.10.133]
 11   162 ms   161 ms   163 ms  208.173.10.194
 12     *        *        *     Zeitüberschreitung der Anforderung.
 13     *        *        *     Zeitüberschreitung der Anforderung.
 14     *        *        *     Zeitüberschreitung der Anforderung.