My server connections have been getting slower and slower all day....not to mention frequent slowdowns the past couple of weeks. Is anybody there? Hello? After all this time you dont have the problems fixed? Why?

I have checked others as well and seen they are also down..this is not good....

When the engine in your car can no longer get it up the hill what do you do?
:confused:

It might be time....:(

07/08/01 20:28:45 Fast traceroute vdi.net
Trace vdi.net (216.10.16.24) ...
1 24.1.X.X 80ms 30ms 40ms TTL: 0 (x.home.net ok)
2 24.1.XXX.X 100ms 30ms 60ms TTL: 0 (x.home.net ok)
3 10.0.242.1 20ms 10ms 20ms TTL: 0 (No rDNS)
4 10.0.242.73 171ms 50ms 90ms TTL: 0 (No rDNS)
5 24.7.75.169 50ms 10ms 80ms TTL: 0 (c1-pos5-1.anhmca1.home.net ok)
6 24.7.65.165 130ms 20ms 61ms TTL: 0 (c1-pos1-0.snjsca1.home.net ok)
7 24.7.76.82 20ms 30ms 60ms TTL: 0 (c2-pos10-0.snjsca1.home.net ok)
8 24.7.69.34 90ms 90ms 70ms TTL: 0 (c1-pos7-0.cmdnnj1.home.net ok)
9 24.7.65.234 171ms 171ms 160ms TTL: 0 (c1-pos1-0.nwrknj1.home.net ok)
10 24.7.69.6 130ms 111ms 100ms TTL: 0 (c1-pos4-0.nycmny1.home.net ok)
11 209.10.13.221 221ms 100ms 121ms TTL: 0 (pos3-3-peer3.nyc1.globix.net ok)
12 209.10.12.113 170ms 170ms 120ms TTL: 0 (ge11-0-core1.nyc1.globix.net ok)
13 209.10.10.233 240ms 140ms 130ms TTL: 0 (so-5-3-0.core1.lhr2.globix.net ok)
14 209.10.11.189 220ms 120ms 130ms TTL: 0 (so-4-3-0.new-core1.lhr1.globix.net fraudulent rDNS)
15 209.10.12.194 200ms 90ms 171ms TTL: 0 (pos5-0-peer1.lhr1.globix.net ok)
16 64.28.9.33 370ms 290ms 151ms TTL: 0 (s4-1-0-lo1-gw1.cignal.net ok)
17 64.28.15.11 200ms TTL: 0 (am1-gw1.cignal.net ok)
18 64.28.15.26 280ms TTL: 0 (st1-gw1.cignal.net ok)
19 194.213.64.233 190ms TTL: 0 (tni-sto1-rc25-atm04-232.telenordia.se ok)
20 194.213.69.106 270ms TTL: 0 (tni-sto1-ri01-ge01-00.telenordia.se ok)
21 195.219.88.1 441ms TTL: 0 (Teleglobe.net fraudulent rDNS)
22 195.219.14.100 321ms TTL: 0 (if-3-2.core2.Stockholm.Teleglobe.net ok)

24 195.219.15.209 491ms TTL: 0 (if-5-0.core2.Paris2.Teleglobe.net ok)
25 195.219.15.85 280ms TTL: 0 (if-4-0.core1.Paris2.Teleglobe.net ok) :eek4::eek4::eek4:


28 216.10.16.24 321ms TTL:239 (www.vdi.net ok)


and

07/08/01 20:31:06 Fast traceroute vdi.net
Trace vdi.net (216.10.16.24) ...
1 24.1.xxx.x 120ms 10ms 30ms TTL: 0 (x.home.net ok)
2 24.1.xxx.x 150ms 40ms 81ms TTL: 0 (x.home.net ok)
3 10.0.242.1 10ms 10ms 30ms TTL: 0 (No rDNS)
4 10.0.242.73 0ms 80ms 50ms TTL: 0 (No rDNS)
5 10.0.242.73 10ms 60ms 100ms TTL: 0 (No rDNS)
6 10.0.242.73 40ms 40ms 91ms TTL: 0 (No rDNS)
7 10.0.242.73 170ms 50ms 60ms TTL: 0 (No rDNS)
8 10.0.242.73 60ms 110ms 140ms TTL: 0 (No rDNS)
9 10.0.242.73 170ms 60ms 90ms TTL: 0 (No rDNS)
10 10.0.242.73 80ms 180ms 50ms TTL: 0 (No rDNS)
11 10.0.242.73 60ms * * TTL: 0 (No rDNS)
12 10.0.242.73 50ms * * TTL: 0 (No rDNS)
13 10.0.242.73 100ms * * TTL: 0 (No rDNS)
14 10.0.242.73 40ms * * TTL: 0 (No rDNS)
15 10.0.242.73 270ms * * TTL: 0 (No rDNS)
16 10.0.242.73 0ms * * TTL: 0 (No rDNS)
17 10.0.242.73 40ms * * TTL: 0 (No rDNS)
18 10.0.242.73 60ms * * TTL: 0 (No rDNS)
19 10.0.242.73 270ms * 80ms TTL: 0 (No rDNS)
20 10.0.242.73 261ms * 100ms TTL: 0 (No rDNS)
21 10.0.242.73 170ms * * TTL: 0 (No rDNS)
22 10.0.242.73 90ms * * TTL: 0 (No rDNS)
23 10.0.242.73 120ms * * TTL: 0 (No rDNS)
24 No Response * * *
25 24.7.65.166 160ms * * TTL: 0 (pending)
26 24.7.65.165 100ms * * TTL: 0 (pending)
27 No Response * * *
28 No Response * * *
29 No Response * * *


:eek4:

They've been having troubles with L3 on and off today, I spoke with John B there about it and he said they were on the other line with them right now. Up until today they have been very solid sincs the new oc-3's went in.

-Brendan

Originally posted by mekmal
When the engine in your car can no longer get it up the hill what do you do?


Walk to the gas station and buy a 5 gallon talk of gasoline?

I would never walk for gas, getting a cab is easier:D

Originally posted by cperciva


Walk to the gas station and buy a 5 gallon talk of gasoline?

I'd rather say buy a brand new Porsche! :D

porsche, I think I would rather walk:D :D

yea, too bad it's too expensive :bawling:

Originally posted by HostAB.com


I'd rather say buy a brand new Porsche! :D



I Want One :bawling:

a used Yugo:bawling:

This thread isn't off topic yet, is it? :p

VDI has actualy been fine for me lately.

Right now I cant access VDI at all.

I've been having trouble recently but it seems to be caused by @Home flakiness... all my traffic seems to be going through snjsca which is dropping between 50% and 90% of my packets.

Since the other people reporting problems seem to be in the 24/8 netblock I'd guess they are also be effected by this same problem.

Hopefully it'll be up by tomorrow morning

slower pings than normal but no more packet loss right now.

-Brendan

pings down to 20-30ms again. looking like its back to normal maybe.

-Brendan

It hasn't been 'solid' since the upgrade, inasmuch as always being there... and it sure isn't around in a big way right now.. Level3 isn't in any tracert's from here, but the globix route is not stable either.

Level 3 has been messing up on them all day, right now the pings are good however. In since the upgrade they have not had unacceptable downtime at all.

-Brendan

ahh.. seems to be back up..

Originally posted by bbrader
Level 3 has been messing up on them all day, right now the pings are good however. In since the upgrade they have not had unacceptable downtime at all.

-Brendan

I guess the location we are in must suffer more than internal USA (which is not VDI's fault), but there HAS been an issue once a week for us since the upgrade, but these haven't been major or long lived on more than a couple of occasions... depends what 'unacceptable' means I guess.. :D

Anyway it seems to be back from here and firing away again... hallelujah...

Just for Info , the slow down was a very large dos attack, the other lines compisated the Bandwith, the dos attack was 150 MBPS according to level3.

I was just told the weehawken Center was down because of it. The ips that were getting the attack are now filtered.

There will be flapping when you get a dos and while the bgp tries to figure out what to do.

it may be possible that several of you could be going through MCI or Globix at this time since level3 is slightly limping ATM ..

AS soon as i get some info i`ll let out some...

Thanks for the update... Things are better for me now....

Don't know if this helps, but last night we had the same DOS attack issue. Our colo facility (where we house our servers - we do not use VDI) has an OC-48 from Level(3) as a primary back bone. They said the same thing, that they were having an attack. Latency was down and packet loss was at least 50%. It was fixed with in a few hours.

Sooo.. you're not alone. ;)

Doesn't look too bad to me anymore... BGP in action. I like Globix better than Level3 anyway...

Target Name: vdi.net
IP: 216.10.16.24

1 14 ms [10.110.30.1]
2 14 ms bb1-fe0-0-0.sptnbrg1.sc.home.net [24.4.112.1]
3 14 ms c1-se6-4.gnvlsc1.home.net [24.7.73.253]
4 14 ms c1-pos1-0.nrflva1.home.net [24.7.65.218]
5 14 ms c2-pos2-0.washdc1.home.net [24.7.65.213]
6 14 ms c1-pos10-0.washdc1.home.net [24.7.78.177]
7 28 ms 110.atm4-0-0-peer2.sjc1.globix.net [209.10.13.193]
8 27 ms ge-6-0-0.core1.dca3.globix.net [209.10.12.73]
9 28 ms so-1-0-0.core1.nyc8.globix.net [209.10.10.133]
10 27 ms pos10-1.core1.nyc1.globix.net [209.10.10.169]
11 27 ms ge6-0-0-hgw1.nyc1.globix.net [209.10.1.66]
12 27 ms p6-0.core1.cftnnj.inet.vdi.net [209.208.253.234]
13 27 ms vlan1.edge1.cftnnj.inet.vdi.net [216.74.127.226]
14 28 ms www.vdi.net [216.10.16.24]