Whippy - Notice history

An earlier issue that caused slow loading and blocked already logged out users from logging in has been resolved. However, we are still monitoring the fix.

The issue was caused by a bad actor trying to run a scraping bot on our systems.

We blocked this bad actor, but needed to temporally pause logins to make sure we could block all related IP Addresses.

Thank you for your patience while be resolved this issue.

We have identified the issue caused by excessive login attempts from a bad actor who we are in the process of blocking.

Some users will be unable to login. Currently logged in users should not experience any issues.

We are will post an update shortly.

Resolved Issue: We are pleased to inform you that the technical difficulties impacting our login system and API services have been resolved.

Cause of Disruption: Our team has identified that the disruption was due to an outage caused by one of our downstream cloud partners. This outage was blocking requests to our Whippy service, leading to the issues experienced by our users.

Current Status: All systems are now fully operational, and users should be able to access their accounts and use our API services without any interruptions.

Ongoing Actions: We are actively investigating this matter to understand the root cause in depth. Our aim is to implement measures that will prevent similar occurrences in the future. We are committed to maintaining a reliable and secure platform for all our users.

Acknowledgement: We sincerely apologize for any inconvenience caused and thank you for your patience and understanding during this time.