comcast chicago blackholing
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing. - Jared -- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Looks like a CEF issue or similar. Traffic to 74.125.225.1 is fine 74.125.225.2 is not 74.125.225.3 is fine 74.125.225.4 is not .... Cheers, Kris On 17 November 2015 at 11:00, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Seeing it in DFW as reported over XO but not Zayo. MTR over XO from DFW 1.|-- 172.16.214.11 0.0% 10 0.5 0.6 0.5 0.8 0.0 2.|-- hide.me.scary.internet 0.0% 10 0.8 0.8 0.8 0.9 0.0 3.|-- 216.156.16.156.ptr.us.xo.net 0.0% 10 26.9 26.4 26.3 26.9 0.0 4.|-- 207.88.12.172.ptr.us.xo.net 0.0% 10 26.4 26.4 26.3 26.5 0.0 5.|-- 207.88.12.171.ptr.us.xo.net 0.0% 10 26.4 26.9 26.3 30.2 1.2 6.|-- 207.88.13.131.ptr.us.xo.net 0.0% 10 26.3 26.3 26.3 26.3 0.0 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 Just dies at Comcast/xo border. I've emailed the Comcast routing team as we have voice traffic back and forth which is affected. -----Original Message----- From: Joseph Jackson Sent: Tuesday, November 17, 2015 11:07 AM To: 'Kris Amy'; Jared Mauch Subject: RE: [outages] comcast chicago blackholing We are seeing Comcast traffic being blackholed in DFW over XO. Over Zayo for the same destinations it is reachable. We have a contact in Comcast that pushed it back on to us. So I'm glad to see others over other networks are seeing the same issue. -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Kris Amy via Outages Sent: Tuesday, November 17, 2015 11:02 AM To: Jared Mauch Cc: outages@outages.org Subject: Re: [outages] comcast chicago blackholing Looks like a CEF issue or similar. Traffic to 74.125.225.1 is fine 74.125.225.2 is not 74.125.225.3 is fine 74.125.225.4 is not .... Cheers, Kris On 17 November 2015 at 11:00, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I see similar problems reaching Comcast through Chicago through NTT. A general lack of connectivity. traceroute to 173.14.36.46 (173.14.36.46), 30 hops max, 60 byte packets 1 ve5.cr1.ord0.amcbb.net (208.78.26.113) 0.426 ms 0.486 ms 0.531 ms 2 ve10.cr2.ord1.amcbb.net (208.78.26.238) 0.264 ms 0.406 ms 0.555 ms 3 xe-0-7-0-11-51.r06.chcgil09.us.bb.gin.ntt.net (128.242.180.145) 0.712 ms 0.735 ms 0.757 ms 4 ae-8.r05.chcgil09.us.bb.gin.ntt.net (129.250.4.221) 0.689 ms 0.713 ms 0.733 ms 5 * * * 6 * * * On Tue, Nov 17, 2015 at 12:00 PM, Jared Mauch via Outages < outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- *James Cornman* *Chief Technology Officer*jcornman@atlanticmetro.net 212.792.9950 - ext 101 *Atlantic Metro Communications* *4 Century Drive, Parsippany NJ 07054* *Colocation • Cloud Hosting • Network Connectivity • Managed Services* Follow us on Twitter: @atlanticmetro <https://twitter.com/atlanticmetro> *• Like us on Facebook <https://www.facebook.com/atlanticmetro>* www.atlanticmetro.net
Can you give me some more details please? I'll take a look. Thanks, John On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I'm having trouble reaching several hosts on Akamai including 23.74.8.91. he-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net is the hop I'm dying at. Kevin Reedy kevinreedy@gmail.com | 708.421.9526 <7084219526> kevinreedy.net | @kevinreedy <http://www.twitter.com/kevinreedy> On Tue, Nov 17, 2015 at 11:02 AM, John Neiberger via Outages < outages@outages.org> wrote:
Can you give me some more details please? I'll take a look.
Thanks, John
On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only
mine.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
This is both an issue over V6 and V4, eg: Jareds-Mac-mini:~% traceroute puck traceroute to puck.nether.net (204.42.254.5), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.603 ms 0.418 ms 0.403 ms 2 173-167-0-110-michigan.hfc.comcastbusiness.net (173.167.0.110) 2.044 ms 2.019 ms 2.179 ms 3 96.120.40.141 (96.120.40.141) 17.399 ms 12.408 ms 9.639 ms 4 68.85.85.37 (68.85.85.37) 14.371 ms 8.378 ms 15.355 ms 5 te-0-8-0-6-ar02.pontiac.mi.michigan.comcast.net (68.87.191.153) 14.025 ms te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net (69.139.255.69) 14.749 ms 18.706 ms 6 be-33668-cr02.350ecermak.il.ibone.comcast.net (68.86.90.45) 21.955 ms 20.456 ms 19.259 ms 7 he-0-16-0-0-pe03.350ecermak.il.ibone.comcast.net (68.86.88.146) 18.333 ms 17.245 ms 16.952 ms ^C Jareds-Mac-mini:~% traceroute6 puck traceroute6 to puck.nether.net (2001:418:3f4::5) from 2601:401:3:6a00:ad42:ce75:8a0:c370, 64 hops max, 12 byte packets 1 2601:401:3:6a00:20f:f7ff:feab:1ec0 1.135 ms 0.965 ms 0.948 ms 2 2601:401:3:6a00:4694:fcff:fecd:64bc 3.710 ms 3.544 ms 21.221 ms 3 2001:558:6007:24::1 30.051 ms 10.909 ms 10.868 ms 4 te8-2-ur02.wannarbor.mi.michigan.comcast.net 10.664 ms 10.451 ms 10.570 ms 5 xe-11-1-0-0-sur01.rochestrhlls.mi.michigan.comcast.net 14.826 ms te-0-8-0-5-ar02.taylor.mi.michigan.comcast.net 13.890 ms 13.179 ms 6 te-0-7-0-13-ar01.pontiac.mi.michigan.comcast.net 18.917 ms 15.503 ms te-0-8-0-11-ar01.pontiac.mi.michigan.comcast.net 13.686 ms 7 be-33668-cr01.350ecermak.il.ibone.comcast.net 22.316 ms 22.014 ms 28.086 ms 8 hu-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net 20.933 ms 20.740 ms 20.831 ms ^C - Jared On Tue, Nov 17, 2015 at 10:02:58AM -0700, John Neiberger wrote:
Can you give me some more details please? I'll take a look.
Thanks, John
On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Thanks, all. Our side should be resolved now. Had a combination of a linecard fabric failure and a partial RSP failure. We're back in working shape and BGP from our core to that edge router is back up. Should be safe for peers to turn sessions back up. John On Tue, Nov 17, 2015 at 10:15 AM, Jared Mauch <jared@puck.nether.net> wrote:
This is both an issue over V6 and V4, eg:
Jareds-Mac-mini:~% traceroute puck traceroute to puck.nether.net (204.42.254.5), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.603 ms 0.418 ms 0.403 ms 2 173-167-0-110-michigan.hfc.comcastbusiness.net (173.167.0.110) 2.044 ms 2.019 ms 2.179 ms 3 96.120.40.141 (96.120.40.141) 17.399 ms 12.408 ms 9.639 ms 4 68.85.85.37 (68.85.85.37) 14.371 ms 8.378 ms 15.355 ms 5 te-0-8-0-6-ar02.pontiac.mi.michigan.comcast.net (68.87.191.153) 14.025 ms te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net (69.139.255.69) 14.749 ms 18.706 ms 6 be-33668-cr02.350ecermak.il.ibone.comcast.net (68.86.90.45) 21.955 ms 20.456 ms 19.259 ms 7 he-0-16-0-0-pe03.350ecermak.il.ibone.comcast.net (68.86.88.146) 18.333 ms 17.245 ms 16.952 ms ^C
Jareds-Mac-mini:~% traceroute6 puck traceroute6 to puck.nether.net (2001:418:3f4::5) from 2601:401:3:6a00:ad42:ce75:8a0:c370, 64 hops max, 12 byte packets 1 2601:401:3:6a00:20f:f7ff:feab:1ec0 1.135 ms 0.965 ms 0.948 ms 2 2601:401:3:6a00:4694:fcff:fecd:64bc 3.710 ms 3.544 ms 21.221 ms 3 2001:558:6007:24::1 30.051 ms 10.909 ms 10.868 ms 4 te8-2-ur02.wannarbor.mi.michigan.comcast.net 10.664 ms 10.451 ms 10.570 ms 5 xe-11-1-0-0-sur01.rochestrhlls.mi.michigan.comcast.net 14.826 ms te-0-8-0-5-ar02.taylor.mi.michigan.comcast.net 13.890 ms 13.179 ms 6 te-0-7-0-13-ar01.pontiac.mi.michigan.comcast.net 18.917 ms 15.503 ms te-0-8-0-11-ar01.pontiac.mi.michigan.comcast.net 13.686 ms 7 be-33668-cr01.350ecermak.il.ibone.comcast.net 22.316 ms 22.014 ms 28.086 ms 8 hu-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net 20.933 ms 20.740 ms 20.831 ms ^C
- Jared
On Tue, Nov 17, 2015 at 10:02:58AM -0700, John Neiberger wrote:
Can you give me some more details please? I'll take a look.
Thanks, John
On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
And by "partial" I mean that it was very sick, but not sick enough to trigger a switchover to the backup RSP. That had to be done manually. John On Tue, Nov 17, 2015 at 12:15 PM, John Neiberger <jneiberger@gmail.com> wrote:
Thanks, all. Our side should be resolved now. Had a combination of a linecard fabric failure and a partial RSP failure. We're back in working shape and BGP from our core to that edge router is back up. Should be safe for peers to turn sessions back up.
John
On Tue, Nov 17, 2015 at 10:15 AM, Jared Mauch <jared@puck.nether.net> wrote:
This is both an issue over V6 and V4, eg:
Jareds-Mac-mini:~% traceroute puck traceroute to puck.nether.net (204.42.254.5), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.603 ms 0.418 ms 0.403 ms 2 173-167-0-110-michigan.hfc.comcastbusiness.net (173.167.0.110) 2.044 ms 2.019 ms 2.179 ms 3 96.120.40.141 (96.120.40.141) 17.399 ms 12.408 ms 9.639 ms 4 68.85.85.37 (68.85.85.37) 14.371 ms 8.378 ms 15.355 ms 5 te-0-8-0-6-ar02.pontiac.mi.michigan.comcast.net (68.87.191.153) 14.025 ms te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net (69.139.255.69) 14.749 ms 18.706 ms 6 be-33668-cr02.350ecermak.il.ibone.comcast.net (68.86.90.45) 21.955 ms 20.456 ms 19.259 ms 7 he-0-16-0-0-pe03.350ecermak.il.ibone.comcast.net (68.86.88.146) 18.333 ms 17.245 ms 16.952 ms ^C
Jareds-Mac-mini:~% traceroute6 puck traceroute6 to puck.nether.net (2001:418:3f4::5) from 2601:401:3:6a00:ad42:ce75:8a0:c370, 64 hops max, 12 byte packets 1 2601:401:3:6a00:20f:f7ff:feab:1ec0 1.135 ms 0.965 ms 0.948 ms 2 2601:401:3:6a00:4694:fcff:fecd:64bc 3.710 ms 3.544 ms 21.221 ms 3 2001:558:6007:24::1 30.051 ms 10.909 ms 10.868 ms 4 te8-2-ur02.wannarbor.mi.michigan.comcast.net 10.664 ms 10.451 ms 10.570 ms 5 xe-11-1-0-0-sur01.rochestrhlls.mi.michigan.comcast.net 14.826 ms te-0-8-0-5-ar02.taylor.mi.michigan.comcast.net 13.890 ms 13.179 ms 6 te-0-7-0-13-ar01.pontiac.mi.michigan.comcast.net 18.917 ms 15.503 ms te-0-8-0-11-ar01.pontiac.mi.michigan.comcast.net 13.686 ms 7 be-33668-cr01.350ecermak.il.ibone.comcast.net 22.316 ms 22.014 ms 28.086 ms 8 hu-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net 20.933 ms 20.740 ms 20.831 ms ^C
- Jared
On Tue, Nov 17, 2015 at 10:02:58AM -0700, John Neiberger wrote:
Can you give me some more details please? I'll take a look.
Thanks, John
On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
May have spoken too soon. Something is still apparently sick, so we've taken the router back out of routing for now. John On Tue, Nov 17, 2015 at 12:17 PM, John Neiberger <jneiberger@gmail.com> wrote:
And by "partial" I mean that it was very sick, but not sick enough to trigger a switchover to the backup RSP. That had to be done manually.
John
On Tue, Nov 17, 2015 at 12:15 PM, John Neiberger <jneiberger@gmail.com> wrote:
Thanks, all. Our side should be resolved now. Had a combination of a linecard fabric failure and a partial RSP failure. We're back in working shape and BGP from our core to that edge router is back up. Should be safe for peers to turn sessions back up.
John
On Tue, Nov 17, 2015 at 10:15 AM, Jared Mauch <jared@puck.nether.net> wrote:
This is both an issue over V6 and V4, eg:
Jareds-Mac-mini:~% traceroute puck traceroute to puck.nether.net (204.42.254.5), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.603 ms 0.418 ms 0.403 ms 2 173-167-0-110-michigan.hfc.comcastbusiness.net (173.167.0.110) 2.044 ms 2.019 ms 2.179 ms 3 96.120.40.141 (96.120.40.141) 17.399 ms 12.408 ms 9.639 ms 4 68.85.85.37 (68.85.85.37) 14.371 ms 8.378 ms 15.355 ms 5 te-0-8-0-6-ar02.pontiac.mi.michigan.comcast.net (68.87.191.153) 14.025 ms te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net (69.139.255.69) 14.749 ms 18.706 ms 6 be-33668-cr02.350ecermak.il.ibone.comcast.net (68.86.90.45) 21.955 ms 20.456 ms 19.259 ms 7 he-0-16-0-0-pe03.350ecermak.il.ibone.comcast.net (68.86.88.146) 18.333 ms 17.245 ms 16.952 ms ^C
Jareds-Mac-mini:~% traceroute6 puck traceroute6 to puck.nether.net (2001:418:3f4::5) from 2601:401:3:6a00:ad42:ce75:8a0:c370, 64 hops max, 12 byte packets 1 2601:401:3:6a00:20f:f7ff:feab:1ec0 1.135 ms 0.965 ms 0.948 ms 2 2601:401:3:6a00:4694:fcff:fecd:64bc 3.710 ms 3.544 ms 21.221 ms 3 2001:558:6007:24::1 30.051 ms 10.909 ms 10.868 ms 4 te8-2-ur02.wannarbor.mi.michigan.comcast.net 10.664 ms 10.451 ms 10.570 ms 5 xe-11-1-0-0-sur01.rochestrhlls.mi.michigan.comcast.net 14.826 ms te-0-8-0-5-ar02.taylor.mi.michigan.comcast.net 13.890 ms 13.179 ms 6 te-0-7-0-13-ar01.pontiac.mi.michigan.comcast.net 18.917 ms 15.503 ms te-0-8-0-11-ar01.pontiac.mi.michigan.comcast.net 13.686 ms 7 be-33668-cr01.350ecermak.il.ibone.comcast.net 22.316 ms 22.014 ms 28.086 ms 8 hu-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net 20.933 ms 20.740 ms 20.831 ms ^C
- Jared
On Tue, Nov 17, 2015 at 10:02:58AM -0700, John Neiberger wrote:
Can you give me some more details please? I'll take a look.
Thanks, John
On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Okay, we should be good to go. For real this time. Had some lingering fabric-related issues to clear up. Everything looks good now. Let me know if anyone sees any more problems through that router. Thanks, John On Tue, Nov 17, 2015 at 12:37 PM, John Neiberger <jneiberger@gmail.com> wrote:
May have spoken too soon. Something is still apparently sick, so we've taken the router back out of routing for now.
John
On Tue, Nov 17, 2015 at 12:17 PM, John Neiberger <jneiberger@gmail.com> wrote:
And by "partial" I mean that it was very sick, but not sick enough to trigger a switchover to the backup RSP. That had to be done manually.
John
On Tue, Nov 17, 2015 at 12:15 PM, John Neiberger <jneiberger@gmail.com> wrote:
Thanks, all. Our side should be resolved now. Had a combination of a linecard fabric failure and a partial RSP failure. We're back in working shape and BGP from our core to that edge router is back up. Should be safe for peers to turn sessions back up.
John
On Tue, Nov 17, 2015 at 10:15 AM, Jared Mauch <jared@puck.nether.net> wrote:
This is both an issue over V6 and V4, eg:
Jareds-Mac-mini:~% traceroute puck traceroute to puck.nether.net (204.42.254.5), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.603 ms 0.418 ms 0.403 ms 2 173-167-0-110-michigan.hfc.comcastbusiness.net (173.167.0.110) 2.044 ms 2.019 ms 2.179 ms 3 96.120.40.141 (96.120.40.141) 17.399 ms 12.408 ms 9.639 ms 4 68.85.85.37 (68.85.85.37) 14.371 ms 8.378 ms 15.355 ms 5 te-0-8-0-6-ar02.pontiac.mi.michigan.comcast.net (68.87.191.153) 14.025 ms te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net (69.139.255.69) 14.749 ms 18.706 ms 6 be-33668-cr02.350ecermak.il.ibone.comcast.net (68.86.90.45) 21.955 ms 20.456 ms 19.259 ms 7 he-0-16-0-0-pe03.350ecermak.il.ibone.comcast.net (68.86.88.146) 18.333 ms 17.245 ms 16.952 ms ^C
Jareds-Mac-mini:~% traceroute6 puck traceroute6 to puck.nether.net (2001:418:3f4::5) from 2601:401:3:6a00:ad42:ce75:8a0:c370, 64 hops max, 12 byte packets 1 2601:401:3:6a00:20f:f7ff:feab:1ec0 1.135 ms 0.965 ms 0.948 ms 2 2601:401:3:6a00:4694:fcff:fecd:64bc 3.710 ms 3.544 ms 21.221 ms 3 2001:558:6007:24::1 30.051 ms 10.909 ms 10.868 ms 4 te8-2-ur02.wannarbor.mi.michigan.comcast.net 10.664 ms 10.451 ms 10.570 ms 5 xe-11-1-0-0-sur01.rochestrhlls.mi.michigan.comcast.net 14.826 ms te-0-8-0-5-ar02.taylor.mi.michigan.comcast.net 13.890 ms 13.179 ms 6 te-0-7-0-13-ar01.pontiac.mi.michigan.comcast.net 18.917 ms 15.503 ms te-0-8-0-11-ar01.pontiac.mi.michigan.comcast.net 13.686 ms 7 be-33668-cr01.350ecermak.il.ibone.comcast.net 22.316 ms 22.014 ms 28.086 ms 8 hu-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net 20.933 ms 20.740 ms 20.831 ms ^C
- Jared
On Tue, Nov 17, 2015 at 10:02:58AM -0700, John Neiberger wrote:
Can you give me some more details please? I'll take a look.
Thanks, John
On Tue, Nov 17, 2015 at 10:00 AM, Jared Mauch via Outages <outages@outages.org> wrote:
Anyone know what is going on here? It seems to have started around 1600 utc and is still ongoing.
- Jared
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
participants (6)
-
James Cornman -
Jared Mauch -
John Neiberger -
Joseph Jackson -
Kevin Reedy -
Kris Amy