Welcome to Vodafone Community
Why cant I connect to the StackOverflow.com website using the mobile wifi broadband. The site itself is functioning correctly but cannot be accessed when using my mobile wifi as internet connectivity. Its not a browser issue as I can connect if I drop back to my home based crappy BT broadband box
I've also been having this issue since yesterday, not only blocking StackOverflow but also my personal website hosted on GitHub but served via Cloudflare.
I've raised this with support at Vodafone but wasn't really given much in terms of response other than it will be raised with 3rd line technical support and responded to within 2-3 days.
Hopefully, this issue will be resolved sooner rather than later as I am working from home currently and StackOverflow tends to be quite useful in my day-to-day job.
Ah right cheers, Thats exactly why I would like access to StackOverflow, its a vital tool for the developer. We tend to use Devops rather than Github so no such issues for me there. Hope they both get resolved soon
I'm also unable to connect to Stack Overflow or any of the Stack Exchange sites.
Glad to see that others are too as I couldn't figure it out whatsoever.
Vodafone - please fix this urgently! It's a nightmare trying to work without it
I have same issue!
Just talked with Vodafone support and she raised the issue saying it will be solved by 72 hours.
Let's wait and see when they will give us back our Stackoverflow!
Same issue here, on my Vodafone home broadband though. I don't have Vodafone mobile.
Spent a while with the online support chat today. They just went through the usual personal content filtering options, but it's not that.
DNS is fine. I can also ping the sites.
However, no web pages are being served. There's clearly a content block happening at the Vodafone servers.
All of the sites that are useful to a developer appear to be having trouble.
stackoverflow, askubuntu, etc..
Replying here too just to highlight this is also affecting me in the South East. Like the others I cannot connect to Stack Exchange and Stack Overflow sites.
It's been 2 days now, this really needs fixing asap.
Just a bit more info:
As well as all the StackExchange/Github sites, Open University (open.ac.uk) was also affected, but that started working again about 4 hours ago - hopefully the others will soon follow suit. This isn't a DNS issue - I've set up my wifi hub to use OpenDNS and then tried Quad9 DNS and that made no difference. All these sites are easily accessible with any other ISP/mobile data. There's been a fair amount of noise on Twitter about this over the last day or two - loads of people affected.
There's another thread with the cause here.
There must be so many support requests saying the same thing, I am surprised this hasn't been triaged.
I am having the exact same issue since yesterday morning, get the below message. Have tried everything from resetting the modem, terminal command, restarting computer... it is the same problem on all browsers. Can only connect to stackoverflow on my phone with 4G. Hope this can be fixed soon??
This site can’t be reached
stackoverflow.com took too long to respond.
Thanks for linking. That routing loop certainly seems to be the issue; I see it too:
traceroute to www.stackoverflow.com (188.8.131.52), 30 hops max, 60 byte packets 1 <local> 0.401 ms 0.514 ms 0.657 ms 2 host-212-158-250-34.dslgb.com (184.108.40.206) 8.126 ms 8.457 ms 8.541 ms 3 220.127.116.11 (18.104.22.168) 10.613 ms 10.692 ms 10.782 ms 4 10.200.18.37 (10.200.18.37) 10.839 ms 10.904 ms 11.191 ms 5 22.214.171.124 (126.96.36.199) 11.397 ms 11.498 ms 11.810 ms 6 188.8.131.52 (184.108.40.206) 12.825 ms 9.721 ms 10.166 ms 7 10.200.18.37 (10.200.18.37) 10.333 ms 10.080 ms 10.146 ms 8 220.127.116.11 (18.104.22.168) 10.561 ms 9.839 ms 10.108 ms 9 22.214.171.124 (126.96.36.199) 10.780 ms 11.224 ms 11.231 ms 10 10.200.18.37 (10.200.18.37) 11.624 ms 11.244 ms 11.860 ms 11 188.8.131.52 (184.108.40.206) 11.780 ms 11.061 ms 11.057 ms 12 220.127.116.11 (18.104.22.168) 11.978 ms 12.133 ms 12.787 ms 13 10.200.18.37 (10.200.18.37) 12.573 ms 11.794 ms 11.860 ms 14 22.214.171.124 (126.96.36.199) 12.231 ms 12.071 ms 12.058 ms 15 188.8.131.52 (184.108.40.206) 12.609 ms 13.032 ms 12.947 ms 16 10.200.18.37 (10.200.18.37) 13.058 ms 13.568 ms 12.898 ms 17 220.127.116.11 (18.104.22.168) 13.481 ms 13.623 ms 13.542 ms 18 22.214.171.124 (126.96.36.199) 13.670 ms 13.904 ms 14.675 ms 19 10.200.18.37 (10.200.18.37) 13.575 ms 13.842 ms 13.779 ms 20 188.8.131.52 (184.108.40.206) 13.867 ms 14.128 ms 14.064 ms 21 220.127.116.11 (18.104.22.168) 15.015 ms 15.001 ms 15.144 ms 22 10.200.18.37 (10.200.18.37) 15.390 ms 14.800 ms 14.753 ms 23 22.214.171.124 (126.96.36.199) 14.764 ms 15.259 ms 15.186 ms 24 188.8.131.52 (184.108.40.206) 15.537 ms 15.599 ms 15.620 ms 25 10.200.18.37 (10.200.18.37) 15.614 ms 16.067 ms 16.287 ms 26 220.127.116.11 (18.104.22.168) 16.113 ms 15.967 ms 15.883 ms 27 22.214.171.124 (126.96.36.199) 16.541 ms 17.005 ms 16.988 ms 28 10.200.18.37 (10.200.18.37) 18.434 ms 18.886 ms 18.133 ms 29 188.8.131.52 (184.108.40.206) 17.614 ms 17.312 ms 16.900 ms 30 220.127.116.11 (18.104.22.168) 18.101 ms 17.506 ms 17.143 ms
In SE London - unable to connect to stackoverflow.com for two days now. Just moved into this flat with Vodafone internet, and never had a problem with any other ISP like this before. Not the best start! Just tweeted VodafoneUK to see when it's likely to be fixed. I'm an app developer and spend a lot of time on stack overflow every day, so this has slowed me right down. Really not happy!
Seems they are trying to build a big community of angry developers here :D,
I got a call from Vodafone today regarding my problem, which I missed! then I tried to call the number that I've been given and they played a full album of Amy Winehouse for me as of a present for my patient which was lovely, but then they dropped the call without solving my issue.
I NEEEEDDDDDD MMYYYY Stackoverflow!
Just replying as I'm having the same problem and wanted to add to this thread.
Where is a Vodafone representative on this thread?
Why hasn't there been any communication by Vodafone?
Why is this taking so long to fix?
This has been raised with Vodafone by an employee at StackOverflow as seen on twitter here. I believe they're now looking into the issue although taking their time.
It has also been raised by many annoyed Vodafone customers, mostly developers it seems, myself included.
As a quick solution I've taken to pasting StackOverflow URIs into a web based proxy, not a solution but a short term fix which I hope is a little help.