Its been 32 days since I was temporarily banned. Let me give you all an update on whats happened since then:
The ipv6 ip range in question has been moved and is now announced by AS701 (Verizon USA) as part of the major overhaul to the ipv6 operations. My planned partnership with Verizon has been cemented and now completed. The BGP official announcement can be seen here: https://gyazo.com/4b4152a0167d11a47d7b06e71b9fcaf1 You can also use any public bgp mapping website yourself to verify it. My equipment (giant physical servers) have arrived on-site in the Verizon facilities and is currently being utilized to setup new ipv6 services under Verizon's flagship announcement. There will be 3 flavors of Verizon ipv6's available which will be outlined on my site later today covering around 30 States and more than 91,000 cities under the Verizon agreement details. Demographics and city/state specifics will also be precisely mapped out and publicly available.
The current traceroute:
traceroute to 2a03:b600:: (2a03:b600:

, 30 hops max, 80 byte packets
1 2001:550:1:312::1 (2001:550:1:312::1) 0.935 ms 0.931 ms
2 be3310.ccr42.dca01.atlas.cogentco.com (2001:550:0:1000::9a36:51d9) 0.988 ms be3308.ccr41.dca01.atlas.cogentco.com (2001:550:0:1000::9a36:518d) 0.824 ms
3 be3083.ccr41.iad02.atlas.cogentco.com (2001:550:0:1000::9a36:1e36) 1.545 ms 1.358 ms
4 2001:550:3::206 (2001:550:3::206) 1.061 ms 1.197 ms
5 Loopback0.GW10.DCA5.ALTER.NET (2600:803::2f) 123.767 ms 123.778 ms
6 * *
7 * *
8 * *
9 * *
10 * *
11 * *
12 * *
13 * *
14 Loopback0.GW10.DCA5.ALTER.NET (2600:803::2f) 1141.238 ms !H *
Hops # 5 and #14 are both Verizon backbone networks. The traceroute will properly complete once I make the ipv6's publicly accessible.
I would also like to note for the record that I think
@jazzc took this entire thread too far and failed to mention that the ipv6 operations and not ipv4 operations were the focus here. The original client complaint was only regarding ipv6 and nothing more. This was not outlined in any disclaimer that
@jazzc put on all my threads and should have been mentioned instead of closing down all my sales threads that had absolutely nothing to do with ipv6 operations. It is my hope that he rectifies the situation here.