question about Plogue and Bidule

[Gate 13]

I didn't know where to post this question.
sorry
But I had a really long break from composing (due to pursuing a master in computer science) and I am trying to upadte all of my software but when I try to visit plogue.com it is not working...
i tried plogue forums, and still not working.
is there server down? is this company a past?
What the heck??

[MIDI Life Crisis]

I was able to get in here: http://www.plogue.com/products/bidule/

[Gate 13]

Thanks but I am afraid is not working for me.

weird....

[MIDI Life Crisis]

Can you try a different browser?

[Gate 13]

i tried 2 different computers
mac with safari
pc with IE and firefox....
no results....
very weird...
can you enter their website?
am i the only one with this problem? lol!

[MIDI Life Crisis]

I was able to get to both the link as well as the forum. Are you getting an error message or just hung up?

[Gate 13]

"The connection has timed out
The server at www.plogue.com is taking too long to respond."

don't worry I will figure out....
thanks anyway!

[MIDI Life Crisis]

K

[dix]

Not working for me either. Times out. Weird

[bayswater]

I can get in with Safari.

[dix]

Not me with Safari. …coincidentally I was planning on searching their forums today re intermittent timing issues I'm getting on certain DP files. I will be patient.

[seb@plogue]

For anyone having problems connecting to the site:

Could you send
a) your ip address (obviously not the one on your home network but
the one for your modem/router connected to the net)
b) the output of a traceroute to plogue.com

We were on the receiving end of some botnet noise traffic and made a few changes to the web server configuration to not have that take away all resources. I'm wondering if this is what's causing the timeout for some people, hence why we're collecting info to send to our web hosting provider.

[dix]

I'm different type of techno geek, but I think it's 69.181.56.167 …i typed "what's my ip" into google and that's what i got.

[seb@plogue]

for b), you need to open a Terminal Window and type/paste:
traceroute www.plogue.com
then you should see a list with increasing numbers and names/numbers,
that's what I also need.

[dix]

So:

traceroute www.plogue.com
traceroute to plogue.com (216.92.27.221), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 8.229 ms 2.975 ms 0.719 ms
2 10.0.0.1 (10.0.0.1) 2.196 ms 1.228 ms 2.373 ms
3 69.181.56.1 (69.181.56.1) 18.386 ms 11.066 ms 9.710 ms
4 te-8-8-ur02.sfmission.ca.sfba.comcast.net (68.85.103.141) 23.884 ms 15.404 ms 9.333 ms
5 te-0-0-0-18-sur04.fremont.ca.sfba.comcast.net (68.85.57.122) 9.631 ms 10.425 ms 10.185 ms
6 te-1-12-0-6-ar01.oakland.ca.sfba.comcast.net (68.85.154.142) 13.331 ms
ge-2-1-ur01.castrovalley.ca.sfba.comcast.net (68.87.192.105) 14.440 ms 9.850 ms
7 be-90-ar01.sfsutro.ca.sfba.comcast.net (68.85.155.14) 15.462 ms 16.403 ms 11.966 ms
8 he-1-7-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.153) 17.322 ms 14.010 ms 20.001 ms
9 50.242.148.34 (50.242.148.34) 12.877 ms 16.406 ms 11.340 ms
10 vlan70.csw2.sanjose1.level3.net (4.69.152.126) 78.905 ms 82.801 ms
vlan80.csw3.sanjose1.level3.net (4.69.152.190) 84.013 ms
11 ae-92-92.ebr2.sanjose1.level3.net (4.69.153.29) 79.557 ms
ae-62-62.ebr2.sanjose1.level3.net (4.69.153.17) 94.829 ms
ae-81-81.ebr1.sanjose1.level3.net (4.69.153.9) 93.535 ms
12 ae-5-5.ebr1.sanjose5.level3.net (4.69.148.137) 79.834 ms
ae-2-2.ebr2.sanjose5.level3.net (4.69.148.141) 79.069 ms 87.350 ms
13 ae-1-100.ebr2.sanjose5.level3.net (4.69.148.110) 82.066 ms 78.714 ms
ae-6-6.ebr2.losangeles1.level3.net (4.69.148.201) 82.294 ms
14 ae-6-6.ebr2.losangeles1.level3.net (4.69.148.201) 82.316 ms
ae-3-3.ebr3.dallas1.level3.net (4.69.132.78) 80.322 ms
ae-6-6.ebr2.losangeles1.level3.net (4.69.148.201) 86.172 ms
15 ae-3-3.ebr3.dallas1.level3.net (4.69.132.78) 81.485 ms
ae-63-63.csw1.dallas1.level3.net (4.69.151.133) 78.928 ms 84.839 ms
16 ae-91-91.ebr1.dallas1.level3.net (4.69.151.162) 79.232 ms
ae-83-83.csw3.dallas1.level3.net (4.69.151.157) 80.025 ms
ae-71-71.ebr1.dallas1.level3.net (4.69.151.138) 80.486 ms
17 ae-91-91.ebr1.dallas1.level3.net (4.69.151.162) 79.486 ms
ae-81-81.ebr1.dallas1.level3.net (4.69.151.150) 109.141 ms
ae-61-61.ebr1.dallas1.level3.net (4.69.151.126) 82.745 ms
18 ae-5-5.ebr2.chicago1.level3.net (4.69.140.193) 81.160 ms 80.901 ms
ae-14-14.ebr2.chicago2.level3.net (4.69.151.117) 80.902 ms
19 ae-6-6.ebr1.chicago1.level3.net (4.69.140.189) 81.849 ms 80.836 ms
ae-5-5.ebr2.chicago1.level3.net (4.69.140.193) 78.816 ms
20 ae-1-100.ebr1.chicago1.level3.net (4.69.151.177) 80.731 ms 86.868 ms
ae-6-6.ebr1.chicago1.level3.net (4.69.140.189) 79.244 ms
21 ae-11-11.car1.pittsburgh3.level3.net (4.69.135.245) 82.236 ms 79.059 ms
ae-3-3.car2.pittsburgh3.level3.net (4.69.135.249) 253.018 ms
22 ae-11-11.car1.pittsburgh3.level3.net (4.69.135.245) 80.928 ms
continental.car1.pittsburgh3.level3.net (4.49.116.254) 89.365 ms 84.137 ms
23 continental.car1.pittsburgh3.level3.net (4.49.116.254) 79.807 ms * *
24 * plogue.com (216.92.27.221) 85.931 ms *