Just wanted to also throw my hat into the ring for the same problems. Mine has actually gotten worse as time wears on to the point that I can barely even use the internet on my '11 2.2 MBP. Here is a copy of my ping times (using the sudo .2 command):
64 bytes from 192.168.1.1: icmp_seq=3163 ttl=64 time=20.338 ms
64 bytes from 192.168.1.1: icmp_seq=3164 ttl=64 time=6.277 ms
64 bytes from 192.168.1.1: icmp_seq=3165 ttl=64 time=2.198 ms
64 bytes from 192.168.1.1: icmp_seq=3166 ttl=64 time=1.832 ms
64 bytes from 192.168.1.1: icmp_seq=3167 ttl=64 time=24.496 ms
64 bytes from 192.168.1.1: icmp_seq=3168 ttl=64 time=5.588 ms
64 bytes from 192.168.1.1: icmp_seq=3169 ttl=64 time=3.701 ms
64 bytes from 192.168.1.1: icmp_seq=3170 ttl=64 time=1.844 ms
64 bytes from 192.168.1.1: icmp_seq=3171 ttl=64 time=10.581 ms
64 bytes from 192.168.1.1: icmp_seq=3172 ttl=64 time=1.684 ms
64 bytes from 192.168.1.1: icmp_seq=3173 ttl=64 time=3.223 ms
64 bytes from 192.168.1.1: icmp_seq=3174 ttl=64 time=4.902 ms
64 bytes from 192.168.1.1: icmp_seq=3175 ttl=64 time=1.846 ms
64 bytes from 192.168.1.1: icmp_seq=3176 ttl=64 time=2.729 ms
64 bytes from 192.168.1.1: icmp_seq=3177 ttl=64 time=1.786 ms
64 bytes from 192.168.1.1: icmp_seq=3178 ttl=64 time=3.268 ms
64 bytes from 192.168.1.1: icmp_seq=3179 ttl=64 time=9.703 ms
64 bytes from 192.168.1.1: icmp_seq=3180 ttl=64 time=1.763 ms
64 bytes from 192.168.1.1: icmp_seq=3181 ttl=64 time=1.798 ms
64 bytes from 192.168.1.1: icmp_seq=3182 ttl=64 time=2.005 ms
64 bytes from 192.168.1.1: icmp_seq=3183 ttl=64 time=18.417 ms
64 bytes from 192.168.1.1: icmp_seq=3184 ttl=64 time=7.694 ms
64 bytes from 192.168.1.1: icmp_seq=3185 ttl=64 time=7.208 ms
64 bytes from 192.168.1.1: icmp_seq=3186 ttl=64 time=1.696 ms
64 bytes from 192.168.1.1: icmp_seq=3187 ttl=64 time=6.615 ms
64 bytes from 192.168.1.1: icmp_seq=3188 ttl=64 time=5.701 ms
64 bytes from 192.168.1.1: icmp_seq=3189 ttl=64 time=88.422 ms
64 bytes from 192.168.1.1: icmp_seq=3190 ttl=64 time=36.572 ms
64 bytes from 192.168.1.1: icmp_seq=3191 ttl=64 time=2.410 ms
64 bytes from 192.168.1.1: icmp_seq=3192 ttl=64 time=95.097 ms
64 bytes from 192.168.1.1: icmp_seq=3193 ttl=64 time=72.629 ms
64 bytes from 192.168.1.1: icmp_seq=3194 ttl=64 time=52.344 ms
64 bytes from 192.168.1.1: icmp_seq=3195 ttl=64 time=17.863 ms
64 bytes from 192.168.1.1: icmp_seq=3196 ttl=64 time=2.800 ms
64 bytes from 192.168.1.1: icmp_seq=3197 ttl=64 time=104.132 ms
64 bytes from 192.168.1.1: icmp_seq=3198 ttl=64 time=64.492 ms
64 bytes from 192.168.1.1: icmp_seq=3199 ttl=64 time=28.975 ms
64 bytes from 192.168.1.1: icmp_seq=3200 ttl=64 time=1.856 ms
64 bytes from 192.168.1.1: icmp_seq=3201 ttl=64 time=145.971 ms
64 bytes from 192.168.1.1: icmp_seq=3202 ttl=64 time=84.563 ms
64 bytes from 192.168.1.1: icmp_seq=3203 ttl=64 time=47.650 ms
64 bytes from 192.168.1.1: icmp_seq=3204 ttl=64 time=8.328 ms
64 bytes from 192.168.1.1: icmp_seq=3205 ttl=64 time=32.229 ms
64 bytes from 192.168.1.1: icmp_seq=3206 ttl=64 time=5.354 ms
64 bytes from 192.168.1.1: icmp_seq=3207 ttl=64 time=2.126 ms
64 bytes from 192.168.1.1: icmp_seq=3208 ttl=64 time=2.615 ms
Request timeout for icmp_seq 3209
64 bytes from 192.168.1.1: icmp_seq=3210 ttl=64 time=2.834 ms
64 bytes from 192.168.1.1: icmp_seq=3211 ttl=64 time=1.813 ms
64 bytes from 192.168.1.1: icmp_seq=3212 ttl=64 time=5.462 ms
64 bytes from 192.168.1.1: icmp_seq=3213 ttl=64 time=15.580 ms
64 bytes from 192.168.1.1: icmp_seq=3214 ttl=64 time=10.390 ms
I do notice when I have unusually high pings that my internet becomes absolutely unusable as I get an error that the server can't be found (in Chrome, Safari & Firefox). My recent '10 i7 MBP has had ZERO issues since purchasing it in Sept '10 and this one has had issues since I got it 3 weeks ago. I've also reseted all hardware involved and can confirm low ping times and very stable internet using iPhone 4, 2 other Windows7 PCs and my other MBP.
There needs to be a fix QUICKLY as not being able to confidently access the internet pretty much makes this thing an expensive aluminum paperweight.
I would call up AppleCare, but that seems like it does zero good. Keeping my fingers crossed for a software fix soon but until then, I have to USB tether to my iPhone to have reliable internet -_-