Community Forum for UK Broadband ISP TalkTalk Goes Offline for Days UPDATE
Customers of consumer broadband provider TalkTalk, specifically those looking to engage with their community forum, have spent the past few days scratching their heads after both the forum and many supporting support pages on the provider’s website – including their all important ‘Service Status’ page – suddenly went offline.
The situation appears to have started around Friday 19th June 2026, at least that’s the date given on the general notice, which TalkTalk seems to have stuck to various related TalkTalk Community pages since last week. But the notice merely said “our Community Forum is unavailable at the moment“, without saying for how long, and those who go looking for the Service Status page are greeted with the same message.
In the past few minutes their Service Status page has been changed again and now directs to a different URL, albeit one that seemingly sends visitors around in circles and back to a generic notice with no information. Clearly the ISP appears to be dealing with a few technical problems on their website at the moment, which will hopefully be resolved soon. We are currently awaiting an update from the provider.
Advertisement
UPDATE 23rd June 2026 @ 6:30am
We’ve had the following comment from TalkTalk, which sadly doesn’t clarify when their forum will be back online.
A TalkTalk spokesperson told ISPreview:
“We are aware that some of our TalkTalk Community pages are currently unavailable and we are working on a solution.
In the meantime, customers can check for the latest service status via our Help Centre, or contact us via the usual channels if they need help with specific queries. We’re sorry for the inconvenience caused.”
Mark is a professional technology writer, IT consultant and computer engineer from Dorset (England), he also founded ISPreview in 1999 and enjoys analysing the latest telecoms and broadband developments. Find me on X (Twitter), Mastodon, Facebook, BlueSky, Threads.net and Linkedin.
« Broadband ISP GoFibre Award £12k to Four Scottish Border Community Projects
Advertisement
Leave a Reply
Privacy Notice: Please note that news comments are anonymous, which means that we do NOT require you to enter any real personal details to post a message and display names can be almost anything you like (provided they do not contain offensive language or impersonate a real person's legal name). By clicking to submit a post you agree to storing your entries for comment content, display name, IP and email in our database, for as long as the post remains live.
Only the submitted name and comment will be displayed in public, while the rest will be kept private (we will never share this outside of ISPreview, regardless of whether the data is real or fake). This comment system uses submitted IP, email and website address data to spot abuse and spammers. All data is transferred via an encrypted (https secure) session.
Avoid this ISP all you can. Unreliable service, no real support. Plenty of negative reviews on the internet and rightfully so.
Im a current customer and its 2-3 time when the forums arent working just when u need them – quite a coincidence? Dont think so… thats 1.
2. Look at the service in practice (16.07.2026):
PING talktalk.co.uk (159.60.150.46) 56(84) bytes of data.
64 bytes from 159.60.150.46: icmp_seq=1 ttl=56 time=4980 ms
64 bytes from 159.60.150.46: icmp_seq=2 ttl=56 time=4702 ms
64 bytes from 159.60.150.46: icmp_seq=3 ttl=56 time=5290 ms
64 bytes from 159.60.150.46: icmp_seq=4 ttl=56 time=6160 ms
64 bytes from 159.60.150.46: icmp_seq=5 ttl=56 time=6050 ms
64 bytes from 159.60.150.46: icmp_seq=6 ttl=56 time=989 ms
64 bytes from 159.60.150.46: icmp_seq=7 ttl=56 time=40.5 ms
64 bytes from 159.60.150.46: icmp_seq=8 ttl=56 time=20.7 ms
64 bytes from 159.60.150.46: icmp_seq=9 ttl=56 time=35.3 ms
64 bytes from 159.60.150.46: icmp_seq=10 ttl=56 time=24.7 ms
64 bytes from 159.60.150.46: icmp_seq=17 ttl=56 time=21.4 ms
64 bytes from 159.60.150.46: icmp_seq=18 ttl=56 time=224 ms
64 bytes from 159.60.150.46: icmp_seq=19 ttl=56 time=3258 ms
64 bytes from 159.60.150.46: icmp_seq=20 ttl=56 time=6111 ms
64 bytes from 159.60.150.46: icmp_seq=21 ttl=56 time=6903 ms
64 bytes from 159.60.150.46: icmp_seq=22 ttl=56 time=7556 ms
64 bytes from 159.60.150.46: icmp_seq=23 ttl=56 time=8666 ms
64 bytes from 159.60.150.46: icmp_seq=24 ttl=56 time=8092 ms
64 bytes from 159.60.150.46: icmp_seq=25 ttl=56 time=7755 ms
64 bytes from 159.60.150.46: icmp_seq=26 ttl=56 time=7323 ms
64 bytes from 159.60.150.46: icmp_seq=27 ttl=56 time=6528 ms
64 bytes from 159.60.150.46: icmp_seq=28 ttl=56 time=5528 ms
64 bytes from 159.60.150.46: icmp_seq=29 ttl=56 time=4480 ms
64 bytes from 159.60.150.46: icmp_seq=30 ttl=56 time=3480 ms
64 bytes from 159.60.150.46: icmp_seq=31 ttl=56 time=2434 ms
64 bytes from 159.60.150.46: icmp_seq=32 ttl=56 time=1434 ms
64 bytes from 159.60.150.46: icmp_seq=33 ttl=56 time=435 ms
64 bytes from 159.60.150.46: icmp_seq=34 ttl=56 time=24.7 ms
64 bytes from 159.60.150.46: icmp_seq=52 ttl=56 time=18.4 ms
64 bytes from 159.60.150.46: icmp_seq=53 ttl=56 time=15.8 ms
64 bytes from 159.60.150.46: icmp_seq=54 ttl=56 time=15.4 ms
64 bytes from 159.60.150.46: icmp_seq=56 ttl=56 time=18.5 ms
64 bytes from 159.60.150.46: icmp_seq=57 ttl=56 time=17.8 ms
64 bytes from 159.60.150.46: icmp_seq=58 ttl=56 time=33.7 ms
64 bytes from 159.60.150.46: icmp_seq=59 ttl=56 time=20.9 ms
64 bytes from 159.60.150.46: icmp_seq=60 ttl=56 time=51.9 ms
64 bytes from 159.60.150.46: icmp_seq=61 ttl=56 time=15.9 ms
64 bytes from 159.60.150.46: icmp_seq=62 ttl=56 time=73.5 ms
64 bytes from 159.60.150.46: icmp_seq=63 ttl=56 time=52.7 ms
64 bytes from 159.60.150.46: icmp_seq=64 ttl=56 time=55.9 ms
64 bytes from 159.60.150.46: icmp_seq=65 ttl=56 time=55.1 ms
From 89.242.70.21 icmp_seq=92 Destination Host Unreachable
64 bytes from 159.60.150.46: icmp_seq=93 ttl=56 time=835 ms
64 bytes from 159.60.150.46: icmp_seq=94 ttl=56 time=2277 ms
64 bytes from 159.60.150.46: icmp_seq=95 ttl=56 time=1954 ms
64 bytes from 159.60.150.46: icmp_seq=96 ttl=56 time=2067 ms
64 bytes from 159.60.150.46: icmp_seq=97 ttl=56 time=1881 ms
64 bytes from 159.60.150.46: icmp_seq=98 ttl=56 time=878 ms
64 bytes from 159.60.150.46: icmp_seq=99 ttl=56 time=17.2 ms
64 bytes from 159.60.150.46: icmp_seq=106 ttl=56 time=21.1 ms
64 bytes from 159.60.150.46: icmp_seq=107 ttl=56 time=2090 ms
64 bytes from 159.60.150.46: icmp_seq=108 ttl=56 time=1723 ms
64 bytes from 159.60.150.46: icmp_seq=109 ttl=56 time=2350 ms
64 bytes from 159.60.150.46: icmp_seq=110 ttl=56 time=2631 ms
64 bytes from 159.60.150.46: icmp_seq=111 ttl=56 time=1908 ms
64 bytes from 159.60.150.46: icmp_seq=112 ttl=56 time=1301 ms
64 bytes from 159.60.150.46: icmp_seq=113 ttl=56 time=301 ms
64 bytes from 159.60.150.46: icmp_seq=131 ttl=56 time=15.7 ms
64 bytes from 159.60.150.46: icmp_seq=132 ttl=56 time=18.2 ms
64 bytes from 159.60.150.46: icmp_seq=133 ttl=56 time=19.5 ms
64 bytes from 159.60.150.46: icmp_seq=134 ttl=56 time=16.0 ms
64 bytes from 159.60.150.46: icmp_seq=135 ttl=56 time=21.5 ms
64 bytes from 159.60.150.46: icmp_seq=143 ttl=56 time=455 ms
— talktalk.co.uk ping statistics —
179 packets transmitted, 96 received, +1 errors, 46.3687% packet loss, time 215591ms
rtt min/avg/max/mdev = 15.378/1382.056/8666.455/2352.787 ms
This is the 2nd day of their Voip fixing.
3. The thing is – im not using it and my service was ok prior to this, so they have effectively degraded my (working) service due to other one (which im not even using!)…
Broadband goes on and off and worst – just before the weekend (its friday)…