Solved

Tracert - Request timed out - how to read results?

Posted on 2011-03-17
25
1,602 Views
Last Modified: 2013-12-25
Some users notified me that some websites stopped working in IE.

I used the tracert command to see the outcome. As an example below for nasdaq.com the time out comes always on the same routers.

How should I read this result?
It seems like the site is blocked to us. I checked from outside of our network and nasdaq works just fine.

Thank you.





C:\Windows\system32>tracert 206.200.251.71

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.130.61.2
  2     1 ms     2 ms    <1 ms  host145.fibersonic.com [216.16.226.145]
  3    <1 ms    <1 ms    <1 ms  216.16.255.225
  4     2 ms     2 ms     2 ms  38.104.251.181
  5     2 ms     2 ms     2 ms  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54
.40.137]
  6    14 ms    14 ms    14 ms  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54
.27.237]
  7    21 ms    21 ms    21 ms  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.
4.126]
  8    22 ms    22 ms    21 ms  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54
.41.114]
  9    23 ms    23 ms    23 ms  verizon.iad01.atlas.cogentco.com [154.54.10.226]

 10    23 ms    23 ms    22 ms  0.ae1.xl3.iad8.alter.net [152.63.33.118]
 11    22 ms    21 ms    22 ms  0.ge-5-3-0.xt1.nyc9.alter.net [152.63.1.106]
 12    22 ms    23 ms    23 ms  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13    23 ms    23 ms    24 ms  63.87.224.23
 14    24 ms    23 ms    24 ms  63.87.242.37
 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
Comment
Question by:Mezczyzna
  • 18
  • 4
  • 3
25 Comments
 
LVL 9

Accepted Solution

by:
TBK-Consulting earned 250 total points
ID: 35159319
Sometimes routers will drop tracert and/or ping packets on purpose so as to not be burdened with the extra traffic ... I've seen tracert results where a few in the middle show request timed out and then the last few pickup again and give valid results ...
0
 

Author Comment

by:Mezczyzna
ID: 35159592
OK.
Where should I look for the reason a website is not displayed.
I checked Chrome. Same story on every computer within our network.

Oops! Internet Explorer could not connect to www.nasdaq.com
Oops! Google Chrome could not connect to www.nasdaq.com
0
 
LVL 9

Expert Comment

by:TBK-Consulting
ID: 35159644
try using pathping as well to see what it's results are and if the stops come in the same place or differently and yes it could be the site is blocked to you, the question tho is by whom, by looking at the tracert so far it is quite a few hops out there so it would not be the ISP blocking it but something further down.
0
 

Author Comment

by:Mezczyzna
ID: 35159776
I still don't understand the result.
It seems going to Verizon and that's it.



C:\Windows\system32>pathping www.nasdaq.com

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:
  0  ST443.company.com [10.130.61.169]
  1  10.130.61.2
  2  host145.fibersonic.com [216.16.226.145]
  3  216.16.255.225
  4  38.104.251.181
  5  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
  6  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
  7  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
  8  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
  9  verizon.iad01.atlas.cogentco.com [154.54.10.226]
 10     *        *        *
Computing statistics for 225 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ST443.company.com [10.130.61.169]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.130.61.2
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  host145.fibersonic.com [216.16.226.145]
                                0/ 100 =  0%   |
  3    0ms     0/ 100 =  0%     0/ 100 =  0%  216.16.255.225
                                0/ 100 =  0%   |
  4   15ms     0/ 100 =  0%     0/ 100 =  0%  38.104.251.181
                                0/ 100 =  0%   |
  5    2ms     0/ 100 =  0%     0/ 100 =  0%  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
                                0/ 100 =  0%   |
  6   14ms     0/ 100 =  0%     0/ 100 =  0%  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
                                0/ 100 =  0%   |
  7   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
                                0/ 100 =  0%   |
  8   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
                                0/ 100 =  0%   |
  9   23ms     0/ 100 =  0%     0/ 100 =  0%  verizon.iad01.atlas.cogentco.com [154.54.10.226]

Trace complete.
0
 
LVL 9

Expert Comment

by:TBK-Consulting
ID: 35159846
Yes it appears as if Verizon is stopping the website for whatever reasons - who knows - are they your ISP??? if yes , send them copies of the tracert and the pathping and ask them why they are blocking, it could be something temporary like a major router down and that's the only route to that specific website thru their network???
0
 

Author Comment

by:Mezczyzna
ID: 35159981
No. Their not.
Fibersonic is.

0
 
LVL 9

Expert Comment

by:TBK-Consulting
ID: 35160008
maybe fibersonic is leasing lines from Verizon?  It is worth giving them a call and seeing if they know if anything is down above them which would be causing this problem ...
0
 

Author Comment

by:Mezczyzna
ID: 35160023
I already talked to them. They said nothing was blocked.
I am in Canada.
Fibersonic became part of Rogers Communications this month.
0
 

Author Comment

by:Mezczyzna
ID: 35160080
I am completely not understanding it.

When I check on dnsstuff.com this 154.54.10.226 comes to African Network Information Center.



#
# Query terms are ambiguous.  The query is assumed to be:
#     "n 154.54.10.226"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=154.54.10.226?showDetails=true&showARIN=false
#

PSINet, Inc. PSINET-B2-54 (NET-154-54-0-0-1) 154.54.0.0 - 154.54.255.255
African Network Information Center NET154 (NET-154-0-0-0-0) 154.0.0.0 - 154.255.255.255


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#






When I check verizon.iad01.atlas.cogentco.com, it comes to this:


WHOIS - 75.125.82.251
Location: United States [City: Dallas, Texas]

No domain or IP specified. Doing IPWHOIS lookup on your IP of 75.125.82.251.
Looking up 75.125.82.251 at verizon.iad01.atlas.cogentco.com.



Sorry, I could not resolve verizon.iad01.atlas.cogentco.com.
 

[If E-mail address(es) were hidden on this page, you can click here to get the results with the E-mail address].
0
 

Expert Comment

by:realdreams
ID: 35254041
There are a something I don't understand in this case, I'll just list what I think.

1.traceroute results don't necessarily indicates a problem. It's a common practice to drop ICMP TTL Expired packet for security or whatever reason(make it harder to figure out the network structure)

Your traceroute shows fibersonic-->Atria Networks LP.(216.16.255.225)-->Cogent (from 38.104.251.181 to 154.54.10.226)-->MCI Communications Services, Inc. d/b/a Verizon Business(from 152.63.33.118 to 63.111.126.50), then the hop(receiving an ICMP ECHO TTL=0) dropped ICMP TTL Expired(no packet coming back causing Request Timed Out).

See attached my tracert 206.200.251.71
my ISP-->Level 3-->MCI Communications Services, Inc. d/b/a Verizon Business(from 152.63.33.118)
the slight difference on pos7-0.ur1.ewr2.web.wcom.net(yours is pos6-0.ur1.ewr2.web.wcom.net), I don't exactly know how that works but probably just choose a different hop for packets from different source

What I dont understand is your pathping www.nasdaq.com. Pathping and tracert and essentially the same thing, why your pathping stopped at 154.54.10.226?

Can you run pathping 206.200.251.71,pathping www.nasdaq.com,tracert www.nasdaq.com and tracert 206.200.251.71 again? They should be the same, or there might be a problem(maybe timeout settings? I haven't checked the default time out for tracert and pathing, you can try add some parameters to see if they make a difference)

(I find some hops may not reply to ICMP ECHO(regular ping), but they do reply ICMP TTL Expired so you can see it in traceroute )

Also can you run ping 63.87.242.37 -t for a while and post the results?
From what I see
ping 63.87.242.37 -t (Windows)
Pinging 63.87.242.37 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.

PING 63.87.242.37 (63.87.242.37) 56(84) bytes of data.(Linux)
From 63.87.242.37 icmp_seq=1 Packet filtered
From 63.87.242.37 icmp_seq=5 Packet filtered
From 63.87.242.37 icmp_seq=6 Packet filtered
From 63.87.242.37 icmp_seq=9 Packet filtered
From 63.87.242.37 icmp_seq=11 Packet filtered

I used wireshark to capture packets from 63.87.242.37, and found
1. replies from 63.87.242.37 are ICMP Type 8(Echo(ping)) Code 13 (Communication Administratively Prohibited  [RFC1812])
So there is a firewall on 63.87.242.37 that denies echo which explains no further path info are shown.
2.63.87.242.37 doesn't reply every echo, smart firewall policy to avoid flooding attack or the hop does have problem(losing packets)


154.54.10.226(epoch.sjc03.atlas.cogentco.com) is an ip address from ARIN. From the dns name it's owned by Cogent Communications, a US network backbone company. They probably just bought some IPs from ARIN for whatever reason.
154.54.10.226      United States      District Of Columbia      Washington      Cogent Communications
Whois doesn't necessarily say the geological location.

Nasdaq.com(probably entire 206.200.250.0/23) doesn't reply ping.

From the dns name verizon.iad01.atlas.cogentco.com(154.54.10.226), it's a route from Cogent Communication to Verizon, owned by  Cogent
The reason you can only reverse resolute 154.54.10.226 is there is a ptr record for 154.54.10.226, but   dns query for verizon.iad01.atlas.cogentco.com gets a no such name reply code 3. I don't know a lot about DNS. maybe security policy...


I don't know how 75.125.82.251(dnsstuff.com web server) is related to this problem...

And BGP and AS
Destination is
206.200.251.71
United States
206.200.250.0/23
AS14495
NASDAQTRM The Nasdaq Stock Market


The last traceable hop is
63.87.242.37
United States
(none)      63.87.224.0/19
AS11486
WAN Worldcom Advance Networks

AS14495 is connected to AS11486 WAN Worldcom Advance Networks(some information:http://www.robtex.com/as/as14495.html#peer), unfortunately I know little about AS and BGP
You might be able to figure out how the packet reaches the destination after 63.87.242.37 with some analysis on BGP/AS.

From another aspect:
1. what other websites don't work( the route goes through AS11486 as well?)
2. try other browsers? chrome/ opera?
3. try other os
4. how are the users experiencing this problem distributed(same subnet)?
5. so you mean some users can still access nasdaq.com, how's the tests(traceroute) at those users like?
6. i think it's likely to be local access restriction. since Nasdaq doesn't allow ping, it makes troubleshooting harder but capturing packets still helps a lot(ping results can be misleading like I posted ping results above, but packets tell you the true story)
7. try to contact nasdaq? the problem may be on their side, not necessarily blocking but misconfiguration(CDN etc.) can definitely cause this problem

Good luck and thanks for the case I reviewed so much network knowledge :)
tracert 206.200.251.71
.....................
 9    21 ms    21 ms    21 ms  xe-11-0-0.edge3.Washington1.Level3.net [4.59.144.69]
10    87 ms    35 ms    21 ms  ae-2-70.edge1.Washington4.Level3.net [4.69.149.79]
11    20 ms    21 ms    23 ms  mci-level3.washingtondc4.level3.net [4.68.62.134]
12    21 ms    21 ms    21 ms  0.ae1.XL3.IAD8.ALTER.NET [152.63.33.118]
13    27 ms    27 ms    27 ms  0.ge-5-3-0.XT1.NYC9.ALTER.NET [152.63.1.106]
14    28 ms    28 ms    29 ms  pos7-0.ur1.ewr2.web.wcom.net [63.111.126.54]
15    28 ms    30 ms    28 ms  63.87.224.23
16    32 ms    27 ms    30 ms  63.87.242.37
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.

Open in new window

0
 

Author Comment

by:Mezczyzna
ID: 35257271
Thank you RealDreams.

I won't be able to do it today, but I will get back to it.
I am the only guy here with a few servers and well over a hundred users.
Have to do something different now.

Thank you.
0
 

Author Comment

by:Mezczyzna
ID: 35257514
Anyway. The guy is late, so I run it:

1:
C:\>pathping 206.200.251.71

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:
  0  ST443.company.com [10.130.61.169]
  1  10.130.61.2
  2  host145.fibersonic.com [216.16.226.145]
  3  216.16.255.225
  4  38.104.251.181
  5  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
  6  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
  7  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
  8  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
  9  verizon.iad01.atlas.cogentco.com [154.54.10.226]
 10  0.ae1.XL3.IAD8.ALTER.NET [152.63.33.118]
 11  0.ge-5-3-0.XT1.NYC9.ALTER.NET [152.63.1.106]
 12  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13  63.87.224.23
 14  63.87.242.37
 15     *        *        *
Computing statistics for 350 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ST443.company.com [10.130.61.169]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.130.61.2
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  host145.fibersonic.com [216.16.226.145]
                                0/ 100 =  0%   |
  3    0ms     0/ 100 =  0%     0/ 100 =  0%  216.16.255.225
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  38.104.251.181
                                0/ 100 =  0%   |
  5    2ms     1/ 100 =  1%     1/ 100 =  1%  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
                                0/ 100 =  0%   |
  6   14ms     0/ 100 =  0%     0/ 100 =  0%  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
                                0/ 100 =  0%   |
  7   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
                                0/ 100 =  0%   |
  8   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
                                0/ 100 =  0%   |
  9   25ms     1/ 100 =  1%     1/ 100 =  1%  verizon.iad01.atlas.cogentco.com [154.54.10.226]
                                0/ 100 =  0%   |
 10   40ms     1/ 100 =  1%     1/ 100 =  1%  0.ae1.xl3.iad8.alter.net [152.63.33.118]
                                0/ 100 =  0%   |
 11   31ms     0/ 100 =  0%     0/ 100 =  0%  0.ge-5-3-0.xt1.nyc9.alter.net [152.63.1.106]
                                0/ 100 =  0%   |
 12   31ms     1/ 100 =  1%     1/ 100 =  1%  pos6-0.ur1.ewr2.web.wcom.net [63.1
11.126.50]
                                0/ 100 =  0%   |
 13   23ms     0/ 100 =  0%     0/ 100 =  0%  63.87.224.23
                               70/ 100 = 70%   |
 14   24ms    70/ 100 = 70%     0/ 100 =  0%  63.87.242.37

Trace complete.
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:Mezczyzna
ID: 35257526
2:

C:\>pathping www.nasdaq.com

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:
  0  ST443.company.com [10.130.61.169]
  1  10.130.61.2
  2  host145.fibersonic.com [216.16.226.145]
  3  216.16.255.225
  4  38.104.251.181
  5  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
  6  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
  7  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
  8  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
  9  verizon.iad01.atlas.cogentco.com [154.54.10.226]
 10  0.ae1.XL3.IAD8.ALTER.NET [152.63.33.118]
 11  0.ge-5-3-0.XT1.NYC9.ALTER.NET [152.63.1.106]
 12  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13  63.87.224.23
 14  63.87.242.37
 15     *        *        *
Computing statistics for 350 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ST443.company.com [10.130.61.169]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.130.61.2
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  host145.fibersonic.com [216.16.226.145]
                                0/ 100 =  0%   |
  3    0ms     0/ 100 =  0%     0/ 100 =  0%  216.16.255.225
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  38.104.251.181
                                0/ 100 =  0%   |
  5    2ms     0/ 100 =  0%     0/ 100 =  0%  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
                                0/ 100 =  0%   |
  6   14ms     0/ 100 =  0%     0/ 100 =  0%  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
                                0/ 100 =  0%   |
  7   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
                                0/ 100 =  0%   |
  8   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
                                0/ 100 =  0%   |
  9   23ms     0/ 100 =  0%     0/ 100 =  0%  verizon.iad01.atlas.cogentco.com [154.54.10.226]
                                0/ 100 =  0%   |
 10   38ms     0/ 100 =  0%     0/ 100 =  0%  0.ae1.xl3.iad8.alter.net [152.63.33.118]
                                0/ 100 =  0%   |
 11   30ms     0/ 100 =  0%     0/ 100 =  0%  0.ge-5-3-0.xt1.nyc9.alter.net [152.63.1.106]
                                0/ 100 =  0%   |
 12   32ms     0/ 100 =  0%     0/ 100 =  0%  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
                                0/ 100 =  0%   |
 13   23ms     0/ 100 =  0%     0/ 100 =  0%  63.87.224.23
                               64/ 100 = 64%   |
 14   24ms    64/ 100 = 64%     0/ 100 =  0%  63.87.242.37

Trace complete.

C:\>
0
 

Author Comment

by:Mezczyzna
ID: 35257729
3:

C:\>tracert 206.200.251.71

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.130.61.2
  2     1 ms    <1 ms    <1 ms  host145.fibersonic.com [216.16.226.145]
  3    <1 ms    <1 ms    <1 ms  216.16.255.225
  4     2 ms     *        2 ms  38.104.251.181
  5     2 ms     2 ms     2 ms  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
  6    14 ms    14 ms    14 ms  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
  7    21 ms    20 ms    21 ms  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
  8    22 ms    21 ms    21 ms  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
  9    23 ms    23 ms    23 ms  verizon.iad01.atlas.cogentco.com [154.54.10.226]
 10    22 ms    22 ms    22 ms  0.ae1.xl3.iad8.alter.net [152.63.33.118]
 11    28 ms    22 ms    24 ms  0.ge-6-3-0.XT1.NYC9.ALTER.NET [152.63.3.129]
 12    23 ms    23 ms    22 ms  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13    23 ms    23 ms    25 ms  63.87.224.23
 14    23 ms    24 ms    23 ms  63.87.242.37
 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.

C:\>
0
 

Author Comment

by:Mezczyzna
ID: 35257750
4:

C:\>tracert www.nasdaq.com

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.130.61.2
  2    <1 ms    <1 ms    <1 ms  host145.fibersonic.com [216.16.226.145]
  3    <1 ms    <1 ms    <1 ms  216.16.255.225
  4     2 ms     2 ms     2 ms  38.104.251.181
  5     2 ms     2 ms     2 ms  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
  6    14 ms    14 ms    14 ms  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
  7    21 ms    21 ms    21 ms  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
  8    22 ms    22 ms    21 ms  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
  9    23 ms    22 ms    22 ms  verizon.iad01.atlas.cogentco.com [154.54.10.226]
 10    22 ms    22 ms    22 ms  0.ae1.xl3.iad8.alter.net [152.63.33.118]
 11    49 ms    23 ms    24 ms  0.ge-6-3-0.XT1.NYC9.ALTER.NET [152.63.3.129]
 12    23 ms    22 ms    22 ms  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13    25 ms    24 ms    23 ms  63.87.224.23
 14    25 ms    23 ms    24 ms  63.87.242.37
 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.

C:\>
0
 

Author Comment

by:Mezczyzna
ID: 35257761
5:

C:\>ping 63.87.242.37 -t

Pinging 63.87.242.37 with 32 bytes of data:
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.
Request timed out.
Reply from 63.87.242.37: Destination net unreachable.

Ping statistics for 63.87.242.37:
    Packets: Sent = 228, Received = 73, Lost = 155 (67% loss),
Control-C
^C
C:\>
0
 

Assisted Solution

by:realdreams
realdreams earned 250 total points
ID: 35257904
Thanks for the test. These 4 tests are exactly as expected(last hop 63.87.242.37: and packet filtered as I said above). The route seems ok, at least from your side to 63.87.242.37.It might be easier to think about those questions at the end of my last reply. :)
0
 

Author Comment

by:Mezczyzna
ID: 35258075
Other browsers have the same problem, (Chrome, Safari). Other system, Mac - same.

So far it is the only webpage that is blocked.

0
 

Author Comment

by:Mezczyzna
ID: 35258082
It is only from our network.
I'll grab a laptop, go outside and it works fine.
0
 

Author Comment

by:Mezczyzna
ID: 35258101
I've sent e-mail to Nasdaq's support (from the web contact us) about a month ago.
No reply.
0
 

Expert Comment

by:realdreams
ID: 35258172
Can you open any of these websites on page http://www.robtex.com/cnet/206.200.251.html , like www.manpower.com ?
0
 

Author Comment

by:Mezczyzna
ID: 35476275
Yes. I can open those sites.
Nasdaq started working.
Suddenly as it suddenly stopped.
0
 

Author Comment

by:Mezczyzna
ID: 35476501
These are the results now:

C:\>ping www.nasdaq.com

Pinging www.nasdaq.com [206.200.251.71] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 206.200.251.71:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>tracert www.nasdaq.com

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.130.61.2
  2     1 ms    <1 ms    <1 ms  host145.fibersonic.com [216.16.226.145]
  3     9 ms    <1 ms    <1 ms  216.16.255.225
  4     *        2 ms     2 ms  38.104.251.181
  5     2 ms     2 ms     2 ms  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54
.40.137]
  6    14 ms    14 ms    14 ms  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54
.27.237]
  7    22 ms    21 ms    21 ms  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.
4.126]
  8    22 ms    22 ms    21 ms  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54
.41.114]
  9    23 ms    23 ms    23 ms  verizon.iad01.atlas.cogentco.com [154.54.10.226]

 10    23 ms    23 ms    23 ms  0.ae1.XL3.IAD8.ALTER.NET [152.63.33.118]
 11    21 ms    23 ms    22 ms  0.ge-5-3-0.XT1.NYC9.ALTER.NET [152.63.1.106]
 12    22 ms    22 ms    22 ms  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13    23 ms    23 ms    24 ms  63.87.224.23
 14    24 ms    24 ms    24 ms  63.87.242.37
 15    23 ms    24 ms    23 ms  206.200.252.142
 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.

C:\>





C:\>pathping www.nasdaq.com

Tracing route to www.nasdaq.com [206.200.251.71]
over a maximum of 30 hops:
  0  ST443.company.com [10.130.61.169]
  1  10.130.61.2
  2  host145.fibersonic.com [216.16.226.145]
  3  216.16.255.225
  4  38.104.251.181
  5  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]
  6  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]
  7  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]
  8  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]
  9  verizon.iad01.atlas.cogentco.com [154.54.10.226]
 10  0.ae1.xl3.iad8.alter.net [152.63.33.118]
 11  0.ge-5-3-0.xt1.nyc9.alter.net [152.63.1.106]
 12  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]
 13  63.87.224.23
 14  63.87.242.37
 15  206.200.252.142
 16     *        *        *
Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ST443.company.com [10.130.61.169] 0/ 100 =  0%   |
 1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.130.61.2 0/ 100 =  0%   |
 2    1ms     0/ 100 =  0%     0/ 100 =  0%  host145.fibersonic.com [216.16.226.145]  0/ 100 =  0%   |
 3    0ms     0/ 100 =  0%     0/ 100 =  0%  216.16.255.225  0/ 100 =  0%   |
 4    6ms     0/ 100 =  0%     0/ 100 =  0%  38.104.251.181  0/ 100 =  0%   |
 5    2ms     0/ 100 =  0%     0/ 100 =  0%  te0-3-0-0.ccr21.yyz02.atlas.cogentco.com [154.54.40.137]  0/ 100 =  0%   |
 6   14ms     0/ 100 =  0%     0/ 100 =  0%  te0-5-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.27.237]  0/ 100 =  0%   |
 7   21ms     0/ 100 =  0%     0/ 100 =  0%  te0-1-0-3.ccr21.dca01.atlas.cogentco.com [66.28.4.126]  0/ 100 =  0%   |
 8   22ms     0/ 100 =  0%     0/ 100 =  0%  te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54.41.114]  0/ 100 =  0%   |
 9   27ms     0/ 100 =  0%     0/ 100 =  0%  verizon.iad01.atlas.cogentco.com [154.54.10.226]  0/ 100 =  0%   |
10   39ms     0/ 100 =  0%     0/ 100 =  0%  0.ae1.xl3.iad8.alter.net [152.63.33.118]  0/ 100 =  0%   |
11   34ms     0/ 100 =  0%     0/ 100 =  0%  0.ge-5-3-0.xt1.nyc9.alter.net [152.63.1.106]  0/ 100 =  0%   |
12   31ms     0/ 100 =  0%     0/ 100 =  0%  pos6-0.ur1.ewr2.web.wcom.net [63.111.126.50]  0/ 100 =  0%   |
 13   23ms     0/ 100 =  0%     0/ 100 =  0%  63.87.224.23  0/ 100 =  0%   |
 14   24ms    64/ 100 = 64%    64/ 100 = 64%  63.87.242.37  0/ 100 =  0%   |
 15   22ms     0/ 100 =  0%     0/ 100 =  0%  206.200.252.142

Trace complete.
0
 

Author Comment

by:Mezczyzna
ID: 35476513
Seems it was stopped / blocked at 63.87.242.37.
0
 

Author Closing Comment

by:Mezczyzna
ID: 35476518
Thank you.
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

Suggested Solutions

Read about why website design really matters in today's demanding market.
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
The viewer will learn how to dynamically set the form action using jQuery.
The viewer will learn how to count occurrences of each item in an array.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now