Cannot access www.tomtom.com with my new FiOS service!

[Mekkon]

I upgraded to FiOS a couple weeks ago, and today tried to update my GPS, and it said that www.tomtom.com could not be reached.  I figured the site was temporarily down, and then tried later, and the same.  So I tried it on my iPhone (on 3G) and it worked fine.  I then tested it remotely, and it worked fine.  A brief googleing points to FiOS as the problem, however most of those posts are pretty old.

Right now I cannot access www.tomtom.com (or anything on the tomtom domain at all) it just times out.  I also cannot use the TomTom Home application, as it dies when trying to connect to tomtom.  Surely there must be a solution - I can't imagine that TomTom blocks access from ALL FiOs users!

Can anyone help?!?!

Thanks,

-tom

[Mekkon]

By the way, if I use a proxy, such as the one below, I can access www.tomtom.com just fine!   So the problem must be IP-related, no?

https://www.megaproxy.com/freesurf/

[Justin46]

---

@Mekkon wrote:

By the way, if I use a proxy, such as the one below, I can access www.tomtom.com just fine!   So the problem must be IP-related, no?

https://www.megaproxy.com/freesurf/

---

Probably. I can get to tomtom.com from my FiOS connection.

What are the first two octets of your own IP address (not the IP address from your router, which would probably be 192.168.x.x, but your WAN address)? You can easily find your IP address by logging into the router if you do not have any other tool to obtain it. It is very common for websites or routers to block traffic from specific IP address ranges due to reported phising attacks or other malicious activity from that block. Verizon (and other ISPs) acquire IP address blocks as needed, sometimes they have previously been used for bad things and the blocking filters used by many sites don't get updated quickly enough. Eventually the problem will probably go away by itself, but it may take a while.....

Probably the easiest solution is to turn off your router overnight. When you power it back on you almost certainly will get a different IP address assigned, hopefully on another IP address block, and the problem will go away. It might even take several tries to get an address that will work. Another option is to try to contact the tomtom folks and tell them about the problem, you might be able to get them to update their filter.

Good luck.

__________________________________
Justin
Verizon FiOS TV, Internet, and phone
QIP7232, IMG 1.8, Build 02.54
Keller, TX 76248

[smith6612]

http://www.tomtom.com/ is down on my end here. Site is online as I can reach it when I VPN into my web server. I use Verizon DSL, but here's a trace route. Seems to be a routing issue leaving the Verizon Network (alter.net). Looks to be a bad route (See second trace edited in)

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>tracert www.tomtom.com

Tracing route to www.tomtom.com [85.90.77.41]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.3.1]
  2    44 ms    48 ms    80 ms  10.15.3.1
  3    64 ms   124 ms   105 ms  so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.81.13.77]
  4   114 ms    91 ms    63 ms  as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.106]
  5    86 ms    64 ms    67 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6   167 ms   170 ms   286 ms  204.255.168.194
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10  ^C
C:\Users\>

EDIT: ~5 minutes later, a portion of their site starts to load up. Can't see anything yet. By this time most devices and browsers would have timed out. My browser's still going at it lol.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Sean Smith>tracert www.tomtom.com

Tracing route to www.tomtom.com [85.90.77.41]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.3.1]
  2    44 ms    48 ms    80 ms  10.15.3.1
  3    64 ms   124 ms   105 ms  so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.8
1.13.77]
  4   114 ms    91 ms    63 ms  as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.
106]
  5    86 ms    64 ms    67 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6   167 ms   170 ms   286 ms  204.255.168.194
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10  ^C
C:\Users\Sean Smith>tracert www.tomtom.com

Tracing route to www.tomtom.com [85.90.77.41]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.3.1]
  2    20 ms     9 ms    23 ms  10.15.3.1
  3     *       94 ms    56 ms  so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.81.13.77]
  4    92 ms    91 ms    92 ms  as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.106]
  5    57 ms   111 ms    94 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6    85 ms    94 ms    73 ms  204.255.168.194
  7     *        *        *     Request timed out.
  8     *        *      180 ms  vl1403.sara-r9-alm.com.sara.nl [85.90.64.5]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *

[Justin46]

When I started to post my first response, I did not get any response from tomtom. But a try a few minutes later came right up. So maybe there are some routing issues or whatever involved.

Here is a tracert I just did:

C:\Windows\system32>tracert www.tomtom.com

Tracing route to www.tomtom.com [85.90.77.41]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2     5 ms     4 ms     4 ms  10.33.34.55
 3     5 ms     4 ms     4 ms  G4-2-758.DLLSTX-LCR-07.verizon-gni.net [130.81.107.36]
 4     8 ms     8 ms     7 ms  so-6-2-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.28.208]
 5     6 ms     6 ms     7 ms  0.xe-8-1-0.BR1.DFW13.ALTER.NET [152.63.2.145]
 6     6 ms     6 ms     7 ms  te1-4-10G.ar5.DAL2.gblx.net [64.208.27.2]
 7   134 ms   134 ms   134 ms  206.41.25.158
 8   133 ms   131 ms   131 ms  vl1403.sara-r9-alm.com.sara.nl [85.90.64.5]
 9   135 ms   141 ms   131 ms  es01salm.tomtom.sara.nl [85.90.85.102]
10     *        *        *     Request timed out.
11   132 ms   131 ms   131 ms  www.tomtom.com [85.90.77.41]

Trace complete.

At least right now no issue getting to the site from my FiOS connection.

__________________________________
Justin
Verizon FiOS TV, Internet, and phone
QIP7232, IMG 1.8, Build 02.54
Keller, TX 76248