Hello,
For the last few days connections to https://www.redpocket.com/ have been timing out, and therefore have called customer service. Their final advice was to contact Redpocket myself about the issue, even after they admitted that several other Sonic subscribers have been impacted, and even after I tried to explain the likely cause of the problem to them. I don't think I should be doing this on behalf of Sonic, though, please see below why.
Customer service helpfully determined, however, that Redpocket must be blocking my IP address, and the issue is not with my equipment, or on Sonic's end. After doing a little research, this is what I've found:
1. Running a traceroute to redpocket.com indeed reveals that the trace leaves Sonic's network, and gets blocked thereafter.
2. Running a DNS lookup for redpocket.com's IP addresses reveals that they are served by AWS. See https://mxtoolbox.com/SuperTool.aspx?ac ... n=toolpage . Therefore I think it's possible that the IP blocking is happening as part of Amazon's infrastructure, which gives me even less motivation to try to solve the issue myself by somehow getting in touch with Redpocket's internal technical teams.
3. Checking blacklist providers whether my IP address may be listed served up something, for instance: https://dnschecker.org/ip-blacklist-che ... .180.170.1 (this is not my actual IP address, I changed the last two bytes, but it's close enough). According to this, dnsbl.spfbl.net has the IP address range on its blacklist, and indeed going to https://matrix.spfbl.net/en/135.180.170.1 confirms the listing.
So my potential explanation is that Amazon is checking the blacklist providers, finds my IP address (and apparently several others in this range) on one list, and blocks access to https://www.redpocket.com/ .
My question is this: is it reasonable to assume that the blocking is caused by the blacklisting above? And if so, is it reasonable for Sonic to expect me to contact Redpocket, possibly Amazon, and if the blacklisting is the cause, spfbl.net (who btw would likely bounce me back to Sonic)? Also, besides Redpocket, other destinations may be unreachable as well, if the assumptions above are true.
I'm not sure that customer service's other suggestion, to shut down the ONT device for a few hours to acquire a new IP address would help, as it's possible I'd still get a similar IP address to the current one, which will also be listed.
Thank you very much!
For the last few days connections to https://www.redpocket.com/ have been timing out, and therefore have called customer service. Their final advice was to contact Redpocket myself about the issue, even after they admitted that several other Sonic subscribers have been impacted, and even after I tried to explain the likely cause of the problem to them. I don't think I should be doing this on behalf of Sonic, though, please see below why.
Customer service helpfully determined, however, that Redpocket must be blocking my IP address, and the issue is not with my equipment, or on Sonic's end. After doing a little research, this is what I've found:
1. Running a traceroute to redpocket.com indeed reveals that the trace leaves Sonic's network, and gets blocked thereafter.
2. Running a DNS lookup for redpocket.com's IP addresses reveals that they are served by AWS. See https://mxtoolbox.com/SuperTool.aspx?ac ... n=toolpage . Therefore I think it's possible that the IP blocking is happening as part of Amazon's infrastructure, which gives me even less motivation to try to solve the issue myself by somehow getting in touch with Redpocket's internal technical teams.
3. Checking blacklist providers whether my IP address may be listed served up something, for instance: https://dnschecker.org/ip-blacklist-che ... .180.170.1 (this is not my actual IP address, I changed the last two bytes, but it's close enough). According to this, dnsbl.spfbl.net has the IP address range on its blacklist, and indeed going to https://matrix.spfbl.net/en/135.180.170.1 confirms the listing.
So my potential explanation is that Amazon is checking the blacklist providers, finds my IP address (and apparently several others in this range) on one list, and blocks access to https://www.redpocket.com/ .
My question is this: is it reasonable to assume that the blocking is caused by the blacklisting above? And if so, is it reasonable for Sonic to expect me to contact Redpocket, possibly Amazon, and if the blacklisting is the cause, spfbl.net (who btw would likely bounce me back to Sonic)? Also, besides Redpocket, other destinations may be unreachable as well, if the assumptions above are true.
I'm not sure that customer service's other suggestion, to shut down the ONT device for a few hours to acquire a new IP address would help, as it's possible I'd still get a similar IP address to the current one, which will also be listed.
Thank you very much!