This problem is highly intermittant, I see it maybe once every 3-4 months or so. 5ghz wifi and wired connection not affected. Modem has been reset and/or power cycled when problem occurs, no effect. Outage usually lasts 5+ hours then comes back up on its own. Usually occurs after midnight (but has occured during the day), service center says no maintenance in my area but I have caught techs working on something 3-4 blocks away during outage. Folks next door with Comcast phone service will tell me the next day that phones were out during the time my 2.4ghz wifi was interupted. I have reported this to the service center several times during the outage over the last 3 years at my current location. Had xfinity bc at older location with older non-ac router for 10+ years with zero problems. I would at some point like to get this solved. Obviously, the service center doesn't know when work is being done in my area, and can't tell that my 2.4 wifi won't let devices 'attach' (either on the 'xfinity' or private 'cbc' carrier). Fyi, wifi signal is max on all four carriers with solid id's, when attempt to attach, router tries then quits. I've moved as much as I can to 5ghz and installed 5-2.4 repeaters but still have a couple dead spots that I don't want to spend money on more repeaters when the comcast 2.4 covers the area just fine when it's working.

I just bought an MB8600 and I'm noticing very high noise on a channel. Is it worth calling Comcast over to see if there's a problem with the line? Should I terminate all open coax jacks in the house? I don't really seem to have my speed affected, but I'm wondering if there's anything I should do.

[att=1] Used to be able to restart this modem from the troubleshooting section, I thought: https://customer.xfinity.com/#/services/modem-restart

So is the Puma 6 issue now solved? I just ran the Puma 6 test here and said as is well despite me running a 1682G which uses a Puma 6. Did notice new firmware version on it tho.

Just got 9.1.93T and thing are a lot better. Page loads are better and mail doesn't take forever to connect to the servers. But speed tests are still nutsz. [att=1] [att=2] Split from > https://www.dslreports.com/forum/r30771922-Firmware-Problems-with-the-new-6190-firmware-9-1-93N

I have been able up until a few days ago to log into my Technicolor at 192.168.100.1. I was able to do so through my router which I bought some time ago and which uses dd-wrt (I've only used the comcast provided R8000 for troubleshooting). It has allowed me to get to the login page of the modem without having to make a direct PC to modem cable connection to check out the signal strength. The other day when I tried, I got a certificate error and made a temporary exception to bypass that (not that I think that is great) and did get to the login password prompt. I have used 3 different browsers and all act the same. I put the default info into the box and got an error. Note: I have been using the default login and password because it was not changeable on the modem as there were no buttons to click on the modem pages to make such a change. Evidently, something has been changed in the modem. While I know there is a possibility of being hacked (and I know that it would absolutely would have to be from the outside if that is the case), I believe that there may have been a firmware update that has caused this problem with both the certificate and the login issue. What I would like to know if there is anyone who has been able to log into the modem and if there is a problem now or if it still works. I would also like to know if anyone knows if the firmware has been modified in the last week or so. I do know that comcast knows that I can log into the modem because I had an issue and spoke with technical support and then had a tech come over who saw the screens when I showed him. This login problem started about 2 weeks after the tech came over. Any help would be appreciated.

What have your recent experiences with Comcast's customer service/support been like? Comcast (Yes, That Comcast) Knows a Thing or Two About Customer Experience By Candace Cui, CMSWire - October 4, 2017 http://www.cmswire.com/customer-experience/comcast-yes-that-comcast-knows-a-thing-or-two-about-customer-experience/quote:The following statement may surprise many: there's much to learn from Comcast’s customer experience team. Comcast Leaves Customer Experience Blunders Behind Members of the Comcast CX team were refreshingly blunt about their former reputation during the CX Day event yesterday held in the flashy new Comcast Studio Xfinity flagship store in Chicago. “We definitely weren’t, and still aren’t, perfect,” said Graham Tutton, VP Customer Insights at the Philadelphia-headquartered Comcast. Tutton cited numerous examples of the company's less than stellar customer service record, including the dubious honor of topping MSN.com’s Customer Service Hall of Shame. But times are changing. Comcast is growing its CX team, tackling its customer happiness with the same force that it grew its operations and prowess. With a $300 million investment in the Chicago-based region alone, it can now boast the largest net promoter score (NPS) worldwide. Cultural Change Drives Customer Efforts It’s not, however, the score that matters for its NPS, it’s the system. David Smith, Comcast’s VP Customer Experience, emphasized cultural change across the company's 90,000 employees was at the heart of the company's many CX efforts. “It’s an emotional thing, energizing employees on the front line.” From monthly employee surveys to ensuring the CEO speaks to customers directly each week, working with that 90,000 person team has boosted its NPS from region to region by an average of 20 points. Without internal advocacy, people go to work with the same goals and customer-facing strategies often go awry. By reaching across the aisle, Tutton repeated many times, you can reinvest in what makes your work matter. Comcast's Win-Win-Win Tutton produced an interesting result of how incremental changes make big impacts. With the processes in place over the last two years of customer experience improvements, Comcast has saved an accumulated 347 years of waiting time for their customers in the Chicago-based region alone. From an ROI perspective, that’s money saved. From a customer perspective, that’s more time for their daily lives. From an employee perspective, that’s a win. Most importantly, the lesson learned from Comcast is that customer experience is never finished. This is not a project with a timeline for completion, only goals reached and setbacks along the way. Without a focus on creating cultural transformation, organizations are guaranteed to see more setbacks than successes. ...

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 received an email from Comcast with the following text. "We’ve detected a loose or damaged cable in your home. If it isn’t fixed, you could experience service issues in the future. This may also impact the service quality of others in your neighborhood. We would like to locate and fix the issue to make sure you don’t experience any problems in the future. Give us a call today to schedule your complimentary service visit." Do any of the techs here know what exactly triggers this email to be sent? The modem logs haven't shown an kind of disconnect or T3 timeout since late September. Nobody left any kind of door tag, and if they climbed the pole in my back yard to disconnect the drop to confirm the ingress was coming from my house, the modem would have reset. The upstream power level is 34-36 dBmV same as it has always been, on the bottom of the acceptable range. The run the modem is old RG-59 coax with two barrel connectors replacing points where there used to be splitters as I am an internet only subscriber. Should I expect that this wiring is going to be condemned and replaced possibly costing me some $$$, or do they typically fix this by adding some kind of attenuator? If something was really messing up the system badly, would I already be disconnected? Here are the signal stats. ------- Channel ID 9 10 11 12 Frequency 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz Signal to Noise Ratio 38 dB 38 dB 38 dB 38 dB Downstream Modulation QAM256 QAM256 QAM256 QAM256 Power Level The Downstream Power Level 0 dBmV 0 dBmV 0 dBmV 0 dBmV Upstream Bonding Channel Value Channel ID 2 1 3 Frequency 19400000 Hz 25800000 Hz 14600000 Hz Ranging Service ID 3125 3125 3125 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 35 dBmV 36 dBmV 34 dBmV Upstream Modulation [2] QPSK [1] 16QAM [3] 64QAM [2] QPSK [1] 16QAM [3] 64QAM [2] QPSK [1] 16QAM [3] 64QAM Ranging Status Success Success Success Signal Stats (Codewords) Bonding Channel Value Channel ID 9 10 11 12 Total Unerrored Codewords 159678590035 159677452215 159677450180 159677396983 Total Correctable Codewords 11686 3591 5926 58036 Total Uncorrectable Codewords 10336 5686 5545 6765

Current package is Xfinity Double play (internet :Performance Pro with basic digital ) plus DirectV Choice ( Genie HD DVR with one Satellite unit, whole house DVR) for $135 incl taxes and fees. I am considering changing to Comcast completely. They are offering me the following : Xfinity double play : Xfinity Internet Performance Pro ;Digital Starter; X1 HD DVR plus 1 satellite device for $120 /mo incl all fees and Tax. Is this a reasonable cost? I can probably get a little more off DirectV but would be hard pressed to match the Xfinity offer (as a total ) . I am wondering whether is worth the hassle to switch if the difference is less than $10 per month also that Comcast is planning to change their transmission scheme to add more channels . Advise please. Tks

Since it has been said there is new firmware coming for the 6190 I decided to put the 6190 back online so I can see for myself if the issues are resolved with the 6190 with the new firmware. Normally this activation page would come up: http://www.xfinity.com/activate Today this new page came up: https://register.be.xfinity.com/activate

Hello I live in Media PA, a suburb of Philadelphia. My internet setup features a Comcast Xfinity modem in the basement, which runs up two floors to a Netgear N750 router in the office, which serves as the main wi-fi source, along with wired connections to the desktop in the office, as well as to my gaming PC in my bedroom. In terms of anti-virus, I run Windows Firewall on my gaming PC, as well as Malwarebytes as an anti-virus. With all of the components mentioned, the issue I've been having involves my internet connection (on wired devices and wireless alike) going down for a brief period of time (often not even a minute). It comes back after a while with no obvious drop in speed, but the moment when the connection goes down is enough to completely mess up things (as a gamer, I find this incredibly frustrating). When it does happen, I run a diagnostic to see what the problem it, and it is often presented to me as a DNS Server issue. This indicates to me that it's likely not my router that is the issue (though feel free to correct me if I am wrong on that one), and that it is something with the connection itself or something with the DNS server or something of that nature. This issue has been happening for well over a month at this point, and it seems to happen daily, often in the evening, though I have caught it happening in the early afternoons and in the mornings as well. If there is anything out there that can resolve this issue, that would be greatly appreciated.

I have been getting a good amount of T3 timeouts lately. I thought maybe had a bad line or something but I have been home couple times it has happened and able to get into logs to see what is going on. What happened I was suddenly unable to browse the web computer shows no internet, but have all connection lights on modem and router. I am unable to log into modem interface, but can get into router. It shows as if I still have connection and still getting the normal blocked internet request. So I try to access my home network threw my cell phone but it just spins and nothing ever shows up. After a few more minuets suddenly the blue light starts flashing on the upstream of the modem. Finally after roughly 10 mins or so I can browse again and get into modem. Long story short going threw the logs shows an abnormally high amount of blocked request on modem logs during the entire time I can not get on the internet. I can even see where I tried to access the network but I never received a response. This has happened twice that I have been home to be able to check logs, and just checking logs of router shows and exuberant amount of blocked request from the internet. Now, I know this is inevitable, but I NEVER got this amount when I was on DSL and when it did pick up, I power cycle the modem until I got an IP that was a lot more quieter. But I have had the same IP since registered a little over a month ago no matter how many times I reboot. Question is, does the Zoom 5370 not able to cope with and which modem would be better at it? Or, is someone just flooding the living day lights out of me? Numbers and power levels are all the same as it has been since the beginning. Router log [Service blocked: ICMP_echo_req] from source 218.101.70.94, Thursday, Nov 02,2017 18:31:23 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:31:23 [Service blocked: ICMP_echo_req] from source 119.128.122.6, Thursday, Nov 02,2017 18:31:18 [Service blocked: ICMP_echo_req] from source 94.75.173.171, Thursday, Nov 02,2017 18:31:17 [Service blocked: ICMP_echo_req] from source 46.177.151.96, Thursday, Nov 02,2017 18:31:17 [Service blocked: ICMP_echo_req] from source 60.54.22.242, Thursday, Nov 02,2017 18:31:15 [Service blocked: ICMP_echo_req] from source 188.163.70.172, Thursday, Nov 02,2017 18:30:32 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:29:46 [Service blocked: ICMP_echo_req] from source 176.234.26.34, Thursday, Nov 02,2017 18:29:04 [Service blocked: ICMP_echo_req] from source 178.121.69.153, Thursday, Nov 02,2017 18:29:01 [Service blocked: ICMP_echo_req] from source 178.73.197.153, Thursday, Nov 02,2017 18:28:58 [Service blocked: ICMP_echo_req] from source 178.210.18.222, Thursday, Nov 02,2017 18:28:19 [Service blocked: ICMP_echo_req] from source 46.38.76.109, Thursday, Nov 02,2017 18:28:19 [Service blocked: ICMP_echo_req] from source 188.112.200.89, Thursday, Nov 02,2017 18:28:18 [Service blocked: ICMP_echo_req] from source 181.208.61.32, Thursday, Nov 02,2017 18:28:17 [Service blocked: ICMP_echo_req] from source 178.121.56.243, Thursday, Nov 02,2017 18:28:14 [Service blocked: ICMP_echo_req] from source 75.137.165.40, Thursday, Nov 02,2017 18:27:26 [Service blocked: ICMP_echo_req] from source 77.69.238.108, Thursday, Nov 02,2017 18:27:26 [Service blocked: ICMP_echo_req] from source 77.77.201.9, Thursday, Nov 02,2017 18:27:24 [Service blocked: ICMP_echo_req] from source 107.77.248.115, Thursday, Nov 02,2017 18:26:41 [Service blocked: ICMP_echo_req] from source 151.135.66.209, Thursday, Nov 02,2017 18:26:40 [Service blocked: ICMP_echo_req] from source 185.81.132.6, Thursday, Nov 02,2017 18:26:40 [Service blocked: ICMP_echo_req] from source 220.76.77.16, Thursday, Nov 02,2017 18:26:39 [Service blocked: ICMP_echo_req] from source 107.15.246.144, Thursday, Nov 02,2017 18:26:39 [Service blocked: ICMP_echo_req] from source 61.128.131.67, Thursday, Nov 02,2017 18:26:39 [Service blocked: ICMP_echo_req] from source 86.63.92.134, Thursday, Nov 02,2017 18:26:00 [Service blocked: ICMP_echo_req] from source 112.209.46.16, Thursday, Nov 02,2017 18:25:57 [Service blocked: ICMP_echo_req] from source 190.73.11.190, Thursday, Nov 02,2017 18:25:57 [Service blocked: ICMP_echo_req] from source 174.124.68.49, Thursday, Nov 02,2017 18:25:53 [Service blocked: ICMP_echo_req] from source 89.137.231.31, Thursday, Nov 02,2017 18:25:10 [Service blocked: ICMP_echo_req] from source 5.19.9.226, Thursday, Nov 02,2017 18:25:09 [Service blocked: ICMP_echo_req] from source 205.250.126.32, Thursday, Nov 02,2017 18:25:03 [Service blocked: ICMP_echo_req] from source 27.18.148.48, Thursday, Nov 02,2017 18:24:21 [Service blocked: ICMP_echo_req] from source 94.224.164.19, Thursday, Nov 02,2017 18:24:19 [Service blocked: ICMP_echo_req] from source 121.239.111.105, Thursday, Nov 02,2017 18:24:18 [Service blocked: ICMP_echo_req] from source 92.98.228.253, Thursday, Nov 02,2017 18:23:37 [Service blocked: ICMP_echo_req] from source 78.29.81.46, Thursday, Nov 02,2017 18:23:36 [Service blocked: ICMP_echo_req] from source 218.156.91.175, Thursday, Nov 02,2017 18:23:35 [Service blocked: ICMP_echo_req] from source 170.233.37.70, Thursday, Nov 02,2017 18:23:33 [Service blocked: ICMP_echo_req] from source 36.235.23.249, Thursday, Nov 02,2017 18:23:33 [Service blocked: ICMP_echo_req] from source 189.190.200.242, Thursday, Nov 02,2017 18:22:55 [Service blocked: ICMP_echo_req] from source 83.242.116.238, Thursday, Nov 02,2017 18:22:53 [Service blocked: ICMP_echo_req] from source 91.96.25.80, Thursday, Nov 02,2017 18:22:49 [Service blocked: ICMP_echo_req] from source 93.158.200.242, Thursday, Nov 02,2017 18:22:48 [Service blocked: ICMP_echo_req] from source 190.31.189.183, Thursday, Nov 02,2017 18:22:31 [DoS attack: Smurf] attack packets in last 20 sec from ip [190.31.188.255], Thursday, Nov 02,2017 18:22:30 [Service blocked: ICMP_echo_req] from source 163.172.18.148, Thursday, Nov 02,2017 18:22:29 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:21:14 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:21:13 [Service blocked: ICMP_echo_req] from source 156.217.122.66, Thursday, Nov 02,2017 18:21:12 [LAN access from remote] Thursday, Nov 02,2017 18:20:59 [LAN access from remote] Thursday, Nov 02,2017 18:20:59 able to access once again [LAN access from remote] Thursday, Nov 02,2017 18:20:59 [LAN access from remote] Thursday, Nov 02,2017 18:20:59 [LAN access from remote] Thursday, Nov 02,2017 18:20:58 [LAN access from remote] Thursday, Nov 02,2017 18:20:58 [LAN access from remote] Thursday, Nov 02,2017 18:20:57 [LAN access from remote] Thursday, Nov 02,2017 18:20:57 [LAN access from remote] Thursday, Nov 02,2017 18:20:56 [LAN access from remote] Thursday, Nov 02,2017 18:20:55 [LAN access from remote] Thursday, Nov 02,2017 18:20:55 [LAN access from remote] Thursday, Nov 02,2017 18:20:55 [Service blocked: ICMP_echo_req] from source 64.121.217.161, Thursday, Nov 02,2017 18:20:36 [Service blocked: ICMP_echo_req] from source 90.221.145.252, Thursday, Nov 02,2017 18:20:36 [Service blocked: ICMP_echo_req] from source 110.74.195.98, Thursday, Nov 02,2017 18:20:36 [Service blocked: ICMP_echo_req] from source 176.232.30.228, Thursday, Nov 02,2017 18:20:33 [Service blocked: ICMP_echo_req] from source 178.44.22.185, Thursday, Nov 02,2017 18:20:31 [Service blocked: ICMP_echo_req] from source 156.217.122.66, Thursday, Nov 02,2017 18:19:47 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:19:42 [Service blocked: ICMP_echo_req] from source 189.1.17.247, Thursday, Nov 02,2017 18:19:02 [Service blocked: ICMP_echo_req] from source 95.245.215.180, Thursday, Nov 02,2017 18:19:01 [Service blocked: ICMP_echo_req] from source 93.90.34.103, Thursday, Nov 02,2017 18:18:59 [Service blocked: ICMP_echo_req] from source 116.86.222.126, Thursday, Nov 02,2017 18:18:15 [Service blocked: ICMP_echo_req] from source 173.239.232.4, Thursday, Nov 02,2017 18:18:14 [Service blocked: ICMP_echo_req] from source 78.121.107.173, Thursday, Nov 02,2017 18:18:13 [Service blocked: ICMP_echo_req] from source 46.249.171.173, Thursday, Nov 02,2017 18:18:12 [Service blocked: ICMP_echo_req] from source 188.254.126.128, Thursday, Nov 02,2017 18:17:31 [Service blocked: ICMP_echo_req] from source 46.107.231.196, Thursday, Nov 02,2017 18:17:30 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:17:29 [Service blocked: ICMP_echo_req] from source 217.150.59.62, Thursday, Nov 02,2017 18:17:29 [Service blocked: ICMP_echo_req] from source 14.232.174.11, Thursday, Nov 02,2017 18:17:27 [Service blocked: ICMP_echo_req] from source 78.102.93.47, Thursday, Nov 02,2017 18:17:27 [Service blocked: ICMP_echo_req] from source 194.48.218.246, Thursday, Nov 02,2017 18:17:27 [Service blocked: ICMP_echo_req] from source 173.171.244.158, Thursday, Nov 02,2017 18:16:50 [Service blocked: ICMP_echo_req] from source 81.162.71.154, Thursday, Nov 02,2017 18:16:49 [Service blocked: ICMP_echo_req] from source 176.226.192.70, Thursday, Nov 02,2017 18:16:42 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:16:21 [Service blocked: ICMP_echo_req] from source 78.56.11.76, Thursday, Nov 02,2017 18:16:04 [Service blocked: ICMP_echo_req] from source 46.177.56.72, Thursday, Nov 02,2017 18:16:01 [Service blocked: ICMP_echo_req] from source 186.248.139.76, Thursday, Nov 02,2017 18:15:58 [Service blocked: ICMP_echo_req] from source 89.151.179.108, Thursday, Nov 02,2017 18:15:19 [Service blocked: ICMP_echo_req] from source 14.231.153.172, Thursday, Nov 02,2017 18:15:17 [Service blocked: ICMP_echo_req] from source 192.211.25.3, Thursday, Nov 02,2017 18:15:16 [Service blocked: ICMP_echo_req] from source 92.114.214.180, Thursday, Nov 02,2017 18:15:12 [Service blocked: ICMP_echo_req] from source 176.120.53.139, Thursday, Nov 02,2017 18:14:33 [Service blocked: ICMP_echo_req] from source 79.16.67.158, Thursday, Nov 02,2017 18:14:30 [Service blocked: ICMP_echo_req] from source 94.75.173.171, Thursday, Nov 02,2017 18:14:29 [Service blocked: ICMP_echo_req] from source 88.146.176.42, Thursday, Nov 02,2017 18:14:28 [Service blocked: ICMP_echo_req] from source 24.52.212.50, Thursday, Nov 02,2017 18:13:44 [Service blocked: ICMP_echo_req] from source 90.195.213.160, Thursday, Nov 02,2017 18:13:41 [LAN access from remote] Thursday, Nov 02,2017 18:13:09 when I tried to access and response [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:13:02 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:13:00 [Service blocked: ICMP_echo_req] from source 180.0.212.250, Thursday, Nov 02,2017 18:12:21 [Service blocked: ICMP_echo_req] from source 104.136.26.91, Thursday, Nov 02,2017 18:12:19 [Service blocked: ICMP_echo_req] from source 191.241.36.238, Thursday, Nov 02,2017 18:12:19 [Service blocked: ICMP_echo_req] from source 188.190.53.96, Thursday, Nov 02,2017 18:12:19 [Service blocked: ICMP_echo_req] from source 178.91.122.120, Thursday, Nov 02,2017 18:12:17 [Service blocked: ICMP_echo_req] from source 154.45.216.238, Thursday, Nov 02,2017 18:12:15 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:04:46 [Service blocked: ICMP_echo_req] from source 156.217.122.66, Thursday, Nov 02,2017 18:04:45 [Service blocked: ICMP_echo_req] from source 193.70.90.205, Thursday, Nov 02,2017 18:04:42 [Service blocked: ICMP_echo_req] from source 192.145.206.3, Thursday, Nov 02,2017 18:04:41 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:04:40 [Service blocked: ICMP_echo_req] from source 65.123.202.139, Thursday, Nov 02,2017 18:04:33 [Service blocked: ICMP_echo_req] from source 23.92.31.220, Thursday, Nov 02,2017 18:04:31 [Service blocked: ICMP_echo_req] from source 186.235.98.5, Thursday, Nov 02,2017 18:03:59 [Service blocked: ICMP_echo_req] from source 194.8.234.26, Thursday, Nov 02,2017 18:03:57 [Service blocked: ICMP_echo_req] from source 188.29.164.210, Thursday, Nov 02,2017 18:03:57 [Service blocked: ICMP_echo_req] from source 156.220.227.151, Thursday, Nov 02,2017 18:03:56 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:03:12 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:03:10 [Service blocked: ICMP_echo_req] from source 97.99.129.253, Thursday, Nov 02,2017 18:02:31 [Service blocked: ICMP_echo_req] from source 83.144.91.62, Thursday, Nov 02,2017 18:02:29 [Service blocked: ICMP_echo_req] from source 91.67.210.241, Thursday, Nov 02,2017 18:02:28 [Service blocked: ICMP_echo_req] from source 217.196.211.99, Thursday, Nov 02,2017 18:02:25 [Service blocked: ICMP_echo_req] from source 5.164.19.99, Thursday, Nov 02,2017 18:02:25 [Service blocked: ICMP_echo_req] from source 78.141.27.13, Thursday, Nov 02,2017 18:02:25 [Service blocked: ICMP_echo_req] from source 58.214.77.114, Thursday, Nov 02,2017 18:01:43 [Service blocked: ICMP_echo_req] from source 46.198.240.12, Thursday, Nov 02,2017 18:01:43 [Service blocked: ICMP_echo_req] from source 78.30.249.51, Thursday, Nov 02,2017 18:01:43 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 18:01:19 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:01:18 [Service blocked: ICMP_echo_req] from source 92.113.50.32, Thursday, Nov 02,2017 18:00:59 [Service blocked: ICMP_echo_req] from source 82.235.103.196, Thursday, Nov 02,2017 18:00:59 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 18:00:58 [Service blocked: ICMP_echo_req] from source 78.0.195.150, Thursday, Nov 02,2017 18:00:16 [Service blocked: ICMP_echo_req] from source 79.210.15.84, Thursday, Nov 02,2017 18:00:15 [Service blocked: ICMP_echo_req] from source 170.82.141.28, Thursday, Nov 02,2017 18:00:12 [Service blocked: ICMP_echo_req] from source 5.18.233.67, Thursday, Nov 02,2017 17:59:31 [Service blocked: ICMP_echo_req] from source 176.109.192.2, Thursday, Nov 02,2017 17:59:30 [Service blocked: ICMP_echo_req] from source 90.190.202.93, Thursday, Nov 02,2017 17:59:30 [Service blocked: ICMP_echo_req] from source 188.235.197.69, Thursday, Nov 02,2017 17:59:28 [Service blocked: ICMP_echo_req] from source 46.29.3.146, Thursday, Nov 02,2017 17:59:27 [Service blocked: ICMP_echo_req] from source 64.231.235.89, Thursday, Nov 02,2017 17:58:46 [Service blocked: ICMP_echo_req] from source 62.178.217.142, Thursday, Nov 02,2017 17:58:43 [Service blocked: ICMP_echo_req] from source 200.141.120.231, Thursday, Nov 02,2017 17:58:40 [Service blocked: ICMP_echo_req] from source 46.39.66.187, Thursday, Nov 02,2017 17:58:01 [Service blocked: ICMP_echo_req] from source 119.128.122.6, Thursday, Nov 02,2017 17:57:57 [Service blocked: ICMP_echo_req] from source 46.108.127.53, Thursday, Nov 02,2017 17:57:54 [Service blocked: ICMP_echo_req] from source 109.167.12.75, Thursday, Nov 02,2017 17:57:15 [Service blocked: ICMP_echo_req] from source 88.254.174.249, Thursday, Nov 02,2017 17:57:12 [Service blocked: ICMP_echo_req] from source 90.195.213.160, Thursday, Nov 02,2017 17:57:12 [Service blocked: ICMP_echo_req] from source 188.232.125.7, Thursday, Nov 02,2017 17:56:32 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 17:56:29 [Service blocked: ICMP_echo_req] from source 95.191.2.243, Thursday, Nov 02,2017 17:55:46 [Service blocked: ICMP_echo_req] from source 109.105.39.50, Thursday, Nov 02,2017 17:55:45 [Service blocked: ICMP_echo_req] from source 87.247.118.178, Thursday, Nov 02,2017 17:55:44 [Service blocked: ICMP_echo_req] from source 177.158.147.190, Thursday, Nov 02,2017 17:55:39 [Service blocked: ICMP_echo_req] from source 37.145.39.92, Thursday, Nov 02,2017 17:54:58 [Service blocked: ICMP_echo_req] from source 95.71.33.139, Thursday, Nov 02,2017 17:54:57 [Service blocked: ICMP_echo_req] from source 109.49.231.92, Thursday, Nov 02,2017 17:54:55 [Service blocked: ICMP_echo_req] from source 41.63.15.2, Thursday, Nov 02,2017 17:54:12 [Service blocked: ICMP_echo_req] from source 45.4.114.140, Thursday, Nov 02,2017 17:54:11 [Service blocked: ICMP_echo_req] from source 187.19.243.30, Thursday, Nov 02,2017 17:54:10 [Service blocked: ICMP_echo_req] from source 212.232.42.192, Thursday, Nov 02,2017 17:53:35 [Service blocked: ICMP_echo_req] from source 188.217.237.133, Thursday, Nov 02,2017 17:53:32 [Service blocked: ICMP_echo_req] from source 188.238.63.27, Thursday, Nov 02,2017 17:53:29 [Service blocked: ICMP_echo_req] from source 84.117.194.149, Thursday, Nov 02,2017 17:53:28 [Service blocked: ICMP_echo_req] from source 124.197.66.149, Thursday, Nov 02,2017 17:53:28 [Service blocked: ICMP_echo_req] from source 118.172.180.54, Thursday, Nov 02,2017 17:53:27 [Service blocked: ICMP_echo_req] from source 36.22.11.90, Thursday, Nov 02,2017 17:53:25 [Service blocked: ICMP_echo_req] from source 46.1.10.200, Thursday, Nov 02,2017 17:53:25 [Service blocked: ICMP_echo_req] from source 104.244.227.124, Thursday, Nov 02,2017 17:52:43 [Service blocked: ICMP_echo_req] from source 95.43.31.224, Thursday, Nov 02,2017 17:52:41 [Service blocked: ICMP_echo_req] from source 190.80.107.33, Thursday, Nov 02,2017 17:52:40 [Service blocked: ICMP_echo_req] from source 84.1.184.90, Thursday, Nov 02,2017 17:52:02 [Service blocked: ICMP_echo_req] from source 186.78.205.137, Thursday, Nov 02,2017 17:52:00 [Service blocked: ICMP_echo_req] from source 178.121.31.23, Thursday, Nov 02,2017 17:51:58 [Service blocked: ICMP_echo_req] from source 186.248.152.82, Thursday, Nov 02,2017 17:51:55 [Service blocked: ICMP_echo_req] from source 37.210.45.64, Thursday, Nov 02,2017 17:51:15 [Service blocked: ICMP_echo_req] from source 93.73.80.206, Thursday, Nov 02,2017 17:51:14 [Service blocked: ICMP_echo_req] from source 46.116.60.63, Thursday, Nov 02,2017 17:51:11 [Service blocked: ICMP_echo_req] from source 110.37.221.34, Thursday, Nov 02,2017 17:51:10 [Service blocked: ICMP_echo_req] from source 167.60.223.214, Thursday, Nov 02,2017 17:51:10 [Service blocked: ICMP_echo_req] from source 92.72.1.45, Thursday, Nov 02,2017 17:50:27 [Service blocked: ICMP_echo_req] from source 188.135.12.231, Thursday, Nov 02,2017 17:50:27 [Service blocked: ICMP_echo_req] from source 186.251.112.250, Thursday, Nov 02,2017 17:50:26 [Service blocked: ICMP_echo_req] from source 134.90.247.191, Thursday, Nov 02,2017 17:50:26 [Service blocked: ICMP_echo_req] from source 68.45.54.45, Thursday, Nov 02,2017 17:50:26 [Service blocked: ICMP_echo_req] from source 196.50.192.51, Thursday, Nov 02,2017 17:49:47 [Service blocked: ICMP_echo_req] from source 192.40.89.36, Thursday, Nov 02,2017 17:49:42 [Service blocked: ICMP_echo_req] from source 138.0.93.181, Thursday, Nov 02,2017 17:49:39 [Service blocked: ICMP_echo_req] from source 89.250.167.55, Thursday, Nov 02,2017 17:48:58 [Service blocked: ICMP_echo_req] from source 168.232.240.26, Thursday, Nov 02,2017 17:48:56 [Service blocked: ICMP_echo_req] from source 212.3.141.148, Thursday, Nov 02,2017 17:48:55 [Service blocked: ICMP_echo_req] from source 170.84.204.6, Thursday, Nov 02,2017 17:48:54 [Service blocked: ICMP_echo_req] from source 177.190.69.15, Thursday, Nov 02,2017 17:48:54 [Service blocked: ICMP_echo_req] from source 188.232.125.7, Thursday, Nov 02,2017 17:48:13 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 17:48:08 [Service blocked: ICMP_echo_req] from source 86.126.187.152, Thursday, Nov 02,2017 17:47:27 [Service blocked: ICMP_echo_req] from source 62.148.129.83, Thursday, Nov 02,2017 17:47:26 [Service blocked: ICMP_echo_req] from source 188.98.199.132, Thursday, Nov 02,2017 17:47:25 [Service blocked: ICMP_echo_req] from source 176.59.17.0, Thursday, Nov 02,2017 17:47:25 [Service blocked: ICMP_echo_req] from source 176.122.51.6, Thursday, Nov 02,2017 17:47:25 [Service blocked: ICMP_echo_req] from source 188.232.125.7, Thursday, Nov 02,2017 17:46:47 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 17:46:44 [Service blocked: ICMP_echo_req] from source 188.232.125.7, Thursday, Nov 02,2017 17:46:25 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 17:46:25 [Service blocked: ICMP_echo_req] from source 218.56.181.1, Thursday, Nov 02,2017 17:45:56 [Service blocked: ICMP_echo_req] from source 188.208.20.165, Thursday, Nov 02,2017 17:45:56 [Service blocked: ICMP_echo_req] from source 46.63.248.54, Thursday, Nov 02,2017 17:45:53 [Service blocked: ICMP_echo_req] from source 78.30.249.51, Thursday, Nov 02,2017 17:45:09 [Service blocked: ICMP_echo_req] from source 178.80.24.169, Thursday, Nov 02,2017 17:45:08 [Service blocked: ICMP_echo_req] from source 176.210.197.47, Thursday, Nov 02,2017 17:45:07 [Service blocked: ICMP_echo_req] from source 80.203.118.43, Thursday, Nov 02,2017 17:45:07 [Service blocked: ICMP_echo_req] from source 62.68.131.248, Thursday, Nov 02,2017 17:45:06 [Service blocked: ICMP_echo_req] from source 92.113.50.32, Thursday, Nov 02,2017 17:44:25 [Service blocked: ICMP_echo_req] from source 188.232.125.7, Thursday, Nov 02,2017 17:44:24 [Service blocked: ICMP_echo_req] from source 82.235.103.196, Thursday, Nov 02,2017 17:44:24 [Service blocked: ICMP_echo_req] from source 190.198.143.145, Thursday, Nov 02,2017 17:44:22 [Service blocked: ICMP_echo_req] from source 46.72.110.11, Thursday, Nov 02,2017 17:44:21 [Service blocked: ICMP_echo_req] from source 212.198.156.157, Thursday, Nov 02,2017 17:44:20 [Service blocked: ICMP_echo_req] from source 217.150.59.62, Thursday, Nov 02,2017 17:44:20 [Service blocked: ICMP_echo_req] from source 194.48.218.246, Thursday, Nov 02,2017 17:44:19 [Service blocked: ICMP_echo_req] from source 2.137.169.78, Thursday, Nov 02,2017 17:44:19 [Service blocked: ICMP_echo_req] from source 14.232.174.11, Thursday, Nov 02,2017 17:44:19 [Service blocked: ICMP_echo_req] from source 190.40.238.11, Thursday, Nov 02,2017 17:44:18 [Service blocked: ICMP_echo_req] from source 156.222.40.220, Thursday, Nov 02,2017 17:44:18 [Service blocked: ICMP_echo_req] from source 118.44.38.218, Thursday, Nov 02,2017 17:43:41 [Service blocked: ICMP_echo_req] from source 212.197.154.8, Thursday, Nov 02,2017 17:43:38 [Service blocked: ICMP_echo_req] from source 197.35.173.198, Thursday, Nov 02,2017 17:43:38 [Service blocked: ICMP_echo_req] from source 81.88.144.58, Thursday, Nov 02,2017 17:43:37 [Service blocked: ICMP_echo_req] from source 197.243.45.198, Thursday, Nov 02,2017 17:43:35 [Service blocked: ICMP_echo_req] from source 179.187.138.232, Thursday, Nov 02,2017 17:43:35 [Service blocked: ICMP_echo_req] from source 103.93.95.80, Thursday, Nov 02,2017 17:43:34 [Service blocked: ICMP_echo_req] from source 85.115.173.198, Thursday, Nov 02,2017 17:43:33 [Service blocked: ICMP_echo_req] from source 59.120.139.200, Thursday, Nov 02,2017 17:43:33 [Service blocked: ICMP_echo_req] from source 77.224.40.67, Thursday, Nov 02,2017 17:43:33 [Service blocked: ICMP_echo_req] from source 84.129.232.16, Thursday, Nov 02,2017 17:42:49 [Service blocked: ICMP_echo_req] from source 82.247.238.199, Thursday, Nov 02,2017 17:42:49 [Service blocked: ICMP_echo_req] from source 74.79.64.205, Thursday, Nov 02,2017 17:42:48 [Service blocked: ICMP_echo_req] from source 172.249.231.112, Thursday, Nov 02,2017 17:42:06 [Service blocked: ICMP_echo_req] from source 178.164.141.81, Thursday, Nov 02,2017 17:41:22 [Service blocked: ICMP_echo_req] from source 212.25.54.8, Thursday, Nov 02,2017 17:41:22 [Service blocked: ICMP_echo_req] from source 104.223.95.2, Thursday, Nov 02,2017 17:41:21 [Service blocked: ICMP_echo_req] from source 106.215.221.38, Thursday, Nov 02,2017 17:41:20 [Service blocked: ICMP_echo_req] from source 89.239.154.103, Thursday, Nov 02,2017 17:40:36 [Service blocked: ICMP_echo_req] from source 176.124.160.115, Thursday, Nov 02,2017 17:40:35 [Service blocked: ICMP_echo_req] from source 188.232.125.7, Thursday, Nov 02,2017 17:39:54 [Service blocked: ICMP_echo_req] from source 176.10.115.141, Thursday, Nov 02,2017 17:39:50 [Service blocked: ICMP_echo_req] from source 109.252.108.16, Thursday, Nov 02,2017 17:39:10 [Service blocked: ICMP_echo_req] from source 81.184.183.65, Thursday, Nov 02,2017 17:39:07 [Service blocked: ICMP_echo_req] from source 218.51.72.9, Thursday, Nov 02,2017 17:39:06 [Service blocked: ICMP_echo_req] from source 51.174.113.150, Thursday, Nov 02,2017 17:39:06 Modem log off by an hour Thu Nov 02 17:11:49 2017 Notice (6) Honoring MDD; IP provisioning mode = IPv6 Thu Nov 02 17:11:39 2017 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=fc:4a:e9:32... Thu Nov 02 17:11:26 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un... Thu Nov 02 17:07:06 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ... Thu Nov 02 17:06:50 2017 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream ... Thu Nov 02 17:06:50 2017 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries... Thu Nov 02 17:06:50 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ... Thu Nov 02 17:06:31 2017 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream ... Thu Nov 02 17:06:31 2017 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries... Thu Nov 02 17:06:31 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ... Thu Nov 02 10:35:01 2017 Notice (6) Honoring MDD; IP provisioning mode = IPv6 Thu Nov 02 10:34:49 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un... Thu Nov 02 10:30:29 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ... Thu Nov 02 10:23:41 2017 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream ... Crap almost lost the post just happened again.

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 this (now closed) topic > 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

Installed Ring Spotlight cams a few weeks back. Frustrated with video capture lag. Have been suspecting local LAN issues and have working with "Networking" forum on LAN improvement solutions. BUT.......two days of TRACERT tests to RING.com suggest maybe something different. Consistent lag at COMCAST TX and CA hubs? Have all west coast backbone issues been completely addressed???? :huh:

I know this modem is getting kind of old but it got a new firmware update last night! Firmware Name: TS0901103M2S_031317_MODEL_7_8_PC20_CT Firmware Build Time: Mon Mar 13 07:00:33 EDT 2017

FYI - A new version of CM1000 firmware, V3.01.02, has been initially released by Netgear for a field soak before being made GA: https://www.dslreports.com/forum/r31609929-

FYI - Saw this thread in the https://www.dslreports.com/forum/motorola forum about someone whose SB6141 modem started resetting often with lots of T3 and T4 timeout errors. It turned out that when he opened the unit up, "most of the capacitors on the board were bulged/leaking at the top." He replaced it with an SB6183 model and no problems since. https://www.dslreports.com/forum/r31699759-SB6141-bad-capacitors

I have been able up until a few days ago to log into my Technicolor at 192.168.100.1. I was able to do so through my router which I bought some time ago and which uses dd-wrt (I've only used the comcast provided R8000 for troubleshooting). It has allowed me to get to the login page of the modem without having to make a direct PC to modem cable connection to check out the signal strength. The other day when I tried, I got a certificate error and made a temporary exception to bypass that (not that I think that is great) and did get to the login password prompt. I have used 3 different browsers and all act the same. I put the default info into the box and got an error. Note: I have been using the default login and password because it was not changeable on the modem as there were no buttons to click on the modem pages to make such a change. Evidently, something has been changed in the modem. While I know there is a possibility of being hacked (and I know that it would absolutely would have to be from the outside if that is the case), I believe that there may have been a firmware update that has caused this problem with both the certificate and the login issue. What I would like to know if there is anyone who has been able to log into the modem and if there is a problem now or if it still works. I would also like to know if anyone knows if the firmware has been modified in the last week or so. I do know that comcast knows that I can log into the modem because I had an issue and spoke with technical support and then had a tech come over who saw the screens when I showed him. This login problem started about 2 weeks after the tech came over. Any help would be appreciated.

Hi, My "Xfinity (My Account)" App (iOS) has, for at least the last week probably longer, been saying there is an outage reported on both TV and Internet. I can't verify TV as I don't use it but the Internet is fine save the bogus indicator on the iPhone App. With the App thinking there is an outage the App won't let me restart the modem. It won't even try. I can connect to the modem via 192.168.100.1 just fine. The Status and Log pages are exemplary. My only recourse is to power cycle the modem to reboot it. I don't like power cycling devices if it can be done via software. So how do I convince the iPhone App that there are no outages? I'm in a near north suburb of Chicago which is suppose to get a speed bump soon so I'd like to reboot the modem periodically (without power cycling). Thanks, J