Dylan Ebner via Outages | 24 Nov 11:09 2014

[outages] Network Solutions DNS not resolving on Comcast or CenturyLink networks


We have multiple network solutions domain names not resolving currently when using comcast or CL dns servers. Google public dns servers do resolve. 

networksolutions.com also does not resolve on comcast or CL dns servers. It does resolve on google dns servers but it is not accessable.



COMCAST DNS SERVERS: DOES NOT WORK
> server 75.75.76.76
Default Server:  cdns02.comcast.net
Address:  75.75.76.76

Server:  cdns02.comcast.net
Address:  75.75.76.76

*** cdns02.comcast.net can't find dms.crlmed.com: Server failed

CENTURY LINK SERVERS: DOES NOT WORK
> server 205.171.3.65
Default Server:  resolver1.qwest.net
Address:  205.171.3.65

Address:  205.171.3.65

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to resolver1.qwest.net timed-out



GOOGLE PUBLIC DNS: WORKS
> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Address:  8.8.8.8

Non-authoritative answer:
Name:    dms.crlmed.com
Address:  67.135.55.235


Networksolutions.com also does not work:


COMCAST DNS: NOT WORKING

> server 75.75.76.76
Default Server:  cdns02.comcast.net
Address:  75.75.76.76

Address:  75.75.76.76

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to cdns02.comcast.net timed-out


CENTURY LINK NOT WORKING
> server 205.171.3.65
Default Server:  resolver1.qwest.net
Address:  205.171.3.65

Address:  205.171.3.65

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to resolver1.qwest.net timed-out
>

GOOGLE Public DNS WORKS
> server 8.8.8.8
Address:  8.8.8.8

Address:  8.8.8.8

Non-authoritative answer:
Address:  205.178.187.13


Tracert from comcast network to networksolutions.com:


C:\Users\Larry>tracert 205.178.187.13

Tracing route to 205.178.187.13 over a maximum of 30 hops

  1     1 ms    <1 ms     1 ms  10.0.1.1
  2     *        9 ms    10 ms  96.120.48.221
  3    12 ms     9 ms     9 ms  te-0-2-0-6-sur01.nempls.mn.minn.comcast.net [68.
85.164.177]
  4    11 ms    15 ms    13 ms  te-0-4-0-13-ar01.roseville.mn.minn.comcast.net [
69.139.219.193]
  5    24 ms    19 ms    19 ms  he-5-3-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.166.253]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *
<div>
<div>
<br><div>
<div>
<div class="BodyFragment">
<div class="PlainText">We have multiple network solutions domain names not resolving currently when using comcast or CL dns servers. Google public dns servers do resolve.&nbsp;
</div>
<div class="PlainText"><br></div>
<div class="PlainText">networksolutions.com also does not resolve on comcast or CL dns servers. It does resolve on google dns servers but it is not accessable.</div>
<div class="PlainText"><br></div>
<div class="PlainText"><br></div>
<div class="PlainText"><br></div>
<div class="PlainText">
<div>
COMCAST DNS SERVERS: DOES NOT WORK</div>
<div>
&gt; server 75.75.76.76</div>
<div>
Default Server: &nbsp;<a href="http://cdns02.comcast.net/" target="_blank">cdns02.comcast.net</a>
</div>
<div>
Address: &nbsp;75.75.76.76</div>
<div>
<br>
</div>
<div>
&gt;&nbsp;<a href="http://dms.crlmed.com/" target="_blank">dms.crlmed.com</a>
</div>
<div>
Server: &nbsp;<a href="http://cdns02.comcast.net/" target="_blank">cdns02.comcast.net</a>
</div>
<div>
Address: &nbsp;75.75.76.76</div>
<div>
<br>
</div>
<div>
***&nbsp;<a href="http://cdns02.comcast.net/" target="_blank">cdns02.comcast.net</a>&nbsp;can't find&nbsp;<a href="http://dms.crlmed.com/" target="_blank">dms.crlmed.com</a>: Server failed</div>
<div>
<br>
</div>
<div>
CENTURY LINK SERVERS: DOES NOT WORK</div>
<div>
&gt; server 205.171.3.65</div>
<div>
Default Server: &nbsp;<a href="http://resolver1.qwest.net/" target="_blank">resolver1.qwest.net</a>
</div>
<div>
Address: &nbsp;205.171.3.65</div>
<div>
<br>
</div>
<div>
&gt;&nbsp;<a href="http://dms.crlmed.com/" target="_blank">dms.crlmed.com</a>
</div>
<div>
Server: &nbsp;<a href="http://resolver1.qwest.net/" target="_blank">resolver1.qwest.net</a>
</div>
<div>
Address: &nbsp;205.171.3.65</div>
<div>
<br>
</div>
<div>
DNS request timed out.</div>
<div>
&nbsp; &nbsp; timeout was 2 seconds.</div>
<div>
DNS request timed out.</div>
<div>
&nbsp; &nbsp; timeout was 2 seconds.</div>
<div>
*** Request to&nbsp;<a href="http://resolver1.qwest.net/" target="_blank">resolver1.qwest.net</a>&nbsp;timed-out</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
GOOGLE PUBLIC DNS: WORKS</div>
<div>
&gt; server 8.8.8.8</div>
<div>
Default Server: &nbsp;<a href="http://google-public-dns-a.google.com/" target="_blank">google-public-dns-a.google.com</a>
</div>
<div>
Address: &nbsp;8.8.8.8</div>
<div>
<br>
</div>
<div>
&gt;&nbsp;<a href="http://dms.crlmed.com/" target="_blank">dms.crlmed.com</a>
</div>
<div>
Server: &nbsp;<a href="http://google-public-dns-a.google.com/" target="_blank">google-public-dns-a.google.com</a>
</div>
<div>
Address: &nbsp;8.8.8.8</div>
<div>
<br>
</div>
<div>
Non-authoritative answer:</div>
<div>
Name: &nbsp; &nbsp;<a href="http://dms.crlmed.com/" target="_blank">dms.crlmed.com</a>
</div>
<div>
Address: &nbsp;67.135.55.235</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
Networksolutions.com also does not work:</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
COMCAST DNS: NOT WORKING</div>
<div>
<div><br></div>
<div>&gt; server 75.75.76.76</div>
<div>Default Server: &nbsp;<a href="http://cdns02.comcast.net/" target="_blank">cdns02.comcast.net</a>
</div>
<div>Address: &nbsp;75.75.76.76</div>
<div><br></div>
<div>&gt;&nbsp;<a href="http://networksolutions.com/" target="_blank">networksolutions.com</a>
</div>
<div>Server: &nbsp;<a href="http://cdns02.comcast.net/" target="_blank">cdns02.comcast.net</a>
</div>
<div>Address: &nbsp;75.75.76.76</div>
<div><br></div>
<div>DNS request timed out.</div>
<div>&nbsp; &nbsp; timeout was 2 seconds.</div>
<div>DNS request timed out.</div>
<div>&nbsp; &nbsp; timeout was 2 seconds.</div>
<div>*** Request to&nbsp;<a href="http://cdns02.comcast.net/" target="_blank">cdns02.comcast.net</a>&nbsp;timed-out</div>
<div><br></div>
<div><br></div>
<div>CENTURY LINK NOT WORKING<br>
</div>
<div>&gt; server 205.171.3.65</div>
<div>Default Server: &nbsp;<a href="http://resolver1.qwest.net/" target="_blank">resolver1.qwest.net</a>
</div>
<div>Address: &nbsp;205.171.3.65</div>
<div><br></div>
<div>&gt;&nbsp;<a href="http://networksolutions.com/" target="_blank">networksolutions.com</a>
</div>
<div>Server: &nbsp;<a href="http://resolver1.qwest.net/" target="_blank">resolver1.qwest.net</a>
</div>
<div>Address: &nbsp;205.171.3.65</div>
<div><br></div>
<div>DNS request timed out.</div>
<div>&nbsp; &nbsp; timeout was 2 seconds.</div>
<div>DNS request timed out.</div>
<div>&nbsp; &nbsp; timeout was 2 seconds.</div>
<div>*** Request to&nbsp;<a href="http://resolver1.qwest.net/" target="_blank">resolver1.qwest.net</a>&nbsp;timed-out</div>
<div>&gt;</div>
</div>
<div>
<br>
</div>
<div>
GOOGLE Public DNS WORKS</div>
<div>
<div>&gt; server 8.8.8.8</div>
<div>Default Server: &nbsp;<a href="http://google-public-dns-a.google.com/" target="_blank">google-public-dns-a.google.com</a>
</div>
<div>Address: &nbsp;8.8.8.8</div>
</div>
<div>
<div>
<br>
</div>
<div>
&gt;&nbsp;<a href="http://networksolutions.com/" target="_blank">networksolutions.com</a>
</div>
<div>
Server: &nbsp;<a href="http://google-public-dns-a.google.com/" target="_blank">google-public-dns-a.google.com</a>
</div>
<div>
Address: &nbsp;8.8.8.8</div>
<div>
<br>
</div>
<div>
Non-authoritative answer:</div>
<div>
Name: &nbsp; &nbsp;<a href="http://networksolutions.com/" target="_blank">networksolutions.com</a>
</div>
<div>
Address: &nbsp;205.178.187.13</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
Tracert from comcast network to networksolutions.com:</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<div>C:\Users\Larry&gt;tracert 205.178.187.13</div>
<div><br></div>
<div>Tracing route to 205.178.187.13 over a maximum of 30 hops</div>
<div><br></div>
<div>&nbsp; 1 &nbsp; &nbsp; 1 ms &nbsp; &nbsp;&lt;1 ms &nbsp; &nbsp; 1 ms &nbsp;10.0.1.1</div>
<div>&nbsp; 2 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;9 ms &nbsp; &nbsp;10 ms &nbsp;96.120.48.221</div>
<div>&nbsp; 3 &nbsp; &nbsp;12 ms &nbsp; &nbsp; 9 ms &nbsp; &nbsp; 9 ms &nbsp;te-0-2-0-6-sur01.nempls.mn.minn.comcast.net [68.</div>
<div>85.164.177]</div>
<div>&nbsp; 4 &nbsp; &nbsp;11 ms &nbsp; &nbsp;15 ms &nbsp; &nbsp;13 ms &nbsp;te-0-4-0-13-ar01.roseville.mn.minn.comcast.net [</div>
<div>69.139.219.193]</div>
<div>&nbsp; 5 &nbsp; &nbsp;24 ms &nbsp; &nbsp;19 ms &nbsp; &nbsp;19 ms &nbsp;he-5-3-0-0-cr01.350ecermak.il.ibone.comcast.net</div>
<div>[68.86.166.253]</div>
<div>&nbsp; 6 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out.</div>
<div>&nbsp; 7 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out.</div>
<div>&nbsp; 8 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out.</div>
<div>&nbsp; 9 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out.</div>
<div>&nbsp;10 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out.</div>
<div>&nbsp;11 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;*</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
*Network via Outages | 20 Nov 13:56 2014

[outages] Level 3 outages - Chicago

 

Here is respond from Level 3

 

 

 

"The IP NOC continues to investigate the routing issues for multiple customer after configuration changes to routing protocols on a device restored services for some. Troubleshooting is ongoing with no ETTR available."

 

What the next step is: I am associating this ticket to the parent event for the outage.

 

Timeline for next step: You will receive further updates from our event team as they are available.

 

Please contact me if you have any questions.

 

 

<div>
<div class="WordSection1">
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Here is respond from Level 3 <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoPlainText"><p>&nbsp;</p></p>
<p class="MsoPlainText">"The IP NOC continues to investigate the routing issues for multiple customer after configuration changes to routing protocols on a device restored services for some. Troubleshooting is ongoing with no ETTR available."<p></p></p>
<p class="MsoPlainText"><p>&nbsp;</p></p>
<p class="MsoPlainText">What the next step is: I am associating this ticket to the parent event for the outage.<p></p></p>
<p class="MsoPlainText"><p>&nbsp;</p></p>
<p class="MsoPlainText">Timeline for next step: You will receive further updates from our event team as they are available.<p></p></p>
<p class="MsoPlainText"><p>&nbsp;</p></p>
<p class="MsoPlainText">Please contact me if you have any questions.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Frank Bulk | 19 Nov 18:14 2014
Picon

Yesterday's news: Microsoft Azure hit with major service outage affecting OneDrive, Microsoft Blogs, Microsoft Band, and more

FYI

http://www.winbeta.org/news/microsoft-azure-hit-major-service-outage-affecting-onedrive-microsoft-blogs-microsoft-band-and

Microsoft's cloud service was hit with an unexpected global outage today [11/18/2014], lasting nearly an hour. "An alert for Websites and Storage in multiple regions is being investigated. It has not been determined if this is customer impacting. More information will be provided as it is known," the Azure Status page stated during the outage.

Frank

<div><div class="WordSection1">
<p><span>FYI<p></p></span></p>
<p><span><a href="http://www.winbeta.org/news/microsoft-azure-hit-major-service-outage-affecting-onedrive-microsoft-blogs-microsoft-band-and">http://www.winbeta.org/news/microsoft-azure-hit-major-service-outage-affecting-onedrive-microsoft-blogs-microsoft-band-and</a><p></p></span></p>
<p>Microsoft's cloud service was hit with an unexpected global outage today [11/18/2014], lasting nearly an hour. "An alert for Websites and Storage in multiple regions is being investigated. It has not been determined if this is customer impacting. More information will be provided as it is known," the Azure Status page stated during the outage.<p></p></p>
<p>Frank<p></p></p>
</div></div>
jd via Outages | 19 Nov 00:32 2014

[outages] zayo fiber cut in los angeles

anyone affected? i think it happened about 60-75 minutes ago.

thanks
Aaron Dean via Outages | 18 Nov 15:59 2014

[outages] Minor Atlanta outage?

I'm seeing some packet loss along the route to NYC from ATL, in this example specifically to DigitalOcean.  Here's the MTR

  4. 66.179.228.85                 0.0%    10    2.7   2.5   2.3   2.7   0.1
  5. 67.133.162.89                 0.0%    10    4.3   7.0   4.2  29.6   8.0
  6. 67.14.14.134                  0.0%    10    4.7   5.7   4.7   9.5   1.4
  7. 129.250.8.193                 0.0%    10    6.1   6.3   5.6   7.7   0.7
  8. 129.250.5.214                50.0%    10   56.4  56.8  54.7  62.3   3.1
  9. 129.250.2.148                10.0%    10   59.9  61.9  59.9  72.2   3.9
 10. 129.250.4.69                 10.0%    10   59.2  61.1  59.2  65.1   1.7
 11. 129.250.203.86               10.0%    10   60.2  61.0  59.5  63.0   1.1
 12. 192.241.164.242              20.0%    10   60.1  61.7  60.1  64.0   1.4

With DNS:

  4. alp1br1-te-0-0-2-1.sgns.net   0.0%    10    2.5   3.1   2.2   6.2   1.3
  5. frp-edge-06.inet.qwest.net    0.0%    10    4.3   6.9   4.1  30.4   8.2
  6. atx-brdr-01.inet.qwest.net    0.0%    10    6.3   5.4   4.7   7.4   0.9
  7. ae-18.r04.atlnga05.us.bb.gin  0.0%    10    6.0   6.5   5.7   7.8   0.7
  8. ae-8.r20.asbnva02.us.bb.gin. 10.0%    10   54.4  56.3  54.3  63.4   3.1
  9. ae-8.r23.nycmny01.us.bb.gin. 20.0%    10   59.3  63.0  59.1  76.7   5.7
 10. ae-1.r05.nycmny01.us.bb.gin. 40.0%    10   60.0  60.5  60.0  61.6   0.6
 11. xe-0-3-0-21.r05.nycmny01.us. 10.0%    10   64.0  61.3  60.1  64.0   1.4
 12. 192.241.164.242              10.0%    10   60.4  61.0  59.9  63.1   1.0


<div><div dir="ltr">I'm seeing some packet loss along the route to NYC from ATL, in this example specifically to DigitalOcean.&nbsp; Here's the MTR<div><br></div>
<div>
<div>&nbsp; 4. 66.179.228.85 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;2.7 &nbsp; 2.5 &nbsp; 2.3 &nbsp; 2.7 &nbsp; 0.1</div>
<div>&nbsp; 5. 67.133.162.89 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;4.3 &nbsp; 7.0 &nbsp; 4.2 &nbsp;29.6 &nbsp; 8.0</div>
<div>&nbsp; 6. 67.14.14.134 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;4.7 &nbsp; 5.7 &nbsp; 4.7 &nbsp; 9.5 &nbsp; 1.4</div>
<div>&nbsp; 7. 129.250.8.193 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;6.1 &nbsp; 6.3 &nbsp; 5.6 &nbsp; 7.7 &nbsp; 0.7</div>
<div>&nbsp; 8. 129.250.5.214 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;50.0% &nbsp; &nbsp;10 &nbsp; 56.4 &nbsp;56.8 &nbsp;54.7 &nbsp;62.3 &nbsp; 3.1</div>
<div>&nbsp; 9. 129.250.2.148 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.0% &nbsp; &nbsp;10 &nbsp; 59.9 &nbsp;61.9 &nbsp;59.9 &nbsp;72.2 &nbsp; 3.9</div>
<div>&nbsp;10. 129.250.4.69 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10.0% &nbsp; &nbsp;10 &nbsp; 59.2 &nbsp;61.1 &nbsp;59.2 &nbsp;65.1 &nbsp; 1.7</div>
<div>&nbsp;11. 129.250.203.86 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10.0% &nbsp; &nbsp;10 &nbsp; 60.2 &nbsp;61.0 &nbsp;59.5 &nbsp;63.0 &nbsp; 1.1</div>
<div>&nbsp;12. 192.241.164.242 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;20.0% &nbsp; &nbsp;10 &nbsp; 60.1 &nbsp;61.7 &nbsp;60.1 &nbsp;64.0 &nbsp; 1.4</div>
<div><br></div>
<div>With DNS:</div>
<div><br></div>
<div>
<div>&nbsp; 4. <a href="http://alp1br1-te-0-0-2-1.sgns.net">alp1br1-te-0-0-2-1.sgns.net</a> &nbsp; 0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;2.5 &nbsp; 3.1 &nbsp; 2.2 &nbsp; 6.2 &nbsp; 1.3</div>
<div>&nbsp; 5. <a href="http://frp-edge-06.inet.qwest.net">frp-edge-06.inet.qwest.net</a> &nbsp; &nbsp;0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;4.3 &nbsp; 6.9 &nbsp; 4.1 &nbsp;30.4 &nbsp; 8.2</div>
<div>&nbsp; 6. <a href="http://atx-brdr-01.inet.qwest.net">atx-brdr-01.inet.qwest.net</a> &nbsp; &nbsp;0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;6.3 &nbsp; 5.4 &nbsp; 4.7 &nbsp; 7.4 &nbsp; 0.9</div>
<div>&nbsp; 7. ae-18.r04.atlnga05.us.bb.gin &nbsp;0.0% &nbsp; &nbsp;10 &nbsp; &nbsp;6.0 &nbsp; 6.5 &nbsp; 5.7 &nbsp; 7.8 &nbsp; 0.7</div>
<div>&nbsp; 8. ae-8.r20.asbnva02.us.bb.gin. 10.0% &nbsp; &nbsp;10 &nbsp; 54.4 &nbsp;56.3 &nbsp;54.3 &nbsp;63.4 &nbsp; 3.1</div>
<div>&nbsp; 9. ae-8.r23.nycmny01.us.bb.gin. 20.0% &nbsp; &nbsp;10 &nbsp; 59.3 &nbsp;63.0 &nbsp;59.1 &nbsp;76.7 &nbsp; 5.7</div>
<div>&nbsp;10. ae-1.r05.nycmny01.us.bb.gin. 40.0% &nbsp; &nbsp;10 &nbsp; 60.0 &nbsp;60.5 &nbsp;60.0 &nbsp;61.6 &nbsp; 0.6</div>
<div>&nbsp;11. <a href="http://xe-0-3-0-21.r05.nycmny01.us">xe-0-3-0-21.r05.nycmny01.us</a>. 10.0% &nbsp; &nbsp;10 &nbsp; 64.0 &nbsp;61.3 &nbsp;60.1 &nbsp;64.0 &nbsp; 1.4</div>
<div>&nbsp;12. 192.241.164.242 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.0% &nbsp; &nbsp;10 &nbsp; 60.4 &nbsp;61.0 &nbsp;59.9 &nbsp;63.1 &nbsp; 1.0</div>
<div><br></div>
</div>
<div><br></div>
</div>
</div></div>

[outages] Senderbase.org down?

The server is temporarily unable to service your request. Please try
again later.
Reference #6.50957441.1416316609.68fa71c

-- 
Marco

Attachment (smime.p7s): application/pkcs7-signature, 5714 bytes
The server is temporarily unable to service your request. Please try
again later.
Reference #6.50957441.1416316609.68fa71c

--

-- 
Marco

Andrew Losey via Outages | 17 Nov 21:22 2014

[outages] Level3 LAX latency - backhoe fever?

Howdy,
Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA?

traceroute to xxx.xxxxx.com (xx.xx.xx.xx), 30 hops max, 60 byte packets
 1  xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx)  0.395 ms  0.379 ms  0.324 ms
 2  xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221)  0.652 ms  0.694 ms  0.691 ms
 3  * * *
 4  ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73)  107.206 ms
ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137)  108.328 ms  109.351 ms
 5  xxxxxxxxxxxx.edge3.LosAngeles1.Level3.net (xx.xx.xx.xx)  94.529 ms  94.589 ms  91.664 ms
 6  xxxx.xxxxxxxx.com (xx.xx.xx.xx)  66.823 ms  77.933 ms  76.571 ms
Spencer Gaw via Outages | 17 Nov 19:58 2014

[outages] unsub test

test
Brian Kovats via Outages | 17 Nov 19:47 2014

[outages] Windstream voice issues?

We had a few reports of not being able to dial out but not all outcalls seemed to be affected and we were receiving calls.  WS said it was a nation-wide issue that was getting extreme priority.  Things got back to normal by about 11am EST.  Keeping an eye on it, though, since the tech also mentioned that they were still getting reports that indicated it was sporadic and may intermittently still affect some customers.

 

Brian Kovats, IT Technician

 

<div><div class="WordSection1">
<p class="MsoNormal">We had a few reports of not being able to dial out but not all outcalls seemed to be affected and we were receiving calls.&nbsp; WS said it was a nation-wide issue that was getting extreme priority.&nbsp; Things got back to normal by about 11am EST.&nbsp; Keeping an eye on it, though, since the tech also mentioned that they were still getting reports that indicated it was sporadic and may intermittently still affect some customers.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><span>Brian Kovats</span><span>, IT Technician<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div></div>

[outages] unsubscribe

unsubscribe

 

<div>
<div class="WordSection1">
<p class="MsoNormal">unsubscribe<span><p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Julian Y Koh via Outages | 17 Nov 16:48 2014

[outages] Windstream voice issues?

Anyone seeing issues with Windstream’s voice network this morning?  We’re seeing intermittent
problems with inbound and outbound calling, looks like it started shortly after 8:45am CST.  

--

-- 
Julian Y. Koh
Acting Associate Director, Telecommunications and Network Services
Northwestern University Information Technology (NUIT)

2001 Sheridan Road #G-166
Evanston, IL 60208
847-467-5780
NUIT Web Site: <http://www.it.northwestern.edu/>
PGP Public Key:<http://bt.ittns.northwestern.edu/julian/pgppubkey.html>

_______________________________________________
Outages mailing list
Outages <at> outages.org
https://puck.nether.net/mailman/listinfo/outages

Gmane