Bright House Networks - Legacy → Lightning pages hanging since Sunday, streaming not working

OK, I seem to have a problem with my lightning service, this started yesterday (sunday 16th Nov) afternoon. There is a long delay happening before requests are being processed. For example I click on a link in a website - nothing happens for 10-20 seconds or longer, it just hangs, then eventually it responds and works as normal. Sometimes it just stays hung. On my Apple TV some streaming channels have stopped working, they say 'no connection - try again later' , many web pages are just hanging. Netflix works fine. Once the connection is stablished it's fast as usual, ping is fast and so is download and upload speed, it's like my request is placed in a queue: the problem is this hanging or long delay before anything happens once a link is clicked or streaming channel selected. I have tried rebooting my router. I have not seen this behavior before.It was even difficult to post this thread, the pages just hanging. This is a definite problem, it's almost 3am, streaming channels are hanging and it's almost impossible to get web pages to respond. Just a note; when it eventually responds (if at all) it's very fast - I have just seen 131mbps download speed on my Lightning 90 service which leads me to suspect that they are introducing this new 150mbps service but the problem is that it's just not working properly, everything is hanging, some websites respond, others don't and streaming is not working. Thanks

This is happening here too (CFL/Ocoee/34761). Speed test shows 160/11.

It's fast when it eventually responds but it's very unreliable with it hanging like this . . . . .

I suspect the "problem" will go away soon. Whether we'll know what caused it, that's another story...
I'm just doing my normal insomniatic browsing. Pages that normally pop right up take several seconds to load.

I certainly hope this problem does just go away but it's been happening randomly since Sunday afternoon and on my end it's making the service difficult to use with streaming channels not connecting and many web pages just not responding. Fast is good but not at the expense of responsiveness and reliability.

I'm encountering the problem also, I think it is Brighthouse DNS. Below is some result from program DNSBench (192.168.1.1 is my router which uses DHCP to get DNS server)

65. 32. 1. 70 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.012 | 0.047 | 0.661 | 0.144 | 72.4 |
- Uncached Name | 0.015 | 0.614 | 0.793 | 0.291 | 57.1 |
- DotCom Lookup | 0.727 | 0.842 | 0.956 | 0.161 | 25.0 |
------+-------+-------+-------+-------+-------+

65. 32. 5.112 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.011 | 0.073 | 0.645 | 0.188 | 81.5 |
+ Uncached Name | 0.730 | 0.760 | 0.781 | 0.019 | 27.3 |
+ DotCom Lookup | 0.895 | 0.895 | 0.895 | 0.000 | 16.7 |
------+-------+-------+-------+-------+-------+

192.168. 1. 1 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.013 | 0.102 | 0.667 | 0.218 | 68.8 |
- Uncached Name | 0.779 | 0.779 | 0.779 | 0.000 | 4.5 |
- DotCom Lookup | - | - | - | - | - |
------+-------+-------+-------+-------+-------+
Local Network Nameserver

65. 32. 5.111 | The DNS server at this IP address does
not provide domain name service answering client queries.
It should not be used for normal client-based resolution.
------+-------+-------+-------+-------+-------+

65. 32. 1. 65 | DNS queries are not answered at this IP.
------+-------+-------+-------+-------+-------+

Normal results should be more like the alternative DNS below

208. 67.222.222 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.012 | 0.014 | 0.016 | 0.001 | 100.0 |
- Uncached Name | 0.014 | 0.079 | 0.317 | 0.074 | 100.0 |
- DotCom Lookup | 0.013 | 0.049 | 0.126 | 0.036 | 100.0 |
------+-------+-------+-------+-------+-------+

8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.025 | 0.028 | 0.049 | 0.004 | 100.0 |
- Uncached Name | 0.027 | 0.081 | 0.236 | 0.056 | 100.0 |
- DotCom Lookup | 0.040 | 0.069 | 0.150 | 0.027 | 100.0 |
------+-------+-------+-------+-------+-------+

We've been having the same issue. Melbourne/CFL Speed tests are ok but it's getting hung up somewhere. 30/2 lighting, newest time capsule/Airport Extreme. ETA tested directly from modem. Issue still happened.

I would suggest changing your DNS to either Google DNS 8.8.8.8 / 8.8.4.4 or Open DNS 208.67.222.222 / 208.67.220.220 and see if the problem persists.

Guys before I send this up I need specifics on each of your modems in direct please. If this makes you feel any better I notice some issues yesterday with some off-net apps and I do NOT use our DNS....so I doubt it was DNS related.

I am not posting in direct, because the problem seems to have resolved itself in the last couple hours. Sorry but when there is a problem with Brighthouse DNS primary nameserver response / secondary nameserver reliability (but not a problem reaching off-net sites such as alternative DNS servers), we have no obvious tool to figure out whether it is just a Brighthouse DNS problem as opposed to some other problem such as whatever "network" that Brighthouse's servers are on.

Then I can't help you....when and if you change your mind let me know.

I don't have a problem anymore, stuff pops up immediately, no issues with streaming. I had an issue between 3AM & 4AM (don't know WHEN it "fixed" itself, I went back to bed @ 4) If you still want a direct post from me, what do you want besides the usual?

Okay what was the observed timeframe then....from each of you....(Day and Time), if current state such. Also if your username does not tag to your location you need to include that as well...you can do it here...not needed in direct.

Hi, It's intermittent because it's actually OK at the moment, I have the Brighthouse supplied Modem SB6141 Motorola. I posted a group message on my neighborhoods Facebook group and have had replies this morning that others have been experiencing exactly the same thing. My Zip Code is 32836 - Thornhill Subdivision off Reams Road - I first noticed the problem Sunday mid afternoon, it improved for a while and just appeared to be slow at responding and then last night 2.40am started hanging badly again, now this morning it's OK again. Thanks!

By the way I checked Netflix WHILE it was happening yesterday (because I understand Netflix has priority bandwidth?) and the problem didn't seem to be affecting Netflix, it loaded straight away while other streams and web pages were still hanging.

Yes, it definitely seems sporadic. It was bad yesterday afternoon (started around 3:00 I think), seemed to resolve itself yesterday evening and then was back early this morning (was up around 5:00 AM). Right before I left for work (7:45 AM) things seemed to have settled down once again (my husband was streaming Sirius and was able to surf the web). I did post earlier in direct because Gary asked. I'm not sure if there is a current issue because I am at work, but I haven't heard anything from my husband, so I am guessing it's still ok.

3AM to 4AM 17 November, websites would take up to 10-15 seconds to load-though when they did, they'd pop right up. Stuttering streaming for videos from assorted news sites. Sorry I can't tell you specific web sites, except Drudge-including linked sites from it, Foxnews, local news sites (Orlando market). When I tested the speed ( »speedtest.bhn.net/ ), it took 10 seconds for that page to load, this was shortly after 3AM when I did the speed test. The test was 160/11 when I did the test. No problems at all now.

On a side note, I feel like I'm wining when complain about a few seconds, then remember back in the days of dial-up...

Dont know if this is related or helps but I was watching wtvt live stream and it hung up sometime between 9:30 am and 9:45 am today.
I had to reload the site to get it working.

This had happened yesterday evening. I just chalked it up to a problem with their site. Never had it happen before yesterday.

I concur, exact same with me, around 3pm yesterday, sporadic and then bad again like 2.40am but OK now

Majority of you are from CFL and the timing matches an event in your area yesterday. It is possible I too traversed that path yesterday. Soooo for now... this will be on my watch list for now...

Thanks, Gary!

Thanks - BTW: It may be unconnected but I have been running some speed tests in the last 10 minutes and the maximum download speed is only about 40mbps with ping slower at 30ms. Earlier today I was seeing around 130mbps download with ping of 20ms or slightly less.

It may be worth mentioning that also yesterday afternoon, a couple of hours before the hanging issue, there was an electrical power cut that lasted a few seconds, I had to reset all the clocks in the house etc. Yes I'm in Central Florida, SW Orlando - Thanks

I have nothing in direct from you....so can't take a peek.

Hi, download speed has now dropped to between 5mbps to 10mbps, with 30ms ping - can you please let me know how to report it to you? Thanks

Click this link for BHN Direct »/fo ··· sedirect
Post your Cable Modem's CM MAC Address not here but in the Direct post so BHN Staff can pull up your info......

Thanks it's actually OK again now but I will keep an eye on it and do that if the problem re-appears.

Let me know guys...I'm here and watching don't worry.

I'm unclear whether you want report back here now rather than direct (my CM MAC is in direct from earlier today).
Around 1:17pm 11/17, the problem which I describe as Brighthouse DNS problem is occurring again. Brighthouse DNS are unreliable or not responding, off-net DNS are working fine.
192.168.1.1 is my Netgear router using DHCP (111/112).
Note: I realize that two of the DNS are for business customers - I sometimes test at my church so those two are in the list.

208. 67.222.222 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.013 | 0.016 | 0.029 | 0.004 | 100.0 |
- Uncached Name | 0.014 | 0.080 | 0.242 | 0.063 | 100.0 |
- DotCom Lookup | 0.047 | 0.061 | 0.086 | 0.015 | 100.0 |
------+-------+-------+-------+-------+-------+

208. 67.220.220 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.014 | 0.017 | 0.029 | 0.003 | 100.0 |
- Uncached Name | 0.015 | 0.083 | 0.361 | 0.076 | 100.0 |
- DotCom Lookup | 0.045 | 0.078 | 0.124 | 0.036 | 100.0 |
------+-------+-------+-------+-------+-------+

8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.025 | 0.030 | 0.047 | 0.006 | 100.0 |
- Uncached Name | 0.026 | 0.079 | 0.278 | 0.067 | 100.0 |
- DotCom Lookup | 0.041 | 0.078 | 0.153 | 0.034 | 100.0 |
------+-------+-------+-------+-------+-------+

8. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.036 | 0.046 | 0.146 | 0.020 | 100.0 |
- Uncached Name | 0.039 | 0.094 | 0.308 | 0.070 | 100.0 |
- DotCom Lookup | 0.048 | 0.071 | 0.133 | 0.024 | 100.0 |
------+-------+-------+-------+-------+-------+

192.168. 1. 1 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.015 | 0.073 | 0.722 | 0.177 | 58.8 |
- Uncached Name | 0.480 | 0.480 | 0.480 | 0.000 | 10.0 |
- DotCom Lookup | - | - | - | - | - |
------+-------+-------+-------+-------+-------+
Non-routable local internet address
Local Network Nameserver

65. 32. 1. 70 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.012 | 0.089 | 0.657 | 0.192 | 72.2 |
- Uncached Name | 0.013 | 0.332 | 0.770 | 0.312 | 52.2 |
- DotCom Lookup | 0.014 | 0.338 | 0.738 | 0.319 | 50.0 |
------+-------+-------+-------+-------+-------+
dns-comm-cac-lb-02.tampflrdc.rr.com

65. 32. 5.111 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.013 | 0.117 | 0.714 | 0.240 | 64.5 |
+ Uncached Name | 0.014 | 0.303 | 0.653 | 0.302 | 45.0 |
+ DotCom Lookup | 0.087 | 0.560 | 1.023 | 0.386 | 55.6 |
------+-------+-------+-------+-------+-------+
dns-redir-lb-01.tampabay.rr.com

65. 32. 5.112 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.013 | 0.118 | 0.644 | 0.215 | 85.7 |
+ Uncached Name | 0.035 | 0.558 | 0.725 | 0.210 | 47.6 |
+ DotCom Lookup | 0.607 | 0.658 | 0.726 | 0.050 | 50.0 |
------+-------+-------+-------+-------+-------+
dns-redir-lb-02.tampabay.rr.com

65. 32. 1. 65 | The DNS server at this IP address does
not provide domain name service answering client queries.
It should not be used for normal client-based resolution.
------+-------+-------+-------+-------+-------+

I have been having the same issue since last night, it's very intermittent. I have been trying to pinpoint the issue but no luck so far.

I'm not chasing this as a DNS issue guys because nothing I have at the moment points in that direction and the vast majority of you were CFL that was impacted by a different event last night.

That could change later but right now I'm comfortable with most of you having impact from the known issue.