Message Too Old, No Replies
Update Jagger - Part 2
1:08 am on Nov 2, 2005 (gmt 0)
8:20 am on Nov 3, 2005 (gmt 0)
Yes, Lots of DC are timing out.
Maybe we are querying them to hard ;)
Lol - Joke Reseller - (might aswell though)
8:22 am on Nov 3, 2005 (gmt 0)
>Jagger3 not visible - maybe by Friday
... and they have pulled 66.102.7.99 in the last few minutes, making it "not visible"
I think the current 216.239.57.99 is the closest yet, with sites like yahoo etc. to be filtered out.
8:25 am on Nov 3, 2005 (gmt 0)
"Jagger3 not visible yet"
No wonder, how can Google update when I am on holidays ;-)
8:27 am on Nov 3, 2005 (gmt 0)
Maybe Google DC's are under a DDOS Attack? :)
8:31 am on Nov 3, 2005 (gmt 0)
64.233.179.99 64.233.179.104 64.233.185.99 64.233.185.104 64.233.187.99 64.233.171.99 New: 64.233.171.104 New: 64.233.171.105 New: 64.233.171.147 next to turn off?
8:31 am on Nov 3, 2005 (gmt 0)
66.102.7.99 and the like must be Jagger 2 stage whatever.
Maybe Keith Richards Stage 1 :)
The DCs have not gone for me - just really really really slow.
8:33 am on Nov 3, 2005 (gmt 0)
Since this update took place I have vanished, gone with the wind....
Just came back on 216.239.57.99 , I am ecstatic!
There is hope!
8:34 am on Nov 3, 2005 (gmt 0)
Jaffstar
That DC times out on me (as well as most others)
London UK
8:36 am on Nov 3, 2005 (gmt 0)
looks like they have problems at gplex
8:39 am on Nov 3, 2005 (gmt 0)
The following dc's are showing new results, some time out/some are not, these were up a few seconds ago.
216.239.57.99
66.102.7.99
66.102.7.104
216.239.57.104
This 1222 message thread spans 123 pages: 1222 |
| 
