O2's Tu Go service No call volume on incoming or outgoing calls

[#1]

Try this command
nmap -Pn -p 80 --traceroute www.nyc-architecture.com
Here are my results:

Quote

Starting Nmap 5.21 ( http://nmap.org ) at 2014-04-22 18:41 BST Nmap scan report for www.nyc-architecture.com (66.96.132.67) Host is up (0.091s latency). rDNS record for 66.96.132.67: 67.132.96.66.static.eigbox.net PORT  STATE SERVICE 80/tcp open  http TRACEROUTE (using port 80/tcp) HOP RTT      ADDRESS 1  1.34 ms  router.asus.com (192.168.1.1) 2  36.24 ms lo0-central10.ptn-ag01.plus.net (195.166.128.190) 3  5.60 ms  link-b-central10.ptn-gw02.plus.net (212.159.2.130) 4  4.91 ms  xe-5-2-0.ptw-cr02.plus.net (212.159.0.106) 5  5.31 ms  ae2.ptw-cr01.plus.net (195.166.129.4) 6  5.09 ms  ae1.pcl-cr01.plus.net (195.166.129.1) 7  5.42 ms  ae-52-52.csw2.London1.Level3.net (4.69.139.120) 8  4.99 ms  ae-225-3601.edge3.London1.Level3.net (4.69.166.146) 9  6.71 ms  be3043.ccr22.lon01.atlas.cogentco.com (130.117.15.245) 10  11.54 ms ae-61-61.csw1.Paris1.Level3.net (4.69.161.78) 11  91.36 ms be2391.ccr22.bos01.atlas.cogentco.com (154.54.44.237) 12  91.15 ms endurance-international-group.demarc.cogentco.com (38.97.106.34) 13  15.04 ms be2313.mpd22.par01.atlas.cogentco.com (154.54.73.253) 14  14.34 ms be2272.ccr22.lon13.atlas.cogentco.com (130.117.49.121) 15  91.45 ms 67.132.96.66.static.eigbox.net (66.96.132.67)

Quote

Starting Nmap 5.21 ( http://nmap.org ) at 2014-04-22 18:41 BST Nmap scan report for voomka.com (192.163.208.88) Host is up (0.13s latency). rDNS record for 192.163.208.88: 192-163-208-88.unifiedlayer.com PORT  STATE SERVICE 80/tcp open  http TRACEROUTE (using port 80/tcp) HOP RTT      ADDRESS 1  1.37 ms  router.asus.com (192.168.1.1) 2  12.75 ms  lo0-central10.ptn-ag01.plus.net (195.166.128.190) 3  5.44 ms  link-a-central10.ptn-gw01.plus.net (212.159.2.128) 4  5.05 ms  xe-5-2-0.ptw-cr01.plus.net (212.159.0.104) 5  ... 6  73.76 ms  100ge1-1.core1.nyc4.he.net (72.52.92.166) 7  87.66 ms  100ge7-2.core1.chi1.he.net (184.105.223.161) 8  119.63 ms 10ge3-2.core1.den1.he.net (184.105.213.86) 9  133.50 ms 10ge4-2.core1.slc1.he.net (184.105.222.154) 10  174.64 ms ace-data-centers-inc.10gigabitethernet1-4.core1.slc1.he.net (66.160.133.118) 11  131.29 ms ve15.ar04.prov.acedc.net (199.58.196.65) 12  131.99 ms prv-211-1-1-1.unifiedlayer.com (69.27.175.145) 13  131.60 ms 192-163-208-88.unifiedlayer.com (192.163.208.88)

Quote

Starting Nmap 5.21 ( http://nmap.org ) at 2014-04-22 18:41 BST Nmap scan report for offgridquest.com (162.144.62.181) Host is up (0.13s latency). rDNS record for 162.144.62.181: server.campinglifequest.com PORT  STATE SERVICE 80/tcp open  http TRACEROUTE (using port 80/tcp) HOP RTT      ADDRESS 1  1.33 ms  router.asus.com (192.168.1.1) 2  25.23 ms  lo0-central10.ptn-ag01.plus.net (195.166.128.190) 3  5.35 ms  link-b-central10.ptn-gw02.plus.net (212.159.2.130) 4  6.73 ms  xe-5-2-0.ptw-cr02.plus.net (212.159.0.106) 5  5.10 ms  10gigabitethernet5-1.core1.lon1.he.net (5.57.80.128) 6  5.07 ms  10ge3-1.core1.lon2.he.net (72.52.92.222) 7  70.60 ms  100ge1-1.core1.nyc4.he.net (72.52.92.166) 8  88.14 ms  100ge7-2.core1.chi1.he.net (184.105.223.161) 9  116.89 ms 10ge3-2.core1.den1.he.net (184.105.213.86) 10  129.33 ms 10ge4-2.core1.slc1.he.net (184.105.222.154) 11  140.25 ms ace-data-centers-inc.10gigabitethernet1-4.core1.slc1.he.net (66.160.133.118) 12  140.14 ms ve15.ar04.prov.acedc.net (199.58.196.65) 13  132.31 ms prv-211-1-1-2.unifiedlayer.com (69.27.175.147) 14  132.48 ms server.campinglifequest.com (162.144.62.181)

[#2]

Ran the command as sudo and got the following:

Quote

Starting Nmap 6.46 ( http://nmap.org ) at 2014-04-22 18:44 BST Nmap scan report for www.nyc-architecture.com (66.96.132.67) Host is up. rDNS record for 66.96.132.67: 67.132.96.66.static.eigbox.net PORT  STATE    SERVICE 80/tcp filtered http TRACEROUTE (using proto 1/icmp) HOP RTT      ADDRESS 1  4.63 ms  10.0.1.1 2  23.45 ms  lo0-central10.pcl-ag02.plus.net (195.166.128.183) 3  22.98 ms  link-b-central10.pcl-gw02.plus.net (212.159.2.166) 4  23.48 ms  xe-10-1-0.pcl-cr02.plus.net (212.159.0.198) 5  23.50 ms  ae1.ptw-cr02.plus.net (195.166.129.2) 6  23.53 ms  ae2.ptw-cr01.plus.net (195.166.129.4) 7  22.95 ms  te-4-2.car5.London1.Level3.net (217.163.45.249) 8  23.56 ms  ae-52-52.csw2.London1.Level3.net (4.69.139.120) 9  22.95 ms  ae-228-3604.edge3.London1.Level3.net (4.69.166.158) 10  23.68 ms  be3043.ccr22.lon01.atlas.cogentco.com (130.117.15.245) 11  23.51 ms  be2315.ccr22.lon13.atlas.cogentco.com (154.54.73.109) 12  109.16 ms be2389.ccr22.bos01.atlas.cogentco.com (154.54.44.181) 13  ... 30 Nmap done: 1 IP address (1 host up) scanned in 8.85 seconds

[#3]

Sorry, just realised that you did the other URL's also;

Quote

Starting Nmap 6.46 ( http://nmap.org ) at 2014-04-22 18:48 BST Nmap scan report for voomka.com (192.163.208.88) Host is up. rDNS record for 192.163.208.88: 192-163-208-88.unifiedlayer.com PORT  STATE    SERVICE 80/tcp filtered http TRACEROUTE (using proto 1/icmp) HOP RTT      ADDRESS 1  6.97 ms  10.0.1.1 2  30.40 ms  lo0-central10.pcl-ag02.plus.net (195.166.128.183) 3  23.68 ms  link-a-central10.pcl-gw01.plus.net (212.159.2.164) 4  24.07 ms  xe-10-1-0.pcl-cr01.plus.net (212.159.0.196) 5  24.08 ms  ae1.ptw-cr01.plus.net (195.166.129.0) 6  23.69 ms  ae2.ptw-cr02.plus.net (195.166.129.5) 7  33.79 ms  10gigabitethernet5-1.core1.lon1.he.net (5.57.80.128) 8  35.18 ms  10ge3-1.core1.lon2.he.net (72.52.92.222) 9  96.58 ms  100ge1-1.core1.nyc4.he.net (72.52.92.166) 10  106.55 ms 100ge7-2.core1.chi1.he.net (184.105.223.161) 11  135.98 ms 10ge3-2.core1.den1.he.net (184.105.213.86) 12  153.72 ms 10ge4-2.core1.slc1.he.net (184.105.222.154) 13  ... 30

Quote

Starting Nmap 6.46 ( http://nmap.org ) at 2014-04-22 18:48 BST Nmap scan report for offgridquest.com (162.144.62.181) Host is up. rDNS record for 162.144.62.181: server.campinglifequest.com PORT  STATE    SERVICE 80/tcp filtered http TRACEROUTE (using proto 1/icmp) HOP RTT      ADDRESS 1  6.01 ms  10.0.1.1 2  28.04 ms  lo0-central10.pcl-ag02.plus.net (195.166.128.183) 3  23.59 ms  link-b-central10.pcl-gw02.plus.net (212.159.2.166) 4  23.57 ms  xe-10-1-0.pcl-cr02.plus.net (212.159.0.198) 5  38.09 ms  ae2.pcl-cr01.plus.net (195.166.129.6) 6  25.14 ms  ae1.ptw-cr01.plus.net (195.166.129.0) 7  ... 8  89.36 ms  100ge1-1.core1.nyc4.he.net (72.52.92.166) 9  116.42 ms 100ge7-2.core1.chi1.he.net (184.105.223.161) 10  136.53 ms 10ge3-2.core1.den1.he.net (184.105.213.86) 11  176.23 ms 10ge4-2.core1.slc1.he.net (184.105.222.154) 12  ... 30

[#4]

Thanks, that's useful and I think there's the problem.
Something is blocking your requests as it should be coming back 'open' rather than 'filtered' on TCP Port 80.
Filtered means a firewall/service/network device is blocking access to that port, meaning nmap cannot tell if it is open or closed. For a website, TCP 80 should be open because that is what you use to connect to it.
Next step will be to figure out where it's being blocked.
- Edit: Just to make sure of something, but if you go here http://www.whatismyip.com/ does it say you have a Plusnet IP?

[#5]

Another one to try nmap -Pn --traceroute gateway.push-apple.com.akadns.net (this is the Apple server for iMessage). I would expect that TCP Ports 80 and 443 will come back filtered (should come back closed).

[#6]

OK, so I've now managed to set up my friends home DSL connection with PN.
In using her new connection for the afternoon this has really highlighted other parts of my own issue.  Often it's difficult to see outside your own situation until you are in another.
First off, all of the affected services work at my friends place fault free.  I also observed that even though her download and upload speeds are a fraction of mine (speed test attached) my laptop was so much more responsive when surfing the web using her connection.  There was very little delay in loading pages and this really has highlighted just how much delay there is on my own connection when accessing "good" websites.
So at home my web page loads are slow with elements often failing to load (see attached), I can not use key services over the PlusNet network, I am unable to see the web in its entirety and the worst of it is that it would seem that this has been the way of it since I first joined.
The "offline team" has been also been looking into this for some time, I'm hoping that they get back to me today as promised.  This is really starting to get me down.

[#7]

Oh and now the forum ain't playing ball, when I post the page "looks" like it hangs (again see attached) however the post has been transmitted just fine

[#8]

Forum stuff is a red herring. We've a known issue on that.
Definitely sounds like you have some sort of fault, or dodgy router to me now.

[#9]

Well at least if it's a known fault with the forums that one can be ticked off the list.
Could it be the BT fibre router thats at fault?

[#10]

It might be worth doing some Wiresharks to see what's going on and if that sheds any light.
I'm pretty sure that the problems you are having are down to ports 80/8080 etc. being blocked for certain sites - but it's a little weird how it seems to be only certain sites.
Do you have any kind of firewall or filtering device on your network? Do you run a VPN? Did you check to make sure your IP shows up as a Plusnet IP?

[#11]

I do run the a VPN service from home however we've tried turning all of my home services off and the issue did not go away.  I'm in total agreement that it's the standard HTTP ports that are only affected.
Yes it's a very odd one indeed, I've no firewall other than locally on the clients and the PlusNet online FW.  Again we've tested with both of these in the off position and the issue remained.
I'll look into Wireshark as I've not heard of that.

[#12]

It's worth trying Wireshark http://www.wireshark.org/download.html - this will capture all traffic on your Mac. You only need to run it for a few secs while trying to access a site that doesn't work. It will capture a lot of data (so don't worry about that).
It could be the Openreach modem. Is it a Huawei HG612 by any chance?

[#13]

There was an issue with VPN and the HG612 https://status.aa.net.uk/1854

[#14]

I know there's issues with VPN  as I routinely have to restart the service on my server as it often fails to connect (thank goodness for Remote Desktop apps).  I'm putting this issue down as also being effected by this odd issue but it may not be as VPN doesn't use http ports.
It looks like I don't have the affected router anyway

[#15]

It would appear you don't.
Both of the BT modems are, however, routers running in 'bridge mode' pretending to be a modem.
Regardless of mode, they're likely to run packets through layer 3 / 4 processing of some sort as they implement TR069 and a management interface to BT.
Interesting that it all works fine from a PlusNet DSL connection though...