Search results

Are you saying that's yours? Doesn't look like it... Looks like Hivelocity.

I've heard that mobile carriers tend to support IPv6, at least a lot more than home ISPs. Is this true? It seems plausible due to the millions of smartphones out there, but in my experience end-user native IPv6 deployment is generally deplorable.

I have never had that problem. If you have, I'd advise you to update your browser(s).

I thought that came from the ASN WHOIS, which you are responsible for setting up?

First, the easy part: Yes, AAAA in IPv6 = A in IPv4. For the address format, it works something like this. You have a total of 8 "segments", separated by colons, just like IPv4 had four segments separated with periods. Each segment has four hex digits (0-f), for a total of 65536 total...

Thanks for letting us shovenose. Great to see AIS has finally gotten that set up. I've ticketed SwiftVM to see if they've got an allocation.

Not much advice to give, really. Just use them like regular IPv4s, except you never have to worry about running out :) If you're unfamiliar with the format of the addresses, there are plenty of tutorials/articles on the Internet covering how they're laid out. I would advise you to check with...

No. No it is not. Don't get me wrong, I like providers offering ultra-low-end VPSes, but don't advertise something you'll never have. 

FrontRangeHosting: AS54856

Happy to help, especially since it means I get a good NYC IPv6 plan :D

I know. That's what I tried to say in that quote. But that bit about ColoCrossing implementing IPv6, that's a good one Francisco, I'll have to remember it  :D

NYC -> NYC, upstream directly peered with HE.net? Might as well be native. However, in your testing, run a traceroute from your server to the HE.net NYC tunnel server IP, just out of curiosity. Thanks for helping me out with this, though. Nice thing is, once your DC goes native, I'll be all set...