| My Blog | https://stebet.net |
| My Blog | https://stebet.net |
This has been a very long time coming, but finally, after a marathon effort, the brand new Have I Been Pwned website is now live! Feb last year is when I made the first commit to the public repo for the rebranded service, and we soft-launched the new brand in
Over 250.000 new passwords are now searchable in the @haveibeenpwned Pwned Passwords API. This data was provided by law enforcement as part of Operation NOVA, an effort to disrupt the LabHost phishing platform. The data also updated counts for over 80.000 existing passwords.
Operation NOVA is a joint law enforcement operation, spanning several countries and law enforcement agencies. You can read the announcement from the RCMP here: https://rcmp.ca/en/news/2025/04/project-nova-canadian-law-enforcement-continues-disruption-criminal-labhost-users
Over 250.000 new passwords are now searchable in the @haveibeenpwned Pwned Passwords API. This data was provided by law enforcement as part of Operation NOVA, an effort to disrupt the LabHost phishing platform. The data also updated counts for over 80.000 existing passwords.
Operation NOVA is a joint law enforcement operation, spanning several countries and law enforcement agencies. You can read the announcement from the RCMP here: https://rcmp.ca/en/news/2025/04/project-nova-canadian-law-enforcement-continues-disruption-criminal-labhost-users
tl;dr: if you use Azure SQL DB Hyperscale’s auto-scaling, it’s probably not cutting your bill down because like SQL Server, Hyperscale doesn’t automatically relinquish memory, and it’ll be up to you to manually manage your own memory if you wanna cut your bill. Now for the long story. Microsoft’s Azure SQL DB Hyperscale has an...
Azure SQL HyperScale is awesome and works wonders for
@haveibeenpwned. But it isn't perfect. We ran into some issues with how scaling in Azure SQL HyperScale works, so I decided to write a blog post about it.
https://stebet.net/autoscaling-azure-sql-hyperscale-for-better-cost-management/
I was going to write about how much I've enjoyed "tinkering" with the HIBP API, but somehow, that term doesn't really seem appropriate any more for a service of this scale. On the contrary, we're putting in huge amounts of effort to get this thing fast, stable, and sustainable. We