Send Outages-discussion mailing list submissions to
outages-discussion@outages.org
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
outages-discussion-requ...@outages.org
You can reach the person managing the list at
outages-discussion-ow...@outages.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Idaho Outage (David A. Armstrong)
2. Re: [outages] Akamai Geolocation Concerns (Gary Leato)
3. Re: [outages] Seemingly Nationwide Comcast DNS Outage (Frank Bulk)
----------------------------------------------------------------------
Message: 1
Date: Tue, 14 Jan 2020 20:39:01 +0000
From: "David A. Armstrong" <da...@malheurfcu.org>
To: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: [Outages-discussion] Idaho Outage
Message-ID:
<mwhpr15mb1486db7f157acac9835c45d8ca...@mwhpr15mb1486.namprd15.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Does anyone on this list have information about the outage that occurred in a
good portion of Idaho on Syringa Networks out of Boise, ID? It occurred around
today at 11:20 am MST and was resolved around 12:00pm MST. My local ISP uses
Syringa, but provides limited information to clients.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20200114/55004393/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 17 Jan 2020 16:13:10 -0600
From: Gary Leato <leato2...@gmail.com>
To: Dan White <dwh...@olp.net>, outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Akamai Geolocation
Concerns
Message-ID:
<caox5p8uty-qzps4fgtkv+usll8j6gebzt71gf8gqxawahm1...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I work in K12 as well and had problems with my GeoIP filter with both of
those sites as well.
For office depot, I mapped these IPs to be in the US.
92.123.196.167
2.16.33.76
88.221.37.87
On Fri, Jan 17, 2020 at 1:13 PM Dan White via Outages <outa...@outages.org>
wrote:
> We are seeing some geolocation oddities with a couple of websites hosted
> at, or resolved by, Akamai.
>
> Two hostnames I'm looking at include:
>
> business.officedepot.com
> www.teacherspayteachers.com
>
> 'A' records for both have a TTL of 20 seconds, and randomly resolve to IPs
> in the US, and Europe (we are in the US/Oklahoma).
>
> For example, business.officedepot.com is resolving to both 96.17.32.230
> and
> 88.221.37.87 (at different times). I've verified the same inconsistent
> behavior against 8.8.8.8 and 1.1.1.1.
>
> This is causing issues for an educational customer of ours. Is anyone aware
> of issues within Akamai that may be causing them to source content from
> Europe?
>
> --
> Dan White
> BTC Broadband
> Network Admin Lead
> Ph 918.366.0248 (direct) main: (918)366-8000
> Fax 918.366.6610 email: dwh...@mybtc.com
> http://www.btcbroadband.com
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20200117/7b6576e7/attachment-0001.htm>
------------------------------
Message: 3
Date: Thu, 23 Jan 2020 16:09:59 -0600
From: "Frank Bulk" <frnk...@iname.com>
To: <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] Seemingly Nationwide
Comcast DNS Outage
Message-ID: <001d01d5d239$da77c9b0$8f675d10$@iname.com>
Content-Type: text/plain; charset="utf-8"
Some news here:
https://www.phillyvoice.com/comcast-nationwide-internet-outage-2020-january-23-philadelphia/
Frank
From: Outages <outages-boun...@outages.org> On Behalf Of Cary Wiedemann via
Outages
Sent: Thursday, January 23, 2020 3:02 PM
To: Chris Cherry <cwche...@outlook.com>
Cc: outa...@outages.org
Subject: Re: [outages] Seemingly Nationwide Comcast DNS Outage
Just confirming this outage affected my sites from Virginia to California.
Start time was just before 2:32pm EST and resolution came around 2:54pm EST.
Looks like anycast routing woes. Not good.
- Cary
On Thu, Jan 23, 2020 at 3:38 PM Chris Cherry via Outages <outa...@outages.org
<mailto:outa...@outages.org> > wrote:
No issue here with my 5 Comcast Business accounts (central Indiana), although
we are using OpenDNS. The VPN tunnels are up and running between those sites.
Friends of mine who live up near Chicago who use Comcast and use the default
DNS servers from them are reporting they are up and running.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Christopher Trudeau via Outages <mailto:outa...@outages.org>
Sent: Thursday, January 23, 2020 3:28 PM
To: outa...@outages.org <mailto:outa...@outages.org>
Subject: [outages] Seemingly Nationwide Comcast DNS Outage
Seeing many recent reports on the interwebs regarding a ?nationwide Comcast
outage?.
Looks like it?s an issue with Comcast DNS (75.75.75.75 / 75.75.76.76) and not
anything else, as queries to other public DNS servers (ex: 1.1.1.1 / 8.8.8.8)
work just fine over my Comcast service.
For reference, I?m located in Chicago, but I did perform NSLookup?s from a box
in NYC, Dallas, and Seattle which resulted in similar behavior as seen below.
nslookup google.com <http://google.com> 75.75.75.75
Server: UnKnown
Address: 75.75.75.75
*** UnKnown can't find google.com <http://google.com> : Query refused
nslookup google.com <http://google.com> 75.75.76.76
Server: UnKnown
Address: 75.75.76.76
*** UnKnown can't find google.com <http://google.com> : Query refused
nslookup google.com <http://google.com> 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: google.com <http://google.com>
Addresses: 2607:f8b0:4009:812::200e
172.217.5.14
nslookup google.com <http://google.com> 8.8.8.8
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: google.com <http://google.com>
Addresses: 2607:f8b0:4009:80f::200e
216.58.192.238
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or
previous e-mail messages attached to it may contain confidential information
that is legally privileged. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are hereby
notified that any disclosure, copying, distribution or use of any of the
information contained in or attached to this transmission is STRICTLY
PROHIBITED. If you have received this transmission in error please notify the
sender immediately by replying to this e-mail. You must destroy the original
transmission and its attachments without reading or saving in any manner. Thank
you.
_______________________________________________
Outages mailing list
outa...@outages.org <mailto:outa...@outages.org>
https://puck.nether.net/mailman/listinfo/outages
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20200123/696c6449/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 160 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20200123/696c6449/attachment.png>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 122, Issue 1
**************************************************
