New project for miners, absolute free, this project development "ETHlargement" - EthereumPill release
Support Algo: Ethash/KawPow/ProgPow

More info: https://github.com/EthereumPillProject/EthereumPill/releases/tag/1.0.0.0

Hashrate:
1080ti - 58 mh/s
2060 - 59 mh/s
2070 - 60-62 mh/s
2080 - 63-67 mh/s
2080ti - 68-71 mh/s
3070 - 76-78 mh/s
3080 - 97-99 mh/s
3090 - 115-127 mh/s

P.S.: the project is being drowned by competitors, don't trust anyone, check the information yourself

253746 appears to be fixed. Ya'll can start unbunching your panties now. 

Try bouncing your PCs network connection and flush your DNS Cache.

See my above post regarding your second question. There was definitely something wrong with Slush's setup this morning.

Your first questions sounds like either your GPU faulted (too hot, too overclocked, hardware problem) or GUIMINER had a connection issue related to your second question.  I have personally not used BFGMiner, but I have used CGMINER and GUIMINER.  CGMINER is far superior in its informational feedback and software options (overclocking options of your GPU built into the software).  I only use GUIMiner on my windows machines that are used for other things and I can't mess around with them too much. CGminer takes more time to setup and is more finicky with OpenCL drivers.  It is much easier to setup on Ubuntu (I use 12.04 LTS on my main mining rig with 2 7870 XTs and 7 ASICMINER Block Erupters).  If you are familiar with linux or up for a challenge, I would HIGHLY suggest researching and setting up a machine running Linux and CGMiner.  The pool management options are extremely useful when mining on Slush since we occasionally (not often, but still) experience server issues.  My main rig will immediately switch to BTC GUILD in the event cgminer cannot communicate with stratum.bitcoin.cz ...  

--EDIT--
Again, just my $0.00  Again, just my $0.02

Just as a forewarning... I dont think using the direct IP is necessarily a good long term option.  From what I understand, Slush uses Amazon AWS. AWS offers load balancing, geolocating\geocaching, and failover based on availability zones.  If AWS is like the Azure platform (which I work with for my job), IP addresses are not dedicated.  When you set it up, you point your regular public DNS to your AWS FQDN and then the AWS system handles DNS\Routing from there which is what allows the above Amazon services to function with little to no setup.  By specifying a server IP address, you are circumventing this feature. This may temporarily resolve an issue such as today when a specific load balancing server is down or a specific geolocation\availability zone is malfunctioning in a way that AWS doesn't recognize the malfunction and remove the specific server from the rotation.  However, long term you don't get the benefits of those options, which would be crucial if the specific server you chose fails.  Also, without dedicated IP's, there is no guarantee that server will continue to be located there after an IP lease renewal or a server reboot. 

I could be totally wrong about this, but this is why I wont use direct IPs.  I experienced the issues earlier today and I resolved them by bouncing NIC's on all my machines to reset my connection and flush old\invalid DNS data. I also bounced the proxy software on 2 of my machines that use that.  I never stopped CGMINER or GUIMINER (on my windows machine... I know I know but CGMINER throws fits on that machine) and the network bounce took less than a minute.
Just my $0.02 

Well BTC on GPU causes alot of BTU, the ASICs aren't so bad (although don't go grabbing a block erupter whiles its running, jesus those things get toasty). 
Of course my GF didn't know what BTUs were... She just used the wrong initials in an attempt to ask me how my mining was going. I give her credit for caring at all... part of the reason I love her  .   She does, however, very much like the things I buy her with my mined "BTUs" haha...

I wish I had the hashing power I have now, back then... I would have been raking in the coinage! or as my lovely girlfriend calls them.. "BTUs" haha

Short term - it's all about luck
Long Term - Higher hashrate = more blocks found

Go figure we have a blockbuster day, 1 day before I get my shipment of 5 more Block Erupters...  BOOO!

Holy spike in hashing power... from 17.5TH/s to 22TH/s in a matter of minutes!

If I had both a jalapeno and kids, I'd being hiding the mining rig for the sake of the jalapeno... not my kids!!  Hehe, but that's me and I obviously dont have kids.

Oh nevermind.  They just put a "Site under maintenance" banner up...  Which is code for "Oh crap, something is wrong and we need some time to figure it out"

Anyone else having issues with blockchain.info?

If ya dont mind, I'm curious what your hashrate is... 3.5GH/s?

Well we apparently identified the problem... Thank you for correcting the issue Synethstesia. Our juju is returning in your absence.

 

If you read the last 1.5 pages of posts, you'll notice we were talking about it.  The pool software does this on occasion (not too often).  Usually Slush will fix it before it get completely confirmed.  Sit tight and hope Slush sees our posts.

Hey Slush... if your watching... block 246435 seems off for me... just a bit:

19090    2013-07-14 00:12:53    4:20:53    65593477    7674    0.00000133    246435    25.41995000      99 confirmations left

Help??   

Umm... no offense bitdude, but if your hardware isn't submitting shares quickly enough in short rounds... maybe its your hardware.  Up until recently I was only running GPUs and the VAST majority of short blocks were well within the acceptable variability one should expect in a short round.  Short rounds are unpredictable. If your miner(s) happen to be working on a higher diff share(s) during the short round you may not submit those in time to get in the round.  Its the nature of mining.  If you've changed your diff on your workers, maybe consider lowering it. 
All in all, the scoring system has some flaws that usually get fixed by Slush, but for the most part it works.  If you don't like the variations in pay, thats ok, there are plenty of pools with very consistent pay (PPS or PPLNS).  But don't go bashing Slush's system just cause you don't like it. Feel free to share concerns or ask questions, but bashing a system you don't seem to understand or like is kind of pointless.

we talking block erupters or BFL stuff?

bahhh... I hate crappy luck.  Like a few others have mentioned, I just upped my hashing power with some erupters but thanks to this slump, im not seeing much of a return.  Oh JOY! 

2 in a row... keep that JuJu going!