BT Infinity issues for the last few days

[psykix]

---

@Tloram wrote:

Well, my connection is still working perfectly after magically getting fixed over an hour ago...

All I can think is: I have been pestering BT constantly ALL week (at least once a day) via their online chat system, so maybe finally sombody actually looked into the connection between my house and the local exchange and actually found and fixed the problem? Stranger things have happend. I still have a "Level 2" technical call due from BT tomorrow lunhctime, so it will be interesting to see what they say they have done to fix the problem.

So to sum up:

 - had zero internet all week from Sunday untill just now (so basically 4 days of no connection)

 - pestered BT all week
 - call due tomorrow from their tech guy

 - all of a sudden today, connection magically is fixed

 - coincidentally it was fixed directly after Robbie posted in this thread:

https://community.bt.com/t5/BT-Infinity-Speed-Connection/BT-Infinity-issues-for-the-last-few-days/m-...

that BT are looking into the issues we are all having...

Oh well, I hope you guys get your connection issues magically resolved like I have. It might be worth doing what I did, and just keep contacting them untill apparently, they get annoyed enough to look into and fix it...

---

I don't think you were experiencing the same issue to be honest.

This is not zero connection but routing issues of some kind. The connection never drops, speedtests prove ok, DNS resolution is fine. However traceroutes are incomplete and multicast IGMP appears to not be working at all.

[psykix]

An admin has contacted me and I've provided some traceroute results.

I've also checked DNS resolution using nslookup and it never fails, so proving DNS resolution is not an issue.

Just thought I'd let you folks know that it's being actively looked at by BT - I know it makes me feel less frustrated to know!

[MarkG33]

Fantastic - Maybe soon enough I will be gaming again online. It's a shame I took this week off work lol. I have been watching this thread like a hawk today.

[Tloram]

@psykix pretty sure I was having the same issues as everybody else, I just wasnt terribly descriptive in that last post I made. I have just updated it with more information about what I was getting (which seems to be what everyone was/is getting).

Only difference is, mine is now fixed (as of 2 hours ago).

[Obiwanw]

Same here in Glossop. Been a problem for about a week and getting worse. Almost unusable now. Switched to google DNS and it seems to have improved things a lot.

[misterleroy]

I've this exact same issue. Only my ps4 has an issue so far. And only really with netflix. Some online games have issues too but I mostly out that down to psn being garbage right now. I've tried multiple playstation devices and even Google dns does not help. BT continue to shove me off the phone with no assistance of even acknowledgement at all.

I'm so tired of this bt bs. It's relentless really

[scottw75]

Glad they've contacted you for your help in finding the fault. Tried a traceroute on my imac and it seemed to take forever to complete.

[MarkG33]

Same on my gaming rig. And laptop. The slowness...

[GrahamWardle91]

Still unable to use my Playstation online.
Here is my HH5 event log for the past few minutes i've tried connecting online:

15:56:08, 11 Dec.	(64597.560000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any-​>9308, internal ports: 9308, internal client: 192.168.1.77
15:56:05, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client associated
15:56:04, 11 Dec.	BLOCKED 2 more packets (because of Advanced Filter Rule)
15:56:02, 11 Dec.	OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath13_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath13)
15:56:01, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client disassociated
15:55:30, 11 Dec.	BLOCKED 1 more packets (because of Spoofing protection)
15:55:28, 11 Dec.	IN: BLOCK [12] Spoofing protection (IGMP 86.128.42.21-​>224.0.0.22 on ppp3)
15:55:06, 11 Dec.	(64535.320000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any-​>9308, internal ports: 9308, internal client: 192.168.1.77
15:55:03, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client associated
15:54:59, 11 Dec.	IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254-​>224.0.0.22 on ptm0.101)
15:54:59, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client disassociated
15:54:30, 11 Dec.	(64500.040000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any-​>9308, internal ports: 9308, internal client: 192.168.1.77
15:54:27, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client associated
15:54:23, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client disassociated
15:53:33, 11 Dec.	(64442.890000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any-​>9308, internal ports: 9308, internal client: 192.168.1.77
15:53:30, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client associated
15:53:27, 11 Dec.	IN: BLOCK [12] Spoofing protection (IGMP 86.128.42.21-​>224.0.0.22 on ppp3)
15:53:26, 11 Dec.	ath00: STA e8:61:7e:49:2f:c1 IEEE 802.11: Client disassociated

Again, i've had variations of PSN Sign In: Failed, NAT Type: Failed, Connection Speed (Download): Failed, each of which i've never had problems with before the past 48 hours.

[MarkG33]

Still the same with my PS3.

This a small chunk as it's pretty much the same from my last post containing the event logs.

Static IP and DMZ set up - It seems to show a bit more detail also -

16:07:45, 11 Dec. IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.100:52917 <-​-​>86.128.189.247:52917 [87.248.208.113:443] CLOSED/CLOSED ppp3 Route)

16:07:45, 11 Dec. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.100:52918-​>93.184.220.97:443 on ppp3)

16:07:45, 11 Dec. IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.100:52921 <-​-​>86.128.189.247:52921 [87.248.208.113:443] CLOSED/CLOSED ppp3 Route)

16:07:45, 11 Dec. (155723.140000) New GUI session from IP 192.168.1.100

16:07:36, 11 Dec. IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.100:42627 <-​-​>86.128.189.247:42627 [74.125.195.101:443] CLOSED/CLOSED ppp3 Route)

16:06:26, 11 Dec. IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.100:3389 <-​-​>86.128.189.247:3389 [222.186.34.157:6000] CLOSED/SYN_SENT ppp3 NAPT)

16:06:25, 11 Dec. IN: ACCEPT [54] Connection opened (Port Forwarding: TCP 192.168.1.100:3389 <-​-​>86.128.189.247:3389 [222.186.34.157:6000] CLOSED/SYN_SENT ppp3 NAPT)