[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 320
  • Last Modified:

I can not get to a specific site from one of my machines

I can not get to voxeo.com from my ip (from other machines it works fine, and on this one it is first time ever that this happens). Here is the traceroute output, but I do not understand why this could be happening. Any advice? Thanks.

 1  192.168.1.1 (192.168.1.1)  3.010 ms  4.463 ms  6.543 ms
 2  73.214.112.1 (73.214.112.1)  21.075 ms  24.610 ms  25.937 ms
 3  68.85.249.5 (68.85.249.5)  26.397 ms  28.984 ms  29.444 ms
 4  68.85.244.33 (68.85.244.33)  29.907 ms  32.548 ms  37.382 ms
 5  68.85.244.73 (68.85.244.73)  39.295 ms  39.755 ms  40.217 ms
 6  te-3-1.car2.Houston1.Level3.net (4.79.90.93)  38.733 ms  13.670 ms  20.374 ms
 7  ae-5-5.ebr1.Atlanta2.Level3.net (4.69.132.238)  54.215 ms  57.657 ms  72.348 ms
 8  ae-11-53.car1.Atlanta1.Level3.net (4.68.103.66)  62.546 ms ae-11-51.car1.Atlanta1.Level3.net (4.68.103.2)  62.050 ms ae-11-55.car1.Atlanta1.Level3.net (4.68.103.130)  65.999 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
0
kerzner
Asked:
kerzner
  • 2
2 Solutions
 
r-kCommented:
I am guessing a temporary glitch at 4.68.103.130 (ae-11-55.car1.Atlanta1.Level3.net )

Is it always getting stuck at that last line? Has it cleared up now?
0
 
r-kCommented:
I should have asked if you're getting the correct DNS resolution for www.voxeo.com.

For comparison, I get 66.193.54.50
0
 
Adrien de CroyCommented:
It's pretty common unfortunately that intermittent network routing problems can make parts of the internet inaccessible.

The way routing works is that each hop of the path between your machine and the other machine you're trying to contact needs to know how to reach the destination, and likewise on the path back.  Sometimes the path back from the other end is different from the path out from your end.  This is because the routers on the path forward packets based on their route table which usually only considers the destination address.

So if there is a problem with a router, or configuration of a route table, then certain paths can stop working.  Sometimes you'll find many machines affected, other times just the one you want.  If the problem persists, I'd contact your ISP, since they may be able to raise the issue with an upstream provider.
0
 
kerznerAuthor Commented:
Thank you for the great explanation. Voxeo resolved it.
0

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now