Unable to access www.wellsfargo.com
cooper20141
Enthusiast - Level 2

we have 3 customers who are unable to access wellsfargo.com with Verizon FIOS.

the get timed out after the level 3 hop...

ae-2-70.edge3.Washington4.Level3.net [4.69.149.8]

Just loads...

0 Likes
1 Solution

Correct answers
Re: Unable to access www.wellsfargo.com
Hubrisnxs
Legend

that was likely it, it was never flushed out.  The Verizon network is quite large, if you don't leave it off long enough  then you usually get the same ip.  The four hour thing is a good way to garuntee that,. or you could release the IP (commands in the router interface) or calling vz tech support (they can do it remotely), and then the important part is to leave it dead no power no lights, no connection for at least 3, 4 5 minutes or more. 

View solution in original post

Re: Unable to access www.wellsfargo.com
smith6612
Community Leader
Community Leader

Could you share the traceroutes? It might be nice to know where a breakdown is being seen. Often, if a trace makes it outside of Verizon's network but fails elsewhere, it is a problem with either the return path to Verizon or a problem with the provider seen in the trace. Each hop seen in a traceroutes can take an entirely different return path for each pinging hop. 

Re: Unable to access www.wellsfargo.com
Telcoguru
Master - Level 1

The website is working in NY. It is probably a local issue in your area.

Re: Unable to access www.wellsfargo.com
Hubrisnxs
Legend

try changing DNS

If that doesn't work then you may want to change IP Addresses or try to at least.    the ip addresses change after 4 hours of DEAD activity.   usually unplugging it over night will do the trick.  

0 Likes
Re: Unable to access www.wellsfargo.com
cooper20141
Enthusiast - Level 2

We have 3 customers.  They are in the state of New Jersey.  One changed from another ISP to Verizon and has not been able to get to our website.  The other one upgraded their service with Verizon.  Thank you.

0 Likes
Re: Unable to access www.wellsfargo.com
cooper20141
Enthusiast - Level 2

Sorry don't have traceroute in text format. Just screen shots.

but it gets timed out after the Level3 hop.

0 Likes
Re: Unable to access www.wellsfargo.com
Hubrisnxs
Legend

If you have 3 customers were you able to tell if they were on the same subnet? 

Re: Unable to access www.wellsfargo.com
cooper20141
Enthusiast - Level 2

Yes it appears to be an issue with the patch to Level 3 communications (specifically 209.200.144.xx)

Current customer 209.200.144.35

0 Likes
Re: Unable to access www.wellsfargo.com
tns2
Community Leader
Community Leader

Note you are not talking to Verizon here but to peers(regular customers). 

I have no trouble reaching Wellsfargo

However tracerts to wellsfargo do not appear to complete and do reach the same IP you mention.  It is one that is OUTSIDE of Verizon and resolves to unknown.prologic.com.  I don't Know how Prologic does its thing but they provide protection from DOS attacks.

Tracing route to www.wellsfargo.com [159.45.2.68]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     1 ms    <1 ms    <1 ms  192.168.1.1
  3     7 ms     7 ms     7 ms  L100.TAMPFL-VFTTP-87.verizon-gni.net [71.99.77.1
]
  4    12 ms    11 ms    12 ms  G0-13-2-5.TAMPFL-LCR-22.verizon-gni.net [130.81.
105.188]
  5     *        *        *     Request timed out.
  6    15 ms    15 ms    13 ms  0.ae4.BR1.MIA19.ALTER.NET [140.222.225.113]
  7    17 ms    14 ms    16 ms  204.255.168.10
  8    59 ms    59 ms    58 ms  if-7-2.tcore1.AEQ-Ashburn.as6453.net [66.198.154
.177]
  9    43 ms    41 ms    39 ms  66.198.154.66
 10    44 ms    47 ms    45 ms  unknown.prolexic.com [209.200.144.32]
 11    43 ms    46 ms    42 ms  unknown.prolexic.com [209.200.144.35]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

0 Likes
Re: Unable to access www.wellsfargo.com
Hubrisnxs
Legend

I'm glad you ran that TNS

looks like that is the default behavior for WF; which isn't surprising.  As you mentioned it's common to drop icmp pings to prevent DOS attacks.  \

I get the same time outs from Level3's and Cogent's Looking glass servers.

http://lookingglass.level3.net/

Traceroute results from Buffalo, NY to 159.45.66.101(www.wellsfargo.com)

 1  * ae-2-70.edge3.Washington4.Level3.net (4.69.149.82)  14.056 ms *
 2  * * *
 3  4.53.116.126 (4.53.116.126)  15.110 ms  15.236 ms  15.270 ms
 4  unknown.prolexic.com (209.200.144.32)  14.769 ms  14.859 ms  15.129 ms
 5  unknown.prolexic.com (209.200.144.35)  14.988 ms 
    unknown.prolexic.com (209.200.144.164)  15.348 ms unknown.prolexic.com (209.200.144.35)  14.771 ms
 6  * unknown.prolexic.com (209.200.144.35)  15.347 ms !filtered unknown.prolexic.com (209.200.144.164)  16.033 ms !filtered


Traceroute complete

http://www.cogentco.com/en/network/looking-glass

traceroute to www.wellsfargo.com (159.45.66.101), 30 hops max, 60 byte packets
1  vl5.mag01.jfk02.atlas.cogentco.com (66.28.3.113)  0.460 ms  0.463 ms
2  te0-17-0-5.ccr41.jfk02.atlas.cogentco.com (154.54.5.226)  0.548 ms  0.569 ms
3  be2061.ccr21.jfk05.atlas.cogentco.com (154.54.3.70)  1.225 ms be2060.ccr21.jfk05.atlas.cogentco.com (154.54.31.10)  1.215 ms
4  tata.jfk05.atlas.cogentco.com (154.54.12.18)  0.523 ms  0.523 ms
5  if-14-14.tcore2.NJY-Newark.as6453.net (66.198.111.125)  7.869 ms  7.678 ms
6  if-3-2.tcore2.AEQ-Ashburn.as6453.net (216.6.87.9)  7.677 ms  7.698 ms
7  if-2-2.tcore1.AEQ-Ashburn.as6453.net (216.6.87.2)  7.231 ms  7.201 ms
8  66.198.154.186 (66.198.154.186)  7.872 ms  8.152 ms
9  unknown.prolexic.com (209.200.144.32)  7.745 ms unknown.prolexic.com (209.200.144.35)  8.075 ms
10  unknown.prolexic.com (209.200.144.164)  7.814 ms !X *
 

0 Likes