New Member
•
1 Message
Routing issues when connecting to Wells Fargo Residential banking site
This has been intermittent over the past week or so. Appears to be a routing issue inside of the the Akamai network and I'm hoping that one of Comcasts peering engineers can address this as it's affecting me from a downstream customer perspective.
The site is: https://connect.secure.wellsfargo.com/auth/login/do
I am able to get to https://www.wellsfargo.com just fine but it times out after trying to login.
On my TMobile 4G hotspot, I can get there just fine.
Traceroute below from my Comcast business connection
C:\>tracert connect.secure.wellsfargo.com
Tracing route to connect.secure.wellsfargo.com.akadns.net [159.45.170.156]
over a maximum of 30 hops:
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms UniFiSecurityGateway4P [192.168.1.1]
2 4 ms 4 ms 1 ms cp.local.tld [192.168.165.1]
3 4 ms 2 ms 1 ms Docsis-Gateway.hsd1.co.comcast.net [10.1.10.1]
4 311 ms 23 ms 17 ms cm-1-acr08.aurora.co.denver.comcast.net [96.120.13.177]
5 17 ms 14 ms 13 ms ae-108-rur202.aurora.co.denver.comcast.net [69.139.228.205]
6 19 ms 14 ms 17 ms ae-2-rur201.aurora.co.denver.comcast.net [68.86.104.117]
7 15 ms 15 ms 12 ms ae-4-ar01.denver.co.denver.comcast.net [68.86.128.241]
8 13 ms 17 ms 13 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121]
9 15 ms 12 ms 15 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94]
10 59 ms 52 ms 27 ms 173.167.57.142
11 37 ms 43 ms 38 ms sjo-b21-link.telia.net [213.155.133.171]
12 38 ms 36 ms 37 ms akamai-ic-317108-sjo-b21.c.telia.net [62.115.146.111]
13 58 ms 42 ms 43 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194]
14 * * * Request timed out.
15 37 ms 42 ms 39 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
16 ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] reports: Destination net unreachable.
2 4 ms 4 ms 1 ms cp.local.tld [192.168.165.1]
3 4 ms 2 ms 1 ms Docsis-Gateway.hsd1.co.comcast.net [10.1.10.1]
4 311 ms 23 ms 17 ms cm-1-acr08.aurora.co.denver.comcast.net [96.120.13.177]
5 17 ms 14 ms 13 ms ae-108-rur202.aurora.co.denver.comcast.net [69.139.228.205]
6 19 ms 14 ms 17 ms ae-2-rur201.aurora.co.denver.comcast.net [68.86.104.117]
7 15 ms 15 ms 12 ms ae-4-ar01.denver.co.denver.comcast.net [68.86.128.241]
8 13 ms 17 ms 13 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121]
9 15 ms 12 ms 15 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94]
10 59 ms 52 ms 27 ms 173.167.57.142
11 37 ms 43 ms 38 ms sjo-b21-link.telia.net [213.155.133.171]
12 38 ms 36 ms 37 ms akamai-ic-317108-sjo-b21.c.telia.net [62.115.146.111]
13 58 ms 42 ms 43 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194]
14 * * * Request timed out.
15 37 ms 42 ms 39 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
16 ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] reports: Destination net unreachable.
ComcastBiz_Support
Administrator
•
261 Messages
5 years ago
Hi there NeotechnicCTO and welcome to the forums! I appreciate all the information you provided; would you please click on our handle (ComcastBiz_Support) and send a private message with your name, the business name, the complete service address (including city, state, ZIP, suite number, etc), and the phone or account number, and any other pertinent details so we can look into this on the backend?
-Gina
0
0