<div dir="ltr"><div dir="ltr"><div dir="ltr">FYI, VDMS acknowledged this, investigated, and just now considered the issue resolved: <a href="https://status.verizondigitalmedia.com/pages/incident/5736344c90417cda1a000f3f/5c4b4c4023395904bd439c78">https://status.verizondigitalmedia.com/pages/incident/5736344c90417cda1a000f3f/5c4b4c4023395904bd439c78</a><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Not sure if this holds true for any other entities impacted by the AT&T issues, but that should at least clear up the Verizon side of things.</span></div><div dir="ltr"><span style="font-size:12.8px"><br></span></div><div dir="ltr"><span style="font-size:12.8px">--</span><br style="font-size:12.8px"><span style="font-size:12.8px">Andy Walker</span><br style="font-size:12.8px"><span style="font-size:12.8px">System Administrator</span><br style="font-size:12.8px"><span style="font-size:12.8px">FBS - creators of flexmls</span><br style="font-size:12.8px"><span style="font-size:12.8px">3415 39th St S</span><br style="font-size:12.8px"><span style="font-size:12.8px">Fargo, ND 58104</span><br style="font-size:12.8px"><span style="font-size:12.8px">701-235-7300</span><br></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 25, 2019 at 12:37 PM Mel Beckman <<a href="mailto:mel@becknet.com">mel@becknet.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I can get there from Frontier:<br>
<br>
traceroute 192.229.210.64<br>
traceroute to 192.229.210.64 (192.229.210.64), 64 hops max, 52 byte <br>
packets<br>
1 47.155.227.1 (47.155.227.1) 9.475 ms 4.429 ms 4.657 ms<br>
2 172.102.107.164 (172.102.107.164) 10.263 ms 9.723 ms<br>
172.102.102.240 (172.102.102.240) 7.703 ms<br>
3 <a href="http://ae8---0.scr01.lsan.ca.frontiernet.net" rel="noreferrer" target="_blank">ae8---0.scr01.lsan.ca.frontiernet.net</a> (74.40.3.37) 7.241 ms<br>
<a href="http://ae8---0.scr02.lsan.ca.frontiernet.net" rel="noreferrer" target="_blank">ae8---0.scr02.lsan.ca.frontiernet.net</a> (74.40.3.49) 7.696 ms <br>
7.243 ms<br>
4 <a href="http://ae0---0.cbr01.lsan.ca.frontiernet.net" rel="noreferrer" target="_blank">ae0---0.cbr01.lsan.ca.frontiernet.net</a> (74.40.3.198) 5.970 ms<br>
<a href="http://ae1---0.cbr01.lsan.ca.frontiernet.net" rel="noreferrer" target="_blank">ae1---0.cbr01.lsan.ca.frontiernet.net</a> (74.40.3.214) 6.743 ms<br>
<a href="http://ae0---0.cbr01.lsan.ca.frontiernet.net" rel="noreferrer" target="_blank">ae0---0.cbr01.lsan.ca.frontiernet.net</a> (74.40.3.198) 7.843 ms<br>
5 74.43.94.17 (74.43.94.17) 6.711 ms 9.975 ms 10.083 ms<br>
6 152.195.77.129 (152.195.77.129) 9.682 ms 9.829 ms 9.679 ms<br>
7 192.229.210.64 (192.229.210.64) 7.438 ms 9.798 ms 7.496 ms<br>
<br>
As a precaution, you should check to make sure you’re not black-holed <br>
by AT&T. We had an incident over Christmas where AT&T automated <br>
security had black-holed our branch office connectivity to our AT&T <br>
hub site! We only proved it and got the block pulled by showing the <br>
destination was reachable from many other locations.<br>
<br>
-mel<br>
<br>
On Fri, 25 Jan 2019 18:03:30 +0000<br>
Geeknik Labs via Outages <<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br>
> Seeing increased latency and packet loss across AT&T Uverse just <br>
>outside of Oklahoma City, currently unable to communicate with most <br>
>if not all of our remote clients at this time. AT&T has no <br>
>information for us and won’t even acknowledge they are having issues <br>
>or that an outage is occurring.<br>
> <br>
> Sent from ProtonMail Mobile<br>
> <br>
> On Fri, Jan 25, 2019 at 10:40, Brian Ladd via Outages <br>
><<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br>
> <br>
>> We're seeing inbound calling issues with East TN numbers that <br>
>>probably backhaul/peer with AT&T via Bandwidth.com/Level 3. Started <br>
>>around 45 min ago<br>
>><br>
>> Brian Ladd<br>
>> Customer Care Manager<br>
>> Voiceopia Communications<br>
>><br>
>> On Fri, Jan 25, 2019 at 11:29 AM Andy W via Outages <br>
>><<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br>
>><br>
>>> We have a handful of users who have reported issues to us that point <br>
>>>to a problem between AT&T/SBCGlobal in Knoxville, TN and <br>
>>>Jacksonville, FL and our CDN provider -- Edgecast/Verizon/VDMS. It <br>
>>>appears that Downdetector has a bit more of an uptick for AT&T than <br>
>>>they usually do, so it could very well affect more than just the <br>
>>>route to VDMS.<br>
>>><br>
>>> Some traceroutes:<br>
>>><br>
>>>> Tracing route to <a href="http://cs493.wpc.edgecastcdn.net" rel="noreferrer" target="_blank">cs493.wpc.edgecastcdn.net</a> [192.229.210.64] over a <br>
>>>>maximum of 30 hops: 1 10 ms 11 ms 19 ms homeportal <br>
>>>>[192.168.1.254]2 140 ms 71 ms 30 ms <br>
>>>> <a href="http://99-51-96-1.lightspeed.jcvlfl.sbcglobal.net" rel="noreferrer" target="_blank">99-51-96-1.lightspeed.jcvlfl.sbcglobal.net</a><br>
>>>> 3 84 ms 23 ms 21 ms 99.166.204.1854 59 ms 110 ms 29 ms <br>
>>>> 99.132.13.665 51 ms 88 ms 137 ms 12.83.101.376 * <br>
>>>> * * Request timed out.7 * * * <br>
>>>> Request timed out.<br>
>>><br>
>>>> Tracing route to <a href="http://cs493.wpc.edgecastcdn.net" rel="noreferrer" target="_blank">cs493.wpc.edgecastcdn.net</a> [192.229.210.64]<br>
>>>> over a maximum of 30 hops:<br>
>>>> 1 2 ms 4 ms 3 ms homeportal [192.168.1.254]<br>
>>>> 2 29 ms 21 ms 25 ms <br>
>>>> <a href="http://99-17-80-1.lightspeed.knvltn.sbcglobal.net" rel="noreferrer" target="_blank">99-17-80-1.lightspeed.knvltn.sbcglobal.net</a><br>
>>>> 3 22 ms 21 ms 45 ms 99.17.140.5<br>
>>>> 4 * * * Request timed out.<br>
>>>> 5 * * * Request timed out.<br>
>>>> 6 * * * Request timed out.<br>
>>><br>
>>> --<br>
>>> Andy Walker<br>
>>> System Administrator<br>
>>> FBS - creators of flexmls<br>
>>> 3415 39th St S<br>
>>> Fargo, ND 58104<br>
>>> 701-235-7300<br>
>>> _______________________________________________<br>
>>> Outages mailing list<br>
>>> <a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br>
>>> <a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div>