We’ve been pushing out changes to auth over the past few weeks, transitioning oauth token handling from an old service to a new service. Many bugs seem to have come up as a part of this, and we’re addressing them as they are found.
It looks like one of those spikes was indeed a bug that was handled recently, and there is a known bug from today that might cause a spike.