We rent the gigabit gateway from comcast. Xb6 is the model. It has poor wifi performance. The antennas on it have poor range. The living room is next to the bedroom where the xb6 sits but all wireless devices in the living room suffer from packet loss and ping spikes to the gateway itself. This causes frequent in game disconnects because of continuous packet loss and ping spikes. This indicates very poor antenna system on the xb6. A ping plot shows dozens to hundreds of packet losses when pinging the gateway once a second. Rather than 1ms pings it's more like 7ms pings and lots of 70-200ms ping spikes. I either need a new gateway to replace the xb6 or a new dedicated router..

Thought this was kinda neat.quote:"I will tell you that we are actively deploying the virtualized CMTS platform while the vast majority of our subscribers are still on the traditional CTMTS platforms," he said. "As for the challenges, I will start with a couple of things. We are literally writing the book as we go, okay? I can't pick up the phone, and call Cisco's John Chapman, and say 'Hey, what have you guys done?' because they haven't done it either. And so the challenge is how do we learn how to build and how do we learn how to operate at the same time?https://www.fiercetelecom.com/telecom/comcast-execs-lessons-learned-from-deploying-vcmts

Hi All, Curious if anyone has noticed significant discrepancies between what Comcast/Xfinity thinks they've used (bandwidth wise) and what your router reports? I'm using Unifi gear (USG), and DPI is telling me this month I've used 363GB of bandwidth. Comcast, on the other hand, says 504GB. This is a whopping 32.5% difference. Someone mentioned in the Ubiquiti forums that this could be due to traffic that comes in, but the router rejects (which Comcast would see as traffic, but the router wouldn't), but 141GB seems like a lot of errant/rogue traffic. I'm a little concerned, but I'm also pretty confident that if I call out Comcast on this, It's just going to fall on deaf ears ("Our system is right, your's is wrong"). Thoughts?

Just thought I would share a video from a recent fiber restoration drill that was done in Washington. It will you some insight into what goes on when a cut is detected, then identified, and repaired. https://www.youtube.com/watch?v=nq81eJ9T2d8&

Mod Note: This topic started as "XI Gigabit DOCSIS 3.1 - data cap with 3-year agreement?" It has become a general discussion of this deployment, hence the title change. uid://455626 If you actually have had this service installed, the stickied report topic is here. > https://www.dslreports.com/forum/r30960001-Speed-Report-DOCSIS-3-1-Gigabit-Service-Here If you report, please include info requested in the first post and keep that topic strictly on topic. Thanks, sortofageek The XI Gigabit DOCSIS 3.1 is now available in my area. I am tempted to sign up. Early reports said unlimited data with a 3-year agreement. The Comcast website says nothing but the typical disclaimer about the data usage plan. I don't want to sign a 3-year agreement for a plan with a data cap. Does anyone know if the XI Gigabit service is subject to the data usage nonsense? See additional discussion in these (now closed) topics > https://www.dslreports.com/forum/r31088308-Speed-Side-Discussion-About-Gigabit-Pro-earlier-Gigabit-Deployments https://www.dslreports.com/forum/r31338340-Speed-DOCSIS-3-1-Gigabit-Service-in-Colorado-Springs https://www.dslreports.com/forum/r31746972-Areas-still-waiting-for-D3-1-chime-in https://www.dslreports.com/forum/r31901914-Plan-Gigabit-Internet-finally-available-with-THEIR-modem

Hello. Brand new to Xfinity, and was installed yesterday. Everything seems fine, such as speed tests and whatnot, but yesterday, on the status center page, it said "issue detected", with a red circle, with an exclamation point in it. I clicked on troubleshooting, and it reset the modem, and maybe 10 minutes later, gave a message saying everything looked good on their end, but may be an issue with equipment. Person on chat couldn't find anything, and a call to tech support, the guy told me he wasn't sure, and because it's my own modem, they can't accesss it, but didn't think it was anything significant, as long as everything works fine. I was a little surprised the guy didn't replace the drop from my house to the pedestal, as it's probaly 30 years old, in conduit, and only about 20 feet from the house to the pedestal. It was cut off about 4 inches from the end of the conduit, and he put a barrel connnector on it, and then maybe a 2 foot piece that went into his box with the ground block and whatnot. I do ViaSat internet for a living, so I'm pretty knowledgeable with all this. Those connectors are not bullet proof, and am surprised he did that, right out of the conduit, and didn't replace the drop. They told me if they get a good signal, they don't normally replace it. I don't know their protocol, so I have to believe him. Anyway, just for fun, I'm posting my modem stats, just to see if anyone sees anything not within parameters, or if it all looks goods, because I simply don't know. Also curious what all this in the event log means, if anything at all. Especially since this isn't January, 2018. Thanks in advance!

Mod Note: Before reporting here, please read this post. Please keep this strictly on topic. Side discussion can be added here -> https://secure.dslreports.com/forum/r29686112-Signals-Side-Discussion-about-16-channel-Downstream-Bonding- uid://455626 It's time to start tracking Comcast/Xfinity areas that have 16 Downstream Channels. Please post the following: 1) State 2) City 3) **Provide a screen shot of your Modem's Status Page. States: Alabama Arizona Tucson, AZ 24 Ch. Arkansas Little Rock, AR 24 Ch. Sherwood, AR 24 Ch. California Anselmo, CA 24 Ch. Belmont, CA 24 Ch. http://www.dslreports.com/forum/r29744016- Berkeley, CA 24 Ch. Berkeley, CA 32 Ch. https://secure.dslreports.com/forum/r29770260- Cloverdale, CA 24 Ch. Concord, CA 24 Ch. Fairfield, CA Firebaugh, CA Folsom, CA 32 Ch. Fremont, CA 24 Ch. https://secure.dslreports.com/forum/r29935571- Hayward, CA 24 Ch. Hayward, CA 32 Ch. https://secure.dslreports.com/forum/r29778881- Livemore, CA 32 Ch. https://secure.dslreports.com/forum/r29901735- Mountain View, CA Mountain View, CA 24 Ch. Oakland, CA Oakland, CA 24 Ch. Pacifica, CA 24 Ch. Pacifica CA 32 Ch. Pleasanton, CA Pleasanton, CA 24Ch. Pleasonton, CA 32 Ch. Redwood Valley, CA Redwood Valley, CA 24 Ch. Redwood Valley, CA 32 Ch. Rohnert, CA Sacramento, CA Sacramento, CA 24 Ch. Sacramento, CA 32 Ch. https://secure.dslreports.com/forum/r29781255- San Francisco, CA 24 Ch. San Francisco, CA 32 Ch. https://secure.dslreports.com/forum/r29888646- San Jose, CA 24 Ch. https://www.dslreports.com/forum/r30045489- Santa Clara, CA 24 Ch Santa Cruz, CA Santa Cruz, CA 24 Ch. Santa Maria, CA 24 Ch. Santa Maria, CA 32 Ch. https://secure.dslreports.com/forum/r29870905- Santa Rosa, CA 24 Ch. Sonora, CA 24 Ch. Stockton, CA https://secure.dslreports.com/forum/r29760938- Vacaville, CA 24 Ch. https://www.dslreports.com/forum/r30012460- Yuba City, CA 32 Ch. Colorado Aurora, CO 24 Ch. Boulder, CO 24 Ch. Castle Rock, CO 24 Ch. Centennial, CO 24 Ch. Colorado Springs, CO Colorado Springs, CO 32 Ch. Denver, CO 24 Ch. Fort Collins, CO Fountain, CO 32 Ch. Littleton, CO Littleton, CO 24 Ch. https://secure.dslreports.com/forum/r29825334- Louisville, CO 24 Ch. Parker, CO Parker, CO 32 Ch. Rifle, CO 24 Ch. https://secure.dslreports.com/forum/r29803101- Connecticut Ansonia, CT Bloomfield, CT Branford, CT Branford, CT 24 Ch. Danbury, CT Hartford, CT 24 Ch. Salem, CT Waterbury, CT Delaware Bear, DE 24 Ch. Hockessin, DE Rehoboth Beach, DE Florida Boca Raton, FL Boca Raton, FL 24 Ch. Boynton Beach, FL 32 Ch. Crawfordville, FL 24 Ch. Davie, FL Fort Lauderdale, FL 24 Ch. Fort Lauderdale, FL 32 Ch. https://www.dslreports.com/forum/r30006137- Fort Myers, FL 24 Ch. Greenacres, FL Hialeah, FL 24 Ch. Lakewood, FL Jacksonville, FL 24 Ch. https://www.dslreports.com/forum/r30070003- Miami, FL Mount Dora, FL 24 Ch. Orange Park, FL 24 Ch. https://secure.dslreports.com/forum/r29840595- Orlando, FL 24 Ch. Panama City, FL Pembroke Pines, FL 24 Ch. Ponte Vedra Beach, FL 24 Ch. Sarasota, FL 24 Ch. Sarasota, FL 32 Ch. Wellington, FL West Kendall, FL 24 Ch. Georgia Alpharetta, GA https://secure.dslreports.com/forum/r29875398- Augusta, GA Braselton, GA Braselton, GA 24 Ch. Cumming, GA 24 Ch. https://secure.dslreports.com/forum/r29942073- Roswell, GA 32 Ch. Savannah, GA 24 Ch. Winder, GA 24 Ch. Illinois Antioch, IL 24 Ch. Aurora, IL 24 Ch. Cary, IL 24 Ch. Champagne, IL https://secure.dslreports.com/forum/r29883678- Chicago, IL Chicago, IL 24 Ch. https://secure.dslreports.com/forum/r29858409- Joliet, IL Mokena, IL 32 Ch. Morton Grove, IL 24 Ch. Morton Grove, IL 32 Ch. Mount Prospect, IL Oak Forest, IL Oak Forest, IL 24 Ch. River Forest, IL 24 Ch. Rockford, IL Sandwich, IL 24 Ch. Springfield, IL 24 Ch. Streamwood, IL 24 Ch. https://secure.dslreports.com/forum/r29780794- Wilmette, IL Woodstock, IL 24 Ch. Woodstock, IL 32 Ch. Indiana https://secure.dslreports.com/forum/r29941668- Goshen, IN 32 Ch. Greenwood, IN Indianapolis, IN 24 Ch. Michigan City, IN 24 Ch. Muncie, IN Muncie, IN 24 Ch. South Bend, IN 24 Ch. http://www.dslreports.com/forum/r30019152- Kansas Olathe, KS Kentucky Fort Campbell, KY 24 Ch. Louisiana Houma, LA Houma, LA 32 Ch. Monroe, LA Maine Brunswick, ME Brunswick, ME 24 Ch. Maryland Accokeek, MD Baltimore, MD Frederick, MD 24 Ch. Laurel, MD 24 Ch. Point Of Rocks, MD 24 Ch. Potomac, MD https://www.dslreports.com/forum/r30000109- Silver Spring, MD Massachusetts Billerica, MA 24 Ch. Concord, MA Concord, MA 24 Ch. Haverhill, MA Mashpee, MA 24 Ch. Northampton, MA Quincy, MA 24 Ch. Seekonk, MA https://secure.dslreports.com/forum/r29932637- Swansea, MA 24 Ch. Michigan Allen Park, MI Belleville, MI Belleville, MI 24 Ch. Canton, MI Detroit, MI Grand Rapids, MI 24 Ch. Grand Rapids, MI 32 Ch. Lansing, MI 24 Ch. Muskegon, MI Muskegon, MI 24 Ch. Muskegon, MI 32 Ch. Port Huron, MI 24 Ch. Roseville, MI Roseville, MI 32 Ch. Saline, MI 32 Ch. Sterling Heights, MI Sterling Heights, MI 24 Ch. https://secure.dslreports.com/forum/r29855762- Ypsilanti, MI 24 Ch. Ypsilanti, MI 32 Ch. Minnesota Bloomington, MN 32 Ch. Brooklyn Center, MN 24 Ch. Brooklyn Center, MN 32 Ch. https://www.dslreports.com/forum/r30041763- Minneapolis, MN 24 Ch. Minneapolis, MN 32 Ch. https://secure.dslreports.com/forum/r29899176- Saint Paul, MN 24 Ch. Mississippi Jackson, MS Jackson, MS 32 Ch. Pearl, MS Southaven, MS Missouri Nevada Henderson, NV New Hampshire Derry, NH Dover, NH Dover, NH 24 Ch. Kingston, NH Kingston, NH 24 Ch. Manchester, NH Manchester, NH 24 Ch. Manchester, NH 32 Ch. Merrimack, NH 24 Ch. New Jersey Beach Haven, NJ 32 Ch. http://www.dslreports.com/forum/r30018409- Beachwood, NJ 24 Ch. Beachwood, NJ 32 Ch. Brick, NJ 24 Ch. Cape May, NJ 24 Ch. Egg Harbor, NJ 24 Ch Glen Gardner, NJ High Bridge, NJ 32 Ch. Lebanon, NJ 24 Ch. https://www.dslreports.com/forum/r30027667- Lincroft, NJ 24 Ch. Mullica Hill, NJ Northfield, NJ 32 Ch. Ocean City, NJ Shamong, NJ 24 Ch. Swedesboro, NJ Vineland, NJ 24 Ch. Vineland, NJ 32 Ch. Washington, NJ Washington, NJ 24 Ch. Wildwood, NJ 24 Ch. New Mexico https://secure.dslreports.com/forum/r29886841- Albuquerque, NM 32 Ch. Santa Fe, NM Santa Fe, NM 24 Ch. Santa Fe, NM 32 Ch. New York Hopewell Junction, NY 24 Ch. Patterson, NY Patterson, NY 32 Ch. North Carolina Ohio Oregon East Multnomah County, OR 32 Ch. https://secure.dslreports.com/forum/r29834437- Happy Valley, OR https://secure.dslreports.com/forum/r29828423- Portland, OR Portland, OR 24 Ch. West Linn, OR Pennsylvania Aliquippa, PA 24 Ch. Ambridge, PA Apollo, PA Avonmore, PA Canonsburg, PA Lancaster, PA 24 Ch. Lancaster, PA 32 Ch. Marietta, PA 24 Ch. Muncie, PA Newtown, PA 24 Ch. Philadelphia, PA 24 Ch. Phillipsburg, PA Pittsburgh, PA Prospect Park, PA Prospect Park, PA 24 Ch. Reading, PA Reading, PA 24 Ch. Reading, PA 32 Ch. Scranton, PA 24 Ch. State College, PA State College, PA 24 Ch. State College, PA 32 Ch. Venetia, PA 24 Ch. Verona, PA Verona, PA 24 Ch. York, PA 32 Ch. South Carolina Tennessee Antioch, TN 24 Ch. Brentwood, TN Chattanooga, TN Frayserville, TN Johnson City / Gray, TN 24 Ch. Knoxville, TN Lakeland, TN Murfreesboro, TN 24 Ch. Murfreesboro, TN 32 Ch. Nashville, TN Texas https://secure.dslreports.com/forum/r29829229- Houston, TX 24 Ch. Spring, TX 24 Ch. Utah Farmington, UT 24 Ch. Ogden, UT 24 Ch. Riverton, UT 24 Ch. Sandy, UT 24 Ch. Taylorsville, UT 24 Ch. Taylorsville, UT 32 Ch. Vermont Virginia Alexandria, VA Alexandria, VA 24 Ch. Alexandria, VA 32 Ch. Arlington, VA 24 Ch. http://www.dslreports.com/forum/r29818660- Clear Brook, VA 24 Ch. Lynchburg, VA Midlothian, VA Palmyra, VA 24 Ch. Penn Laird, VA https://www.dslreports.com/forum/r30070887- Winchester, VA 24 Ch. Washington Centralia, WA https://secure.dslreports.com/forum/r29893844- https://secure.dslreports.com/forum/r29875374- Kent, WA Kent, WA 24 Ch. North Bend, WA 24 Ch. Seattle, WA Seattle, WA 24 Ch. Seattle, WA 32 Ch. Spokane, WA Spokane, WA 24 Ch. Spokane, WA 32 Ch. https://www.dslreports.com/forum/r29992142- Vancouver, WA 24 Ch. Washington, D.C. https://www.dslreports.com/forum/r29994953- West Virginia Morgantown, WV Morgantown, WV 32 Ch. Wisconsin -- In God we trust; all others bring data!

Anyone know if Comcast has actually started installs? I live in the west palm beach, fl market announced for deployment this month. So far phone agents don't know anything of the service. I've been told by different agents, 2016, June and it'll be in the system tomorrow. None had even heard of the service before I inquired and they did a bit of research, so I went to out local sales office to inquire in person. There I had to show them the press release, to which they simply said its not yet available in the market. Seems like this was a pure fiber to the press release hail marry announcement to try to salvage the dead merger. Mod Note: Report actual receipt of Gigabit service here -> https://www.dslreports.com/forum/r30084813-Speed-Report-Gigabit-Pro-Service-Here Side discussion in this thread, please. Keep it on topic. If you have questions or suggestions, please IM uid://455626. We need to consolidate all discussion about Gigabit Pro to one topic, all discussion which is not confirmed report of availability in a particular area. The report topics are now posted and stickied. See also these now closed topics -> https://www.dslreports.com/forum/r30008362-Speed-2-Gbps-Coming-to-SE-Florida https://www.dslreports.com/forum/r30038435-Speed-Chicago-getting-Gigabit-Pro-later-this-Month https://www.dslreports.com/forum/r30068565-Speed-Gigabit-Pro-May-be-coming-to-Portland https://www.dslreports.com/forum/r30068519-Speed-Gigabit-Pro-coming-to-Denver https://www.dslreports.com/forum/r30068453-Comcast-to-offer-Gigabit-Pro-in-Minneapolis-St-Paul https://www.dslreports.com/forum/r30049713-Speed-Comcast-2-Gbps-Fiber-to-the-Home http://www.dslreports.com/forum/r30129326-Reduced-latency-with-Extreme-250-service http://www.dslreports.com/forum/r30165313-Plan-Extreme-505-Mbps-for-400 http://www.dslreports.com/forum/r30166441-extreme-505 http://www.dslreports.com/forum/r30168268-Speed-Comcast-Gigabit-pro-for-Nashville-available-to-order https://www.dslreports.com/forum/r30676109-Email-stating-gigabit-is-on-the-way-to-Woodstock-GA https://www.dslreports.com/forum/r30668361-Install-Gigabit-Pro-install-in-an-MDU https://www.dslreports.com/forum/r30687179-Comparing-Comcast-Gigabit-to-other-high-speed-ISPs https://www.dslreports.com/forum/r30748503-DOCSIS-Gigabit-Service-Email (Marietta, GA) Note this new side discussion topic for the DOCSIS 3.1 Gigabit deployment > https://www.dslreports.com/forum/r30813189-Plan-Side-Discussion-on-DOCSIS-3-1-Gigabit-service uid://720248 will post new stickied topic for those who wish to report actual install of DOCSIS 3.1 Gigabit service. Watch for it in the stickied section at top of the forum list. uid://455626 Forum Moderator

I had a similar question to this thread, but I can't post on it because it's locked. https://www.dslreports.com/forum/r31614799-CustSvc-Xfinity-TV-Stream-authentication-IP-Range-question Basically I use my vpn for my main connection through pfsense and I wanted to add an exception for xfinity stream. I used this addon to see which connections chrome makes https://chrome.google.com/webstore/detail/network-sniffer/coblekblkacfilmgdghecpekhadldjfj?hl=en I tried to use wireshark and mcirosoft network analyzer but sorting through all system connections is annoying. I used pfsense's alias feature to add the hostnames, and then just put that rule in the firewall rules under the lan section. These were the main ones I found. Some of them will be different for your area of course, but just using the hostnames may be enough. Hopefully someone else will find this useful. EDIT: Actually some channels connect to external sources like ESPN have issues, you have to add more hostnames/ips. Honestly, another solution that works better is to use FoxyProxy with Firefox. Then on another computer (I'm using an orangepipc) Enable SSH. Then connect to it on your desktop with myentunnel and enable dynamic socks. Then enter localhost and port 7070 in foxyproxy. Then in my case, in pfsense I made it so the orangepipc goes straight to Comcast. I use Chrome as my main browser and then Firefox for xfintiy stream so this works alright. This method is more convenient.

Attached the WinMTR report to 8.8.8.8. Works well randomly, then websites etc. stop loading for a few seconds and rinse and repeat. This has been going on for a few weeks. I also went to Comcast and got an XB6 gateway, no difference. So back to my Netgear modem. Support says my modem levels are all fine.

Just FYI. I have an X1, but do not use the AnyRoom feature. My understanding is that AnyRoom uses the MOCA 1.1 protocol to communicate between STBs. I installed a network extender, 2 MOCA 2.0 adapters, to get internet back to my office in the rear of the house. Wifi works in the office, but it's a weak and slow signal. My Xfinity account supports 250/10 speeds, but Speedtest showed 95/10 through the MOCA setup. After some time online I found that in a MOCA network, the various adapters negotiate to the least common denominator. In this case they all step back to MOCA 1.1 to match the STB. When I unplugged the coax from the X1, and reset the MOCA 2.0 adapters, my tested speeds went to 290/12. I just now ordered a MOCA filter online. I'll put it between the X1 and the coax, to see if it hides the MOCA 1.1 in the X1 and allows me full speed on my network. I suspect it will. Just wanted to pass my experience on.

I frequently have to reboot my Denver area MB8600. Usually, it locks up between 2-10 days of use. Could it be something on the plant causing it to lock up? My signal levels are very good, but I can't check the logs for errors when it locks up (can't get to the 100.1 page). Or should I just try to have Motorola replace it?

Closing on our new home (04043) in March 2019. Comcast does NOT have a presence in our new area. Yes, I know Comcast will say "...bad choice of location. You owe us $X.** as a termination fee." and that I am stuck with that. Only choices for our address are DirecTV and Spectrum. I am reading almost nothing but shear horror stories regarding almost all aspects of Spectrum. Anyone from that zip code who may be able to comment on a similar transition from Comcast and how it has all worked out? Thanks in advance.

I recently switched modems from a Zoom 5341J to a Moto MB8600. I immediately noticed that I wasn't getting the speeds I was getting with the Zoom. I have the Performance Pro tier and in my market, that tier is advertised at 150/5 and has historically provided 175/6, I've been getting those speeds for years with the Zoom. I tried in the Direct forum and while I believe, I hope, that the rep is still working on it I'm not sure but as I got a call from Comcast Corporate this morning that basically told me that I'm getting what I pay for so I should be happy and as I did not contact Corporate about this I'm assuming the rep in the Direct forum initiated the call. I'm waiting to hear back from him. Bottom line, I'm just trying to get the right config file for the modem and if anyone has any ideas on how to go about that I would sure appreciate it. Thanks!

Since they completed Fiber Deep in my neighborhood, we now only lock 30 rather than 31 downstream DS 3.0 channels, but speeds are still high due to the OFDM channel. A better question is what's at 615000000 Hz (Channel 18) - it has a drastically higher error count than any other: Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 21 831000000 Hz 4.8 dBmV 43.1 dB 3372667650 4723 7168 2 Locked QAM256 1 519000000 Hz 3.4 dBmV 43.4 dB 3439606675 8493 19783 3 Locked QAM256 2 525000000 Hz 3.3 dBmV 43.4 dB 3439622600 8793 21268 4 Locked QAM256 3 531000000 Hz 3.3 dBmV 43.4 dB 3439620535 8788 20593 5 Locked QAM256 4 537000000 Hz 3.4 dBmV 43.3 dB 3439625219 8536 20565 6 Locked QAM256 5 543000000 Hz 3.4 dBmV 43.3 dB 3439631337 9080 20746 7 Locked QAM256 6 549000000 Hz 3.5 dBmV 43.2 dB 3439629970 8728 20063 8 Locked QAM256 7 555000000 Hz 3.5 dBmV 43.2 dB 3439639988 8569 19425 9 Locked QAM256 8 561000000 Hz 3.6 dBmV 43.3 dB 3439660620 32092 47287 10 Locked QAM256 9 567000000 Hz 3.4 dBmV 43.2 dB 3439773741 17304 20642 11 Locked QAM256 10 573000000 Hz 3.5 dBmV 43.3 dB 3439777782 8470 19539 12 Locked QAM256 11 579000000 Hz 3.4 dBmV 42.0 dB 3439791602 8467 19498 13 Locked QAM256 12 585000000 Hz 3.5 dBmV 43.0 dB 3439783624 8224 20127 14 Locked QAM256 13 591000000 Hz 3.8 dBmV 42.6 dB 3439672641 64110 65702 15 Locked QAM256 14 597000000 Hz 3.9 dBmV 42.5 dB 3439798869 8816 20436 16 Locked QAM256 15 603000000 Hz 4.0 dBmV 42.9 dB 3439796641 7951 18554 17 Locked QAM256 16 609000000 Hz 4.0 dBmV 43.4 dB 3439996640 8090 18650 18 Locked QAM256 17 615000000 Hz 4.1 dBmV 43.3 dB 3436626777 1350073 875489 19 Locked QAM256 18 813000000 Hz 5.1 dBmV 43.6 dB 3440011615 8492 20173 20 Locked QAM256 19 819000000 Hz 4.9 dBmV 43.5 dB 3440013765 8387 19766 21 Locked QAM256 20 825000000 Hz 4.7 dBmV 43.3 dB 3440017531 8497 20778 22 Locked QAM256 22 837000000 Hz 4.7 dBmV 43.2 dB 3440021989 8321 19985 23 Locked QAM256 23 843000000 Hz 4.7 dBmV 43.3 dB 3440008574 14995 33289 24 Locked QAM256 24 849000000 Hz 4.7 dBmV 43.4 dB 3440029337 8564 19943 25 Locked QAM256 25 855000000 Hz 4.7 dBmV 43.2 dB 3440064656 8273 20381 26 Locked QAM256 26 861000000 Hz 4.8 dBmV 43.4 dB 3440067905 8860 20488 27 Locked QAM256 27 867000000 Hz 4.4 dBmV 43.2 dB 3440074774 8556 20213 28 Locked QAM256 28 873000000 Hz 4.6 dBmV 43.4 dB 3440077198 8247 19790 29 Locked QAM256 29 879000000 Hz 4.2 dBmV 43.3 dB 3440075746 8064 19175 30 Locked QAM256 30 885000000 Hz 4.5 dBmV 43.5 dB 3440079904 8305 19942 31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 Upstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 5 36500000 Hz 41.8 dBmV 2 Locked ATDMA 6 30100000 Hz 41.0 dBmV 3 Locked ATDMA 7 23700000 Hz 40.0 dBmV 4 Locked ATDMA 8 17300000 Hz 39.5 dBmV 5 Not Locked Unknown 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0, 255 33 654000000 Hz 4.8 dBmV 42.0 dB 1108 ~ 2987 5141085108 4460528027 0 2 Not Locked 0, 255 0 0 Hz 2.4 dBmV 0.0 dB 0 ~ 4095 0 0 0

This evening i picked up an SB8200 and a CM1000. I wanted to compare performance between the two. What I found unusual is that the SB8200 had a higher power level vs the CM1000. Is this normal? With the CM1000 closer to 0, is it making a better connection? e.g 483000000 - SB8200 = 4.8 &38.6 vs cm1000 = 3.2 & 39.1

Sometime overnight or early this morning, I received a voicemail that was sent on Thursday at 7:34 PM. Has anyone else here experienced this?

As of last month, I went over my allotted data by 1024G. As of today, I've been throttled. I have Google WIFI and can get a consistent 740/38 like I always have but any SSL or VPN is crawling at 1.5-4MB. I've upgraded my plan to unlimited which I thought would have removed the throttle. Are you guys able to assist me with this?

I have been checking my modem logs and noticed T3 timeouts almost constantly. This is a new modem, Arris SB6183. I never noticed this on my old SB 6121. The weird thing, at least to me, is that I don't seem to have any noticeable problems. From what I have read, This seems to sometimes be corrected by having a new line run. I will post the log if anyone wants to weigh in. I did a chat with comcast/xfinity and that was pretty much a waste of time. Should I be concerned or just let it go since I don't seem to have any other issues, at least none I am aware of. Event Log The table below contains the log of events that the SB6183 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur. Time Priority Description Sat Nov 03 11:26:30 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:23:03 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:23:03 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:23:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:54 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:54 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:43 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:43 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:22:43 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:50 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:50 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:41 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:41 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:41 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:31 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:31 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:15:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:38 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:38 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:38 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:29 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:29 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:19 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:19 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:08:19 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:26 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:26 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:26 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:17 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:17 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:17 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:06 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:06 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 11:01:06 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:13 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:13 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:13 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:04 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:04 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:54:04 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:53:54 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:53:54 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:53:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:47:01 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:47:01 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:47:01 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:52 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:52 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:52 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:42 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:42 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:46:42 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:48 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:48 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:48 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:39 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:39 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:39 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:29 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:29 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:39:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:35 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:35 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:35 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:27 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:27 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:27 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:17 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:17 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:32:17 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:23 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:23 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:23 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:15 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:15 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:15 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:04 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:04 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:25:04 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:11 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:11 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:02 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:02 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:18:02 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:17:52 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:17:52 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:17:52 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:58 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:58 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:58 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:49 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:49 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:49 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:39 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:39 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0; Sat Nov 03 10:10:39 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b7:b5:ad;CMTS-MAC=00:01:5c:69:3e:5e;CM-QOS=1.1;CM-VER=3.0;

Are there any plans to extend or build out into the area of Scott & Stoneybrook as noted above? We only have Windstream available for land based internet as other large providers won’t build out into our area at all. I’ve had confirmation of this from multiple sources. I can safely state that even though this neighborhood is on minimum 5 acre lots, all in this neighborhood would jump at the chance for better internet connectivity (better than a max of 15/1).