Yes, it's been creeping up over the past few weeks and not reducing.
It may be unrelated, but they have a (Chrome) bug in the web site that isn't handling cookie time-outs correctly. If you don't logout but close the browser window the active cookie is left behind. Next time you visit the site from that PC (browser) the menu indicates you can view your Dashboard (suggesting you're still logged in), but clicking this flicks back to the login page. Clicking Logout before trying to Login works around this.
They have a number of basic web app bugs in the login page that are quite annoying and their support team don't seem to respond on these. They're a two minute fix and would really improve the user experience;
1. The email field should 'toLower' and trim blanks before trying to validate the input value. Auto-complete keyboards on mobile devices will often leave a trailing space (e.g. Swiftkey on Android) and this causes the email validation to fail.
2. The username/email field should probably gain focus automatically when the login page loads. This would reduce the number of clicks the user has to complete in order to log in.
3. Press 'enter' while the username/email field has focus should only trigger the login button if the password field has a value, otherwise it should put focus to the password field.
These are basic functional test failures that give me some raise for concern that if these aren't working correctly, what else, that's more complex, is not being tested and fixed...?
Sorry, slightly on a soap box, but really, these are basic web dev issues that are 'low risk' but make the login UX better. Which I guess is what they want?