The Bitstamp order book graph looks a bit funky today:

Wow, what the hell. I'll look into this. Seems to just be theirs so maybe it's the data we're getting back from their API.
There's some bug with how we're handling their socket feed... I fixed it for now by restarting our real-time service but I expect it will degrade again over time. I'll look into this. Thanks for the heads up.
. It was the first time I'd seen that happen. Hopefully it's the last.