It looks like the proxy is still connected to the pool:
2014-01-24 06:45:34,548 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:34,600 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:34,653 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:34,705 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:34,757 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:34,810 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:36,363 INFO proxy client_service.handle_event # New job 7af38b9 for prevhash 06de5ca8, clean_jobs=False
2014-01-24 06:45:44,955 INFO proxy getwork_listener._on_authorized # Worker 'worker.1' asks for new work
2014-01-24 06:45:56,288 INFO proxy client_service.handle_event # New job 7af38ba for prevhash 06de5ca8, clean_jobs=False
2014-01-24 06:46:06,368 INFO proxy client_service.handle_event # New job 7af38bb for prevhash 06de5ca8, clean_jobs=False
2014-01-24 06:46:16,817 INFO proxy client_service.handle_event # New job 7af38bc for prevhash 06de5ca8, clean_jobs=False
This is what it looks like on the blade side:
Total MHS: 00000
Received: 0000000009
Accepted: 0000000000
Per Minute: 000.00
Efficiency: 000.00%
Up Time: 0d,00h,01m,31s
Current Server: 192.168.0.253:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
I'm currently connected to Ghash, but I was having the same trouble with BTCGuild.