There are many geoIP data providers. There's no universal source for that data. You need to look at what MalePrime says your location is (see the screenshot a few messages up).
The other thing is… I see you're on IPv6. This site only uses IPv4. So that's not even the IP we're using - we're using a different one. You've used 4 different IPv4s in the past 2 weeks…
That's using BZ's internal geoIP lookup, which is NOT the same data source as what I use to do the redirects. But unless you've been traveling that's showing 4 different locations, 3 different states. But even Indiana wouldn't get you blocked since FSC got an injunction for that state. But the data provider I'm using may have put you somewhere else completely.
This is common with mobile providers - they move IPs all over the place and sometimes let you hold onto one as you move around. So it's significant that you're connecting via AT&T. You'd probably have fewer issues on something like cable-based wifi in your house.
A lot of you know that I had a stroke last year. That slowed me down a lot. Then in December I figured out I had mild to moderate case of Long Covid and that I had it for over a year (at that point - pushing 2 years now). It took me a while to be seen by specialists, get the diagnosis, and understand what I needed to do to get better. But that's happening now. The problem is (and why I'm mentioning it here) that sitting and working at my computer actually drains my energy reserves quite a bit, so I'm getting almost no programming done. I'm far better than I was 3 month ago, and starting to see signs that in the next few months computer work will be more possible. When that happens one of my first projects will be to upgrade that page on Male Prime that you see so that mobile users can basically say "your data is wrong, here let my device tell you my lat/long…" Then I'll figure out what state that is, and let you in and whitelist that Class C range for the following week. But first I need to get better…
As far as IPv6… geoIP lookups are even more difficult and unreliable for IPv6 than they are for IPv4. It's pretty safe to say everyone in a class C range is near each other, so if I have the location for one IP in the Class C, I can (fairly) safely assume the others are close by. But IPv6 is far more complicated. Let me try to break it down for you…
Your IPv6 is/was 2600:0387:000f:5b16:0:0:0:0002
The first 4 segments (2600:0387:000f:) are your "network address", the portion after that… well, it depends on how your ISP set things up. An entire company (or ISP) can all be on the same network address. From a legal compliance standpoint it's fairly safe to say that everyone at a particular network address is at least routed through a single location, but the laws don't specify how their routed, but rather the physical location of the user. AND there's no equivalent of a Class C. You have to know the location of each and every network address - and there are BILLIONS of them!