blockchain.info seems to have hard-forked itself about an hour and a half ago. My local bitcoind is up at block 237307 (hash 00000000000000dd3d053fa66aa7e336e0f8339b0a2297cdc446743d3c88bf06); blockchain.info is stuck at should-be-orphaned 237298 (hash 000000000000002bcaf84854f751e9e6d85f54a308faa12e26c84875c54d9e86). What's going on?!

If it helps: the winning chain's 237298 (hash 00000000000001045defb8087b606cae318d02a0b04403ba11a484cb1487e9d0) is the point of first disagreement, i.e. 237297 before it (hash 000000000000005baf99bd1784a0ea57bf5da1f974b3d0dd0bfcdfe68772f0b4) is the point of last agreement. Also, the two competing 237298's arrived [at my local node anyway] within seconds of each other. (Which, of course, should not be a problem.)

EDIT: All is now well! But that does still leave the question: how did such a well-connected node as blockchain.info fall so far behind in the first place?