Skip to main content

    Support

    Offers

mcb318's profile
mcb318
1st Topic

Visitor

 • 

2 Messages

Monday, July 31st, 2023 11:32 AM

Closed

AWS Kinesis issue

I have a Phyn Plus water shutoff and it sends data properly for anywhere from a few hours to a day but then I receive a message saying that it  is not able to send data. The Phyn troubleshooting page says the following -

  • The ISP modem/router provided to you by your ISP has default DNS settings that block data uploads to AWS Kinesis – kinesis.us-east-1.amazonaws.com
    • Note:  Some newer models of Cox and Comcast xFinity routers have experienced this issue.

I have done all of their problem resolution steps, same issue. It has worked fine for almost a year until a few months ago. Is there an issue with xfinity and AWS east. I did see in other posts some gamers are having issues as well. Thanks

Question

 • 

Updated 

2 years ago

99

1

0

flatlander3

Problem Solver

 • 

1.5K Messages

2 years ago

This one is kind of interesting.  Kinesis is part of AWS telemetry/data analytics.  There's nothing technically wrong with the dns entry, but 76 (dot )76....... doesn't resolve it at all my market, and 75(dot)75.......will throw a timeout on it.  Google, cloudflare and other public DNS are fine with it.

I'm not sure disabling advanced security would do anything for you either.  Seems intentional, something more like a global ad block, and you wouldn't be able to do anything about it with xfinity equipment with locked DNS settings.  

Don't even know where you would report a DNS issue.  Someplace like security here? (report blocked website link???) https://internetsecurity.xfinity.com/help/report-abuse    Anyone have a better link?  I can see blocking things of this sort locally, but not globally on a network by default.

  

2

0

mcb318

Visitor

 • 

2 Messages

@flatlander3​ Hi, Yes, I have done several ways to get by this. I have the xfinity xb6 operating normally, I get the failure, I have my own netgear router with the xfinity in bridge mode, same problem. I have the DNS configured to use Level3, Google and cloudfare , same problem, I have an older netgear R7500 running dd-wrt and when that is in place, same problem. The device worked fine for about 8 months then the problem arose. I also forced the phyn device to use aws-west instead of aws-east, same problem. I tried a newer Phyn device before we installed it at my daughter's house, same problem with the new one, and finally, she has Verizon Fios stock setup, no issues at all it works fine at her house so it looks like it has to be something with xfinity. I doubt this will ever get resolved  until some sort of change is made somewhere in the network and it will start working again

2 years ago

0

flatlander3

Problem Solver

 • 

1.5K Messages

@mcb318​  For me, bridge mode using cloudflare, google or afraid.org public dns, no problem with two different comcast locations in two states in the upper midwest, or on a backbone in with a commercial host in Colorado using them as a forwarder. It's just the comcast servers that come up empty.

Dunno.  Seems odd.  Net nanny perhaps like cloud edge blocking it?

2 years ago

0

forum icon

New to the Community?

Start Here