<div>
Can you ping your company? 
 
Tracert shows only 30 hops. Tracert pings every hop. When a hop has ICMP blocked, then you'll get a request timeout. So this may not indicate any failure at all.
</div>

<div>
No, when I try and ping i get &quot;Request timed out&quot; 
 
Regarding ICMP blocked/ &nbsp;Would an ATT.net hop everte5any do this?
</div>

<div>
BThomehub..home means you're in UK? Where's your company located? Cause it looks like your packages are routed to/over New York/US.
</div>

<div>
Yes, I'm in the UK but the company is located in Florida.
</div>

<div>
I should have mentioned I use this connection daily and it was working fine until 11:30 GMT when my connection was severed.
</div>

<div>
Then you should phone or e-mail with an administrator of your company. When there is a problem, then tracert tells you, that it is somewhere after NY.
</div>

<div>
Yes, that's been done and everything is fine locally. &nbsp;In fact, Florida users are able to connect to the vpn without issue. 
 
So I am assuming the issue is with the Florida hop but I am uncertain how to confirm/disprove this.
</div>

<div>
Trace route timeouts can be considered normal. &nbsp;A lot of devices are configured to ignore the type of packets that are used by trace route. 
 
Can you ping the IP address of your VPN server in Fla? If not, should you be able to? &nbsp;You would need to ask your IT support in Fla. if you should be able to. &nbsp;You can also ask them if there are any IP address in the Fla. location that you should be able to ping.
</div>

<div>
Use the great tool PathAnalyzer, &nbsp;there is free LFT tool which can trace and bypass firewalls that blocks ICMP. this method called LFT Layer Four Traceroute.
</div>

<div>
First off, thanks for all the help guys. 
 
The link came back up mid-day and i was able to connect. &nbsp;While I'm up I'd like to come away from this question with a method of more quickly and independently identifying it an AT&amp;T outage. 
 
giltjr - Turns out I can not ping my VPN even when it's up and that this is normal. 
nader alkahtani - Next time this occurs I will give the tool a try 
 
Here's what the TraceRT reports looks like now that we're able to connect. &nbsp;It shows it getting 
past all the att.net servers. &nbsp;So in the event of a future failure, if I were to see it failing at an att.net server would I be correct in assuming it is an AT&amp;T Fault? &nbsp;And is there an online resource to look for faults using the ip address of one of their hops? 

<pre><code class="code-10 nolinks" id="code-8290101">Tracing route to vpn.***.com [***]
over a maximum of 30 hops:

 1 1 ms 1 ms &lt;1 ms BThomehub.home [192.168.1.254] 
 2 * * * Request timed out.
 3 * * * Request timed out.
 4 6 ms 6 ms 6 ms 217.41.217.125 
 5 12 ms 12 ms 11 ms 212.140.235.218 
 6 11 ms 11 ms 12 ms 217.41.169.9 
 7 11 ms 11 ms 11 ms 217.41.169.107 
 8 10 ms 10 ms 10 ms acc1-10GigE-3-3-0.sf.21cn-&lt;wbr &gt;&lt;/wbr&gt;ipp.bt.net&lt;wbr &gt;&lt;/wbr&gt; [109.159.251.91] 
 9 20 ms 19 ms 19 ms core2-te0-13-0-2.ilford.uk&lt;wbr &gt;&lt;/wbr&gt;core.bt.ne&lt;wbr &gt;&lt;/wbr&gt;t [109.159.251.11] 
 10 21 ms 20 ms 20 ms 109.159.254.197 
 11 17 ms 17 ms 17 ms 166-49-211-250.eu.bt.net [166.49.211.250] 
 12 18 ms 18 ms 18 ms 82.112.101.73 
 13 17 ms 17 ms 17 ms ae-7.r23.londen03.uk.bb.gi&lt;wbr &gt;&lt;/wbr&gt;n.ntt.net [129.250.6.54] 
 14 20 ms 27 ms 20 ms ae-0.r22.londen03.uk.bb.gi&lt;wbr &gt;&lt;/wbr&gt;n.ntt.net [129.250.4.85] 
 15 85 ms 85 ms 85 ms ae-5.r24.nycmny01.us.bb.gi&lt;wbr &gt;&lt;/wbr&gt;n.ntt.net [129.250.2.18] 
 16 86 ms 87 ms 87 ms ae-13.r05.nycmny01.us.bb.g&lt;wbr &gt;&lt;/wbr&gt;in.ntt.net&lt;wbr &gt;&lt;/wbr&gt; [129.250.4.71] 
 17 88 ms 87 ms 87 ms ae-0.att.nycmny01.us.bb.gi&lt;wbr &gt;&lt;/wbr&gt;n.ntt.net [129.250.9.206] 
 18 130 ms 127 ms 127 ms cr2.n54ny.ip.att.net [12.122.115.90] 
 19 128 ms 128 ms 127 ms cr2.wswdc.ip.att.net [12.122.3.38] 
 20 125 ms 123 ms 127 ms cr1.wswdc.ip.att.net [12.122.2.29] 
 21 125 ms 123 ms 123 ms cr2.ormfl.ip.att.net [12.122.5.141] 
 22 125 ms 123 ms 124 ms cr81.fldfl.ip.att.net [12.122.1.46] 
 23 127 ms 127 ms 128 ms gar6.fldfl.ip.att.net [12.122.143.209] 
 24 126 ms 128 ms 127 ms *** 
 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.
</code></pre>
</div>

<div>
<div class="content wysiwyg-content">
I am having trouble connecting to my company's VPN. &nbsp;The results of a tracert to the vpn address are shown below and ultimately time out at cr81.fldfl.ip.att.net. &nbsp; 
 
Is this indicative of an AT&amp;T fault? &nbsp;If so, is there a way to locate that outage to follow its progress? 
 

<pre><code class="code-10 nolinks" id="code-10-28914100-1">Tracing route to vpn.***.com [****]
over a maximum of 30 hops:

 1 &lt;1 ms &lt;1 ms &lt;1 ms BThomehub.home [192.168.1.254] 
 2 * * * Request timed out.
 3 * * * Request timed out.
 4 6 ms 6 ms 6 ms 217.41.217.125 
 5 12 ms 13 ms 11 ms 212.140.235.218 
 6 12 ms 11 ms 11 ms 217.41.169.9 
 7 11 ms 10 ms 10 ms 217.41.169.107 
 8 10 ms 10 ms 10 ms acc1-10GigE-3-3-0.sf.21cn-ipp.bt.net [109.159.251.91] 
 9 19 ms 19 ms 19 ms core2-te0-13-0-2.ilford.ukcore.bt.net [109.159.251.11] 
 10 19 ms 19 ms 20 ms 109.159.254.197 
 11 17 ms 17 ms 17 ms 166-49-211-250.eu.bt.net [166.49.211.250] 
 12 18 ms 18 ms 18 ms 82.112.101.73 
 13 17 ms 16 ms 17 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.54] 
 14 20 ms 20 ms 20 ms ae-0.r22.londen03.uk.bb.gin.ntt.net [129.250.4.85] 
 15 87 ms 86 ms 85 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18] 
 16 86 ms 86 ms 86 ms ae-13.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.71] 
 17 90 ms 87 ms 87 ms ae-0.att.nycmny01.us.bb.gin.ntt.net [129.250.9.206] 
 18 128 ms 127 ms 127 ms cr2.n54ny.ip.att.net [12.122.115.90] 
 19 129 ms 127 ms 127 ms cr2.wswdc.ip.att.net [12.122.3.38] 
 20 * * * Request timed out.
 21 * * * Request timed out.
 22 121 ms 123 ms 124 ms cr81.fldfl.ip.att.net [12.122.1.46] 
 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.
</code></pre>
</div>
</div>

I am having trouble connecting to my company's VPN.  The results of a tracert to the vpn address are shown below and ultimately time out at cr81.fldfl.ip.att.net.  

Is this indicative of an AT&T fault?  If so, is there a way to locate that outage to follow its progress?

(CODE)

How to diagnose results from tracert failing at cr81.fldfl.ip.att.net

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Network analysis is the process of identifying and remediating the processes and systems within a network, including performance, connectivity and security. The process is performed through the use of tools developed for monitoring and analyzing network activity. Network problems that involve finding an optimal way of doing something are studied under the name combinatorial optimization. Examples include network flow, shortest path problem, transport problem, transshipment problem, location problem, matching problem, assignment problem, packing problem, routing problem, Critical Path Analysis and PERT (Program Evaluation & Review Technique).

Network Analysis

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.