I found this email, maybe try shooting them an email with all your traceroutes, and see what course of action they can take or what direction they point you in. This is more for the folks with latency and time outs to TINET's 'tinet-gw.customer' peering point
»drpeering.net/workshops/presos/1 ··· uses.pdf
This looks like an SLA for Peering points between several providers including verizon and TINET
It also shows verizon is using OC192's which is just a MAMMOTH connection.