Tracert Bad Hopping Between ~7:30pm - 10 pm EST daily

[xistva]

Hi all,

Question: Wondering about my options or lack thereof to correct this issue.  Request new IP? 

Notes: Wasn't always like this - started about 5-6 weeks ago.

Description: Must be a peak usage time hop re-route or possible maintenance issue during those times that I get re-routed for.  Specifically I play ut99 as a client to a server in Florida.  Up until about 7pm EST (and after about 10 pm EST) I have a nice steady 30 ping to the server and a nice direct route.  But shortly after or around 7pm my ping jumps to an unsteady 100 ping because I get routed throguh Colorado then back to Florida.  I'm in Virginia.... why send me through Colorado to get to Florida?

Other thoughts: This is a low probability but I did recently have both my Debit card and Credit card information stolen... possible concern that someone is routing me in order to gain access to my information... but I know crap about this so... just a random thought.

Anyway: see the good vs the bad hops below.

Good Hops:

Tracing route to ash.xfactorservers.com [75.102.40.199]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     8 ms     6 ms  L100.RCMDVA-VFTTP-14.verizon-gni.net [*******]
  3     7 ms     7 ms     7 ms  G0-3-0-5.RCMDVA-LCR-22.verizon-gni.net [******]
  4    13 ms    12 ms    11 ms  P14-0-0.RCMDVA-LCR-02.verizon-gni.net [******]
  5    11 ms    12 ms    12 ms  P15-0-0.RCMDVA-LCR-01.verizon-gni.net [******]
  6    12 ms    12 ms    12 ms  so-15-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.
28.248]
  7    56 ms    14 ms    11 ms  0.xe-4-1-0.XL3.IAD8.ALTER.NET [152.63.2.249]
  8    13 ms    15 ms    14 ms  TenGigE0-4-0-1.GW7.IAD8.ALTER.NET [152.63.37.154
]
  9    18 ms    14 ms    14 ms  nlayer.customer.alter.net [152.179.50.74]
 10    13 ms    17 ms    14 ms  ae4-40g.cr2.iad1.us.nlayer.net [69.31.31.185]
 11    14 ms    11 ms    39 ms  as23352.xe-3-0-0-101.cr2.iad1.us.nlayer.net [69.
31.30.19]
 12    13 ms    15 ms    14 ms  as36352.ge-1-1-5.cr2.iad1.scnet.net.us.scnet.net
 [75.102.43.122]
 13    15 ms    14 ms    14 ms  ash.xfactorservers.com [75.102.40.199]

Trace complete.

Bad Hops:

Tracing route to 75-120-40-99.dyn.centurytel.net [75.120.40.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms     6 ms     6 ms  L100.RCMDVA-VFTTP-14.verizon-gni.net [******]
  3     9 ms     6 ms     7 ms  G0-3-0-5.RCMDVA-LCR-22.verizon-gni.net [******]
  4    10 ms    11 ms    12 ms  P14-0-0.RCMDVA-LCR-02.verizon-gni.net [******]
  5    12 ms    12 ms    11 ms  P15-0-0.RCMDVA-LCR-01.verizon-gni.net [******]
  6    73 ms   124 ms    48 ms  so-15-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.
28.248]
  7    14 ms    14 ms    14 ms  0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
  8    13 ms    11 ms    15 ms  dcp-brdr-03.inet.qwest.net [63.146.26.105]
  9   143 ms   141 ms   142 ms  min-edge-09.inet.qwest.net [67.14.21.186]
 10   145 ms   143 ms   142 ms  209.180.14.206
 11    69 ms    84 ms    69 ms  bb-kscbmonr-jx9-02-xe-1-1-0.core.centurytel.net
[206.51.69.53]
 12    88 ms    72 ms    74 ms  bb-nlrkargp-jx9-01-xe-11-1-0.core.centurytel.net
 [206.51.69.17]
 13    82 ms    59 ms    60 ms  bb-atlngamv-jx9-01-ae5-0.core.centurytel.net [20
6.51.69.197]
 14    65 ms    64 ms    64 ms  bb-plcyalxa-jm1-01-ae0-597.core.centurytel.net [
208.110.249.165]
 15    64 ms    64 ms    64 ms  GE-RB-bras.pell.centurytel.net [64.91.92.18]
 16    77 ms    74 ms    74 ms  75-120-40-99.dyn.centurytel.net [75.120.40.99]

Trace complete.

And... info about the the CO QWest location.

NetRange:       63.144.0.0 - 63.151.255.255
CIDR:           63.144.0.0/13
OriginAS:       
NetName:        QWEST-INET-8
NetHandle:      NET-63-144-0-0-1
Parent:         NET-63-0-0-0-0
NetType:        Direct Allocation
Comment:        ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
Comment:        NOTE: For abuse issues, please email abuse@qwest.net.
RegDate:        2000-03-13
Updated:        2012-02-24
Ref:            http://whois.arin.net/rest/net/NET-63-144-0-0-1

OrgName:        Qwest Communications Company, LLC
OrgId:          QCC-18
Address:        1801 California Street
City:           Denver
StateProv:      CO
PostalCode:     80202
Country:        US
RegDate:        2005-05-09
Updated:        2011-09-08
Ref:            http://whois.arin.net/rest/org/QCC-18

OrgNOCHandle: QIN-ARIN
OrgNOCName:   Qwest IP NOC
OrgNOCPhone:  +1-877-886-6515
OrgNOCEmail:  support@qwestip.net
OrgNOCRef:    http://whois.arin.net/rest/poc/QIN-ARIN

OrgAbuseHandle: QIA2-ARIN
OrgAbuseName:   Qwest Abuse
OrgAbusePhone:  +1-877-886-6515
OrgAbuseEmail:  abuse@qwest.net
OrgAbuseRef:    http://whois.arin.net/rest/poc/QIA2-ARIN

OrgTechHandle: QIA-ARIN
OrgTechName:   Qwest IP Admin
OrgTechPhone:  +1-877-886-6515
OrgTechEmail:  ipadmin@qwestip.net
OrgTechRef:    http://whois.arin.net/rest/poc/QIA-ARIN

Anyway... do I have any options to correct this?

-xistva

[Hubrisnxs]

email both of those email addresses?   tell them about the trouble you are having related to their network

[xistva]

I don't believe I have a problem with their network.  I have a problem with being routed through Colorado to get to Florida between 7:30pm est and 10:30pm est daily.

And that starts with 130.81.28.248 which is Verizon, who routes me along with ALTER.net in the wrong geographical direction entirely.

[Hubrisnxs]

Verizon doesn't do static routes through the internet, in fact most isp's do not do that.  They rely on shortest path/fastest path, so if it calculates round trip time and adjusts to the path dynamically. 

It would be unlikely that anyone at verizon would adjust your path, I think your better move is to notify the people that own he bad hop and let them know.  I think you'll have an incredibly difficult time finding anyone at verizon to do any kind of adjustment for that.   You could always do a who is on the alter.net last hop and email them, but if you call in (from my experience) you won't find anyone that really knows what your talking about.  

maybe try the twitter.com/verizonsupport - those guys seem to be more advanced vz tech's and if anyone could help you, I would imagine it's them.  definetely report back and let us know if they helped you though, so we can point people to the right entities for help.