Xfinity blocking SAS airlines website and request to unblock going unanswered after a week

As a possible temporary workaround, you could try disabling their Advanced Security feature and see;

https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security 

OK, good luck with it !

@user_wcapvw wrote: "I reported the website flysas.com as being blocked ..."

I can reach the site using Comcast's internet ("Welcome to the world of SAS"). What happens when you try to reach it? Any error messages?

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

... The request is blocked ...

Hmmmm. What does a trace to flysas.com show? In Windows, open a Command Prompt window, enter

    tracert -4 flysas.com

and post the output. Mine looks like:

C>tracert -4 flysas.com

Tracing route to flysas.com [66.22.34.74] over a maximum of 30 hops:

   1     1 ms    <1 ms    <1 ms  router1 [192.168.1.1]
   2     9 ms      8 ms       8 ms  96.120.9.181
   3     9 ms      8 ms       9 ms  po-301-1203-rur01.york.pa.pitt.comcast.net [24.124.216.181]
   4     9 ms      8 ms       8 ms  po-2-rur02.york.pa.pitt.comcast.net [96.110.24.214]
   5    10 ms    19 ms     10 ms  be-87-rar01.lancaster.pa.pitt.comcast.net [96.110.25.65]
   6    18 ms    17 ms     18 ms  be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
   7    18 ms    19 ms        *       be-31631-cs03.pittsburgh.pa.ibone.comcast.net [96.110.42.169]
   8    26 ms    26 ms     26 ms  be-3211-pe11.ashburn.va.ibone.comcast.net [96.110.32.126]
   9    26 ms    27 ms     26 ms  ash-b2-link.ip.twelve99.net [62.115.51.193]
 10    38 ms    27 ms     28 ms  ash-bb2-link.ip.twelve99.net [62.115.123.124]
 11    28 ms    28 ms     28 ms  nyk-bb2-link.ip.twelve99.net [62.115.136.200]
 12     *          104 ms   101 ms  ldn-bb1-link.ip.twelve99.net [62.115.113.21]
 13   101 ms  101 ms      *         slou-b2-link.ip.twelve99.net [62.115.127.7]
 14   100 ms  102 ms   101 ms  radware-ic-369403.ip.twelve99-cust.net [62.115.35.181]
 15      *            *             *         Request timed out.
 16   103 ms  104 ms   103 ms  66.22.34.74

Trace complete.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Since your trace shows you are reaching the target site, chances are that's where the "request is blocked" message is coming from. The site or its webhost is most likely blocking your public Comcast IP. You can look up your IP at https://www.google.com/search?q=what+is+my+IP. You'll need to ask the site's admins for help with this. In many cases they don't even know that their systems do IP blocking, so this may not be easy.

Good luck!

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

@BruceW 

Look at all those routing loops ! 😮

... Look at all those routing loops ! ...

My guess was that those were probably a traceroute artifact, but maybe not?

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Beats me.... Just sayin'.

4 and 5, 6 and 7, 8 and 9 are numerically different hops but with the same IP's. Something is going on there.

At the second hop in the trace the path appears to split in two directions, 10.a.b.2 and 10.a.b.3, which we note, are more of those mysterious Comcast private IPs. The split persists in hop three, which consists of 96.c.d.217 and 96.c.d.177. My guess is that this split continues through the rest of the trace, with one path a step ahead of the other, and that the result is apparent routing loops.

But "guess" is the key word in that paragraph.  😉  (Apologies to the OP for this digression).

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Yes. Apologies. But it may not be a "digression". It's pointing out another issue that may or may not be related to the initial issue. Something that the Comcast network engineers should be made aware of.

Howdy user_wcapvw!

This style concern would traditionally flow through our CSA team. Is that who you had contacted? That is our online security team, they are awesome! The Customer Security Assurance organization has been established to ensure a safe and secure online experience for Comcast customers. This team is a dedicated group of security professionals who respond to issues pertaining to phishing, spam, infected computers (commonly referred to as bots), online fraud and other security issues.

• Business Hours: 8:00am - 12:00am EST, 7 days a week
• Contact: 1-888-565-4329

https://internetsecurity.xfinity.com/help/report-abuse

It is quite remarkable how many people I have spoken to within the Xfinity/Comcast network who want to help but are not able to because they are Tier 1 customer support.  I am up to 10 people and 4 hours on the phone over the course of three days.  No one is responding to direct messaging.  I've identified two points of failure at this point.  The first, is that after submitting the online form with details on what site I request access to and receiving an email confirmation it was received, there is no tracking number assigned to the request.  Second, there is no POC provided to follow up with directly for a status update on the submitted form.  

... I spoke with the CSR team today for almost an hour and was told they cannot help ...

If, as appears to be the case, the "request is blocked" message is coming from the site or its webhost, Comcast/Xfinity CSA will not be able to help you. You need to be working with the entity doing the blocking.

This is happening to me as well. So frustrating... unable to open the SAS site to look at my flight status.  This is simply awful!