Re:Ask HN: Carrier “lost” my number in a port request
by brewtide on Wednesday November 02, 2022 @07:27PM
(#33444286)
My work number is a Google voice number, but was my 'real' number before segmentation in hopes of gaining sanity with my phone (sidenote, if anyone is self employed and busy enough to be debating such a plan, do it, no regrets), and I've had zero issues with 2FA coming through to my once a cell number now a voice number.
[ Parent
| on HN ]
Re:Ask HN: Carrier “lost” my number in a port request
by guiambros on Wednesday November 02, 2022 @10:51PM
(#33446367)
Mostly, but not every time.
I also have a Google Voice-backed number (since before Google acquisition, when it was Grand Central), and every now and then I find a site that doesn't accept GV numbers for 2FA. A recent example was Simplisafe.
Does anyone know where "Fraud Risk" and "Textable" come from in unlec's database? My number has fraud risk = high, and textable = No -- even though text works just fine via GV, and it's a personal number with minimal use, so no reason for flag (other than some companies not liking virtual carriers).