FYI

[MrChaos]

Ive been told that Guam has a US quarter in honor of it now and it says "The State of Guam". If true the level of stupidity required to get it issued is so epic it defies words

[Gstar]

No. You are wrong.

[Striker]

QUOTE (MrChaos @ Sep 27 2009, 09:22 PM) Ive been told that Guam has a US quarter in honor of it now and it says "The State of Guam". If true the level of stupidity required to get it issued is so epic it defies words

It doesn't.

http://www.usmint.gov/mint_programs/DCAndT...es&local=GU

[Gstar]

Striker is both nicer and more succinct than me. I will work toward both.

[Broodwich]

QUOTE (Gstar @ Sep 27 2009, 09:22 PM) Striker is both nicer and more succinct than me. I will work toward both.

how dare you

[MrChaos]

a) Well it was a fun idea while it lasted
b) You are both GStar and don't let McWarren tell you any different he is just jealous off your Hello Kitty collection
c) Thanks Striker I was pretty sure it was utter @#(! but it was a fun min-rant
d) I'm a little freaked out that something nice was said about you Striker and it didn't instantly turn into a five page flamefest @#(!storm

[Bard]

QUOTE (Striker @ Sep 26 2009, 02:13 PM) The odd part about all of this is the length of time it is taking to fix the issue. Most providers upgrade their equipment as needed and stay under a set percentage of their pipe. Once they hit that figure they start rolling out more equipment to handle the load before there is a bandwidth crunch.

Sadly, in this new age of virtualization, it's not all about the physical equipment.

I don't know if these guys are using a virtual machine to keep solap isolated from the other stuff they're hosting, but I've had problems with the networking drivers passing traffic from the blade NIC's to the individual VM's at speed before even though hardware was more than adequate. It was never really a problem until I had 20+ on a machine with only 3 gb NIC's, but that shouldn't be at all hard on a nice phat blade server.

[Broodwich]

so bard's saying size doesnt matter?
btw as its happening tracerts


Tracing route to solap.fe23.co.uk [66.36.240.92]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms 192.168.111.1
2 * * * Request timed out.
3 20 ms 17 ms 17 ms ge-3-41-ur01.bellevue.wa.seattle.comcast.net [68
.86.113.129]
4 26 ms 12 ms 11 ms be-50-ar01.burien.wa.seattle.comcast.net [68.86.
96.213]
5 12 ms 13 ms 14 ms be-30-ar01.seattle.wa.seattle.comcast.net [68.85
.240.69]
6 15 ms 15 ms 11 ms pos-0-3-0-0-cr01.seattle.wa.ibone.comcast.net [6
8.86.90.209]
7 16 ms 14 ms 11 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
8 29 ms 16 ms 17 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]

9 13 ms 17 ms 17 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

10 39 ms 53 ms 53 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
11 64 ms 65 ms 66 ms ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
12 68 ms 65 ms 65 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

13 97 ms 95 ms 94 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

14 99 ms 104 ms 106 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
58]
15 98 ms 109 ms 100 ms ae-41-99.car1.Washington1.Level3.net [4.68.17.19
5]
16 * * * Request timed out.
17 * * * Request timed out.
18 103 ms 102 ms * 66.36.240.92
19 103 ms 101 ms * 66.36.240.92
20 101 ms 101 ms * 66.36.240.92
21 102 ms 101 ms 103 ms 66.36.240.92

Trace complete.

Interesting i dont think i've ever seen it fail to get a 3rd ping each hop. Also this happened the first times later at night, like 7-8pm ish PST. Now its at like 4:30 =P

[FreeBeer]

*shrug* 102 ms is playable.

[spideycw]

Same problem as brood same time.

I'm jumping from 35/40 up to 160-180
Will post trace tomorrow