- mice-discuss - lists.micemn.net

Re: 2025-01-20 MICE Maintenance - Route Server 2

by Brady Kittel

As a server guy I'll mention two things. 1) If we're using SM fiber with LR optics I've seen issues with LR optics burning out on the receive side when used with short distances to servers. Depends on the optic it seems but it definitely happens. Fix for us was just to either use SR optics with mm fiber or use a DAC. Definitely avoid the use of active mode DACs too. I've seen all sorts of problems with compatibility and even causing OS crashes. Never had problems with hardware compatible passive mode DACs in my experience across our fleet of 350 servers. On Sun, Jan 19, 2025, 7:50 PM Richard Laager <rlaager(a)micemn.net> wrote: > MICE physical server 2 (and thus by extension route server 2) is again > having errors on its peering interface. We will be performing maintenance > tomorrow to address this. Since this only affects one of the two route > servers, participants should not be impacted. > > > Details: > > Sometime tomorrow (exact time depending on day job schedules), Jeremy and > I will: > > 1. Apply the usual security updates to VMs and the host, since the host is > going to be rebooted anyway. > > 2. Convert server 2's port to a LAG. This will make future changes easier, > especially if this error problem continues. > > This will involve a reboot of the server. The reboot is "necessary" > because Linux's netplan does not remove VLAN configuration when changes are > made (only adds it). Without removing the old > direct-on-the-physical-interface VLAN config, we could (would?) create a > loop. You may recall that I created a loop that blew up the exchange in > more-or-less that exact way when setting up the servers originally. > > While I could remove the VLAN configuration manually, in this case, it's > easier and safer to simply reboot. That also ensures our running > configuration is fully consistent with the configuration files. > > 3. Replace the optic, also moving to the other port on the NIC. > > > The underlying failure manifests as a decrease in optical transmit power > (i.e. power received at the switch) over time. We have replaced the optic > previously, which fixes it, but then it fails again after a while. We are > open to suggestions about why this might be occurring. > > One theory is that this is due to heat. We are going to try the second > port in case that makes a difference. We are also considering switching to > a direct attach cable, as perhaps that would produce less heat. > > -- > Richard Laager > Chief Manager, Director > Midwest Internet Cooperative Exchange LLC > > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net >

Jan. 23, 2025

Re: MICE 400G Switch

by Mike Horwath

On Thu, Jan 23, 2025 at 09:26:48AM -0600, Jeremy Lumby wrote: > Here are some pics: Thanks! That's some chonk! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Jan. 23, 2025

RE: MICE 400G Switch

by Jeremy Lumby

Here are some pics: https://www.mnvoip.com/MICE400G/1.jpg https://www.mnvoip.com/MICE400G/2.jpg https://www.mnvoip.com/MICE400G/3.jpg https://www.mnvoip.com/MICE400G/4.jpg https://www.mnvoip.com/MICE400G/5.jpg https://www.mnvoip.com/MICE400G/6.jpg https://www.mnvoip.com/MICE400G/7.jpg https://www.mnvoip.com/MICE400G/8.jpg https://www.mnvoip.com/MICE400G/9.jpg -----Original Message----- From: Mike Horwath <drechsau(a)geeks.org> Sent: Thursday, January 23, 2025 7:37 AM To: MICE Discuss <mice-discuss(a)lists.micemn.net> Subject: Re: MICE 400G Switch On Thu, Jan 23, 2025 at 12:02:13AM -0600, Richard Laager wrote: > The 400G switch has arrived. whoop! > Jeremy racked the switch. It's a big one! Pics!? -- Mike Horwath, reachable via drechsau(a)Geeks.ORG _______________________________________________ mice-discuss mailing list -- mice-discuss(a)lists.micemn.net To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

Jan. 23, 2025

Re: MICE 400G Switch

by Mike Horwath

On Thu, Jan 23, 2025 at 12:02:13AM -0600, Richard Laager wrote: > The 400G switch has arrived. whoop! > Jeremy racked the switch. It's a big one! Pics!? -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Jan. 23, 2025

MICE 400G Switch

by Richard Laager

The 400G switch has arrived. Jeremy racked the switch. It's a big one! We don't have a firm go-live date at this point, but it will be soon. If you are interested in 400G ports, the Order Form has been updated: https://micemn.net/files/MICE%20Order%20Form.docx (I've just sent this to mice-discuss so far. I'm thinking we'll send something to mice-announce once the switch is live. But if people think I should be sending it there now, I'm open to the suggestion.) -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

Jan. 23, 2025

2025-01-20 MICE Maintenance - Route Server 2

by Richard Laager

MICE physical server 2 (and thus by extension route server 2) is again having errors on its peering interface. We will be performing maintenance tomorrow to address this. Since this only affects one of the two route servers, participants should not be impacted. Details: Sometime tomorrow (exact time depending on day job schedules), Jeremy and I will: 1. Apply the usual security updates to VMs and the host, since the host is going to be rebooted anyway. 2. Convert server 2's port to a LAG. This will make future changes easier, especially if this error problem continues. This will involve a reboot of the server. The reboot is "necessary" because Linux's netplan does not remove VLAN configuration when changes are made (only adds it). Without removing the old direct-on-the-physical-interface VLAN config, we could (would?) create a loop. You may recall that I created a loop that blew up the exchange in more-or-less that exact way when setting up the servers originally. While I could remove the VLAN configuration manually, in this case, it's easier and safer to simply reboot. That also ensures our running configuration is fully consistent with the configuration files. 3. Replace the optic, also moving to the other port on the NIC. The underlying failure manifests as a decrease in optical transmit power (i.e. power received at the switch) over time. We have replaced the optic previously, which fixes it, but then it fails again after a while. We are open to suggestions about why this might be occurring. One theory is that this is due to heat. We are going to try the second port in case that makes a difference. We are also considering switching to a direct attach cable, as perhaps that would produce less heat. -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

Jan. 20, 2025

RE: [MICE-DISCUSS] MICE Server Updates

by nanog＠jima.us

Cameron (or others), A cohort reached out to ask me... Does anyone know when the IPv6 address for micemn.net stopped responding? I foolishly didn't check after the migration; I see the v6 address is announced by the same ASN as the (working) v4 address, but attempts to trace die off after the penultimate hop (versus the v4 path). Happy Eyeballs would generally keep the site loading in browsers, assuming one has native IPv4/464XLAT, but it seems like a non-ideal state of affairs. Thank you! - Jima > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Cameron > Skappel > Sent: Monday, November 25, 2024 13:19 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] MICE Server Updates > > The first round of updates, which included Route Server 1, has been > completed. > > On 11/22/24 11:45, Cameron Skappel wrote: > > I plan to update the MICE servers and firewalls Monday November 25th > > at 13:00 Central and Tuesday November 26th at 14:30 Central. I will do > > one route server per day. > > > -- > Cameron Skappel > 218-436-5226 > Wikstrom Telephone Company

Dec. 18, 2024

Re: [MICE-DISCUSS] ipHouse MICE Disconnect

by John Unger

Thank you Doug and the IPhouse folks that helped, you will be missed!! Regards, John Unger Vaultas On Mon, Dec 2, 2024 at 2:41 PM Jay Hanke via mice-discuss < mice-discuss(a)lists.micemn.net> wrote: > ipHouse is disconnecting from MICE. > > ipHouse is an OG member of MICE and has been a huge supporter over the > years contributing to just about every aspect of the IX. They have > contributed everything from donating equipment, transit, mailing list > services and TONS of manual Bird config over the years. > > In particular, Doug McIntyre has contributed a huge amount of effort > when MICE was just a pinkie. It would have been much more difficult > without his help. > > Thanks! > > Jay > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net > -- John Unger President 612.325.2909 Vaultas | vaultas.com Connecting you to the Ecosystem

Dec. 18, 2024

Please welcome Mid-Rivers to MICE!

by Jeremy Lumby

Name: Mid-Rivers Telephone Cooperative Switch: 511 Core (7504R 10G/100G) Port: E 4/13 and E4/14 added to portchannel 39 ASN: 11961 IPv4: This is a port upgrade to a total of 4x10G. All IP info remains the same. IPv6: Peering Contact: nse(a)midrivers.coop Route Servers: Yes Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

Dec. 13, 2024

[MICE-DISCUSS] Re: ipHouse MICE Disconnect

by Joe Unger

Thank you to ipHouse for all that you have done over the years. The MICE community truly appreciates your help and support. You guys will be missed. On Mon, Dec 2, 2024 at 3:56 PM Mike Horwath <drechsau(a)geeks.org> wrote: > On Mon, Dec 02, 2024 at 02:38:21PM -0600, Jay Hanke via mice-discuss wrote: > > In particular, Doug McIntyre has contributed a huge amount of effort > > when MICE was just a pinkie. It would have been much more difficult > > without his help. > > Doug deserves so much thanks. He rocks but I've known that since the > late 1980s.. :) > > -- > Mike Horwath, reachable via drechsau(a)Geeks.ORG > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net > -- Joe Unger 612.709.8699 joe(a)vaultas.com Vaultas | *Connecting you to the Ecosystem* vaultas.com

Dec. 2, 2024

[MICE-DISCUSS] Re: ipHouse MICE Disconnect

by Mike Horwath

On Mon, Dec 02, 2024 at 02:38:21PM -0600, Jay Hanke via mice-discuss wrote: > In particular, Doug McIntyre has contributed a huge amount of effort > when MICE was just a pinkie. It would have been much more difficult > without his help. Doug deserves so much thanks. He rocks but I've known that since the late 1980s.. :) -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Dec. 2, 2024

[MICE-DISCUSS] ipHouse MICE Disconnect

by Jay Hanke

ipHouse is disconnecting from MICE. ipHouse is an OG member of MICE and has been a huge supporter over the years contributing to just about every aspect of the IX. They have contributed everything from donating equipment, transit, mailing list services and TONS of manual Bird config over the years. In particular, Doug McIntyre has contributed a huge amount of effort when MICE was just a pinkie. It would have been much more difficult without his help. Thanks! Jay

Dec. 2, 2024

[MICE-DISCUSS] Please welcome Park Region to MICE!

by Jeremy Lumby

Name: Park Region Switch: Fiber Minnesota Port: Hu1/0/19 ASN: 25637 IPv4: This is a port upgrade to 100G. All IP info remains the same. IPv6: Peering Contact: noc(a)parkregion.com Route Servers: Yes Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

Nov. 27, 2024

[MICE-DISCUSS] MICE Server Updates

by Cameron Skappel

The second round of updates, which included Route Server 2, has been completed. -- Cameron Skappel 218-436-5226 Wikstrom Telephone Company

Nov. 26, 2024

[MICE-DISCUSS] Re: MICE Mailing Lists

by Mike Horwath

favorite header: X-No-Archive: yes I miss OG UseNet -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Nov. 25, 2024

[MICE-DISCUSS] Re: MICE Mailing Lists

by Mike Horwath

On Mon, Nov 25, 2024 at 02:12:29PM -0600, Richard Laager wrote: > This is a test of the new mice-discuss mailing list. no fail! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Nov. 25, 2024

[MICE-DISCUSS] Re: MICE Mailing Lists

by Nevin Lyne

First post came through nicely :) -Nevin -- -- Nevin Lyne -- Founder and Director of Technology -- Arcustech, LLC - https://www.arcustech.com/ On Mon, Nov 25, 2024, at 2:12 PM, Richard Laager wrote: > This is a test of the new mice-discuss mailing list. > > On 2024-11-25 13:56, Richard Laager wrote: >> MICE is migrating mailing lists to new infrastructure. >> >> ipHouse is winding down / spinning off certain operations. I want to thank ipHouse for their support of MICE over many years. In particular, I want to thank Doug McIntyre for years of work. >> >> The web interface will be available at https://lists.micemn.net and the lists will be the same names but at the new domain, i.e. mice-discuss(a)lists.micemn.net and mice-announce(a)lists.micemn.net. >> >> I am transferring all subscriptions. You will shortly receive an invitation message. In theory, no action is necessary, and hopefully this all just works. :) >> >> For those of you with digest subscriptions, I will manually change your setting to digest after importing your address. So give me a few minutes. >> >> The external provider will be importing the archives shortly. Again, hopefully that works. It will not include this message, since this is after I exported the archives. >> >> Also, the MICE board now have personal @micemn.net emails: >> >> Anthony Anderberg <ant(a)micemn.net> >> Reid Fishler <rfishler(a)micemn.net> >> Richard Laager <rlaager(a)micemn.net> >> > -- > Richard Laager > Chief Manager, Director > Midwest Internet Cooperative Exchange LLC > _______________________________________________ > mice-discuss mailing list -- mice-discuss(a)lists.micemn.net > To unsubscribe send an email to mice-discuss-leave(a)lists.micemn.net

Nov. 25, 2024

[MICE-DISCUSS] Re: MICE Mailing Lists

by Richard Laager

This is a test of the new mice-discuss mailing list. On 2024-11-25 13:56, Richard Laager wrote: > MICE is migrating mailing lists to new infrastructure. > > ipHouse is winding down / spinning off certain operations. I want to > thank ipHouse for their support of MICE over many years. In > particular, I want to thank Doug McIntyre for years of work. > > The web interface will be available at https://lists.micemn.net and > the lists will be the same names but at the new domain, i.e. > mice-discuss(a)lists.micemn.net and mice-announce(a)lists.micemn.net. > > I am transferring all subscriptions. You will shortly receive an > invitation message. In theory, no action is necessary, and hopefully > this all just works. :) > > For those of you with digest subscriptions, I will manually change > your setting to digest after importing your address. So give me a few > minutes. > > The external provider will be importing the archives shortly. Again, > hopefully that works. It will not include this message, since this is > after I exported the archives. > > Also, the MICE board now have personal @micemn.net emails: > > Anthony Anderberg <ant(a)micemn.net> > Reid Fishler <rfishler(a)micemn.net> > Richard Laager <rlaager(a)micemn.net> > -- Richard Laager Chief Manager, Director Midwest Internet Cooperative Exchange LLC

Nov. 25, 2024

MICE Server Updates

by Cameron Skappel

I plan to update the MICE servers and firewalls Monday November 25th at 13:00 Central and Tuesday November 26th at 14:30 Central. I will do one route server per day. -- Cameron

Nov. 22, 2024

Re: [EXTERNAL] - Re: [MICE-DISCUSS] netflix/tyson

by Ben Wiechman

Our levels of network traffic were lower than a typical Thursday Night Football event so the overall bandwidth utilization was not a factor. We had similar reports from our employees that the experience was hit and miss on many different service providers: Arvig, various employees are on other service providers, and mobile. One employee reported a better experience connecting to a VPN that terminated in TX than using any local connections. We also noted that while the fight would not load, other Netflix content tended to load and playback without issues or the same delays. On most tries I was unable to get video content for the fight to play at all, but attempts to then load any other Netflix content popped up in what I was describe as fairly typical response times. Traffic to our caches initially spiked, then crashed to nothing, then recovered at relatively heavy levels. We weren't seeing evidence of network congestion. My opinion is that, beyond that initial surge of traffic to the caches, the issue was less network or cache capacity than it was an ability of the client to access the resources that redirected it to the correct CDN for the content. The only possible workaround we discussed was shutting down the cache or access to the cache, but that was not a direction we chose to go down. Untested and not ideal given that there were no guarantees that Netflix would redirect subscribers to another CDN gracefully, or that another CDN would have any more additional capacity. Keep in mind that Netflix will be hosting a couple of Christmas NFL football games. A quick Google search suggests that typical Thanksgiving games run around 30M viewers, so half+ the load that this event generated, but still something to consider. Ben Wiechman Director of Network Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com On Mon, Nov 18, 2024 at 1:46 PM Joe Unger <joe(a)vaultas.com> wrote: > I was streaming at home from my Comcast/Xfinity coax connection , and had > a terrible experience for most of the last 3 fights to the point it was > completely unwatchable at times. I was texting with friends and family from > all over the midwest and everyone I spoke with experienced buffering, > freezing and outages. From the small amount of data I have it appears the > cable providers suffered the most (Comcast, Spectrum & Cox). > > I haven't seen or heard of any definitive choke points as of yet. I > thought it might have been a perfect storm of; Netflix cloud infrastructure > issues and network congestion issues. > > I saw reports of 60 million+ users streaming the fight. > > It's clear things broke, and now there are elements to fix and make > better. > > On Fri, Nov 15, 2024 at 11:02 PM Miles McCredie <Miles.McCredie(a)midco.com> > wrote: > >> If there are folks interested in collaborating on a post-mortem, count me >> in. >> >> >> >> We’re getting complaints. Haven’t identified any obvious on-net issues >> (yet?). >> >> >> >> I’m actually remote and streaming on Comcast which has been mostly OK >> with a couple “stream not available” errors. >> >> >> >> Roughly 3x normal Netflix peaks. >> >> >> >> >> >> >> >> *Miles McCredie * >> Principal Network Engineer II-Core IP >> >> Office: 6052755192 >> Miles.McCredie(a)midco.com >> >> *Midco.com* >> >> Let's go beyond. >> >> *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Richard >> Laager >> *Sent:* Friday, November 15, 2024 10:31 PM >> *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> *Subject:* [EXTERNAL] - Re: [MICE-DISCUSS] netflix/tyson >> >> >> >> *CAUTION:* This email originated from outside of *MIDCO*. >> *Do not click links or open attachments unless you recognize the sender >> and know the content is safe.* >> >> I'm seeing issues depending on which Netflix cache I hit. It fails to >> show the live event when the client picks mine (which I know to be serving >> large amounts of data, but well within its capacity, and serves other >> content just fine), or that of one of my upstreams. But other caches work >> fine. >> >> -- >> >> Richard >> >> >> ------------------------------ >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> >> ------------------------------ >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > > > -- > Joe Unger > 612.709.8699 > joe(a)vaultas.com > Vaultas | *Connecting you to the Ecosystem* > vaultas.com > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Nov. 18, 2024

Re: [EXTERNAL] - Re: [MICE-DISCUSS] netflix/tyson

by Joe Unger

I was streaming at home from my Comcast/Xfinity coax connection , and had a terrible experience for most of the last 3 fights to the point it was completely unwatchable at times. I was texting with friends and family from all over the midwest and everyone I spoke with experienced buffering, freezing and outages. From the small amount of data I have it appears the cable providers suffered the most (Comcast, Spectrum & Cox). I haven't seen or heard of any definitive choke points as of yet. I thought it might have been a perfect storm of; Netflix cloud infrastructure issues and network congestion issues. I saw reports of 60 million+ users streaming the fight. It's clear things broke, and now there are elements to fix and make better. On Fri, Nov 15, 2024 at 11:02 PM Miles McCredie <Miles.McCredie(a)midco.com> wrote: > If there are folks interested in collaborating on a post-mortem, count me > in. > > > > We’re getting complaints. Haven’t identified any obvious on-net issues > (yet?). > > > > I’m actually remote and streaming on Comcast which has been mostly OK with > a couple “stream not available” errors. > > > > Roughly 3x normal Netflix peaks. > > > > > > > > *Miles McCredie * > Principal Network Engineer II-Core IP > > Office: 6052755192 > Miles.McCredie(a)midco.com > > *Midco.com* > > Let's go beyond. > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Richard > Laager > *Sent:* Friday, November 15, 2024 10:31 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [EXTERNAL] - Re: [MICE-DISCUSS] netflix/tyson > > > > *CAUTION:* This email originated from outside of *MIDCO*. > *Do not click links or open attachments unless you recognize the sender > and know the content is safe.* > > I'm seeing issues depending on which Netflix cache I hit. It fails to show > the live event when the client picks mine (which I know to be serving large > amounts of data, but well within its capacity, and serves other content > just fine), or that of one of my upstreams. But other caches work fine. > > -- > > Richard > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Joe Unger 612.709.8699 joe(a)vaultas.com Vaultas | *Connecting you to the Ecosystem* vaultas.com

Nov. 18, 2024

Re: [EXTERNAL] - Re: [MICE-DISCUSS] netflix/tyson

by Miles McCredie

If there are folks interested in collaborating on a post-mortem, count me in. We're getting complaints. Haven't identified any obvious on-net issues (yet?). I'm actually remote and streaming on Comcast which has been mostly OK with a couple "stream not available" errors. Roughly 3x normal Netflix peaks. [http://images.midcocomm.com/ES_MidcoLogo.png] Miles McCredie Principal Network Engineer II-Core IP Office: 6052755192 Miles.McCredie(a)midco.com Midco.com Let's go beyond. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Friday, November 15, 2024 10:31 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [EXTERNAL] - Re: [MICE-DISCUSS] netflix/tyson CAUTION: This email originated from outside of MIDCO. Do not click links or open attachments unless you recognize the sender and know the content is safe. I'm seeing issues depending on which Netflix cache I hit. It fails to show the live event when the client picks mine (which I know to be serving large amounts of data, but well within its capacity, and serves other content just fine), or that of one of my upstreams. But other caches work fine. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Nov. 16, 2024

Re: netflix/tyson

by Richard Laager

I'm seeing issues depending on which Netflix cache I hit. It fails to show the live event when the client picks mine (which I know to be serving large amounts of data, but well within its capacity, and serves other content just fine), or that of one of my upstreams. But other caches work fine. -- Richard

Nov. 16, 2024

Re: netflix/tyson

by Darin Steffl

Yes, seeing issues. Twitter is full of reports of buffering and low quality. Downdetector showing lots of reports too. On Fri, Nov 15, 2024, 9:51 PM Jeff Wilde <jeff.wilde(a)parkregion.com> wrote: > Ty. it works through Verizon wireless for me but not otherwise is why I > was wondering. > > > > > > [image: A picture containing icon Description automatically generated] > > Jeff Wilde · Network Engineer · Park Region > > Office 218.826.6161 · Direct 218.826.8330 · Fax 218.826.6298 > > > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Justin > Huffman > *Sent:* Friday, November 15, 2024 9:49 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] netflix/tyson > > > > It's Netflix. They didn't prepare for this. > > > > Thanks, > > > > Justin > > Long Lines Broadband > ------------------------------ > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Jeff > Wilde <jeff.wilde(a)PARKREGION.COM> > *Sent:* Friday, November 15, 2024 9:48:29 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > *Subject:* [MICE-DISCUSS] netflix/tyson > > > > WARNING!! This message originated from an *External Source*. Please use > proper judgment and caution when opening attachments, clicking links, or > responding to this email. > > Anyone having issues with it streaming. I think its just the fight not > Netflix. I can view other stuff. > > > > > > [image: A picture containing icon Description automatically generated] > > Jeff Wilde · Network Engineer · Park Region > > Office 218.826.6161 · Direct 218.826.8330 · Fax 218.826.6298 > > > > > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Nov. 16, 2024

Re: netflix/tyson

by Jeff Wilde

Ty. it works through Verizon wireless for me but not otherwise is why I was wondering. [A picture containing icon Description automatically generated] Jeff Wilde * Network Engineer * Park Region Office 218.826.6161 * Direct 218.826.8330 * Fax 218.826.6298 From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Justin Huffman Sent: Friday, November 15, 2024 9:49 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] netflix/tyson It's Netflix. They didn't prepare for this. Thanks, Justin Long Lines Broadband ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> on behalf of Jeff Wilde <jeff.wilde(a)PARKREGION.COM<mailto:jeff.wilde@PARKREGION.COM>> Sent: Friday, November 15, 2024 9:48:29 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Subject: [MICE-DISCUSS] netflix/tyson WARNING!! This message originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Anyone having issues with it streaming. I think its just the fight not Netflix. I can view other stuff. [A picture containing icon Description automatically generated] Jeff Wilde * Network Engineer * Park Region Office 218.826.6161 * Direct 218.826.8330 * Fax 218.826.6298 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Nov. 16, 2024