Truespeed
Active issue
Is Truespeed down? Truespeed is down in Blagdon and Jasper's Green
No problems reported elsewhere on the network. Status checked at 02:55 on 29 October 2026.
What Truespeed says
Their latest update
We’re investigating an issue in Jasper's Green impacting around 4 customers. We’ll update this page when we have more information.
Read the full noticeLast 30 days
TruespeedDownBlagdon and Jasper's GreenIncidents
Current
Incident in Jasper's Green - reference NOCE-14537
SourceOngoing since 13:35, 27 Oct
“We’re investigating an issue in Jasper's Green impacting around 4 customers. We’ll update…”
Incident in Blagdon - reference NOC-3284
SourceOngoing since 09:50, 26 Oct
“We’re working to fix an issue in Blagdon impacting around 13 customers. We’ll update this…”
Past incidents
Tue 27 Oct
Incident in Norfolk: Aslacton, Banham, Bressingham, Carbrooke North, Carleton Rode, Great Hockham, Harling, North Lopham, Old Buckenham, Tacolneston, Winfarthing, Wretham. - reference NOCE-14509
SourceResolved 10:30
“We've now resolved the earlier issue in Norfolk: Aslacton, Banham, Bressingham, Carbrooke…”
Mon 26 Oct
Incident in Norfolk: Aslacton, Banham, Bressingham, Carbrooke North, Carleton Rode, Great Hockham, Harling, North Lopham, Old Buckenham, Tacolneston, Winfarthing, Wretham. - reference NOCE-14509
SourceResolved 08:29, 27 Oct
“We've now resolved the earlier issue in Norfolk: Aslacton, Banham, Bressingham, Carbrooke…”
Incident in High Easter - reference NOCE-14513
SourceResolved 15:05, 27 Oct
“We’re working to fix an issue in High Easter impacting around 24 customers. We’ll update…”
Sun 25 Oct
Incident in Peldon - reference NOCE-14486
SourceResolved 19:40, 26 Oct
“We’re investigating an issue in Peldon impacting around 5 customers. We’ll update this…”
Show 14 older entriesHide older entries
Sun 25 Oct
Incident in Great Wigborough - reference NOCE-14483
SourceResolved 13:35, 27 Oct
“We’re investigating an issue in Great Wigborough impacting around 6 customers. We’ll…”
Incident in Eight Ash Green and Aldham - reference NOCE-14451
SourceResolved 14:00
“We’re working to fix an issue in Eight Ash Green and Aldham impacting around 160…”
Incident in Foxearth, Belchamps and Bulmer - reference NOCE-14448
SourceResolved 19:10
“We’re working to fix an issue in Foxearth, Belchamps and Bulmer impacting around 203…”
Sat 24 Oct
Incident in Tacolneston - reference NOCE-14396
SourceResolved 13:10, 28 Oct
“We’re investigating an issue in Tacolneston impacting around 5 customers. We’ll update…”
Incident in Moorlinch, Spring Lane - reference NOC-3283
SourceResolved 08:20, 28 Oct
“We’re working to fix an issue in Moorlinch, Spring Lane impacting around 3 customers…”
Wed 21 Oct
Incident in White Notley, Faulkbourne - reference NOCE-14238
SourceResolved 14:30
“We’re working to fix an issue in White Notley, Faulkbourne impacting around 71 customers…”
Mon 19 Oct
Incident in Toppesfield - reference NOCE-14126
SourceResolved 11:40
“We’re working to fix an issue in Toppesfield impacting around 8 customers. We’ll update…”
Sun 18 Oct
Incident in Moorlynch - reference NOC-3274
SourceResolved 15:45, 21 Oct
“We’re working to fix an issue in Moorlynch impacting around 5 customers. We’ll update…”
Thu 15 Oct
Incident in Rickinghall, Thelnetham - reference NOCE-14048
SourceResolved 09:35, 16 Oct
“We’re working to fix an issue in Rickinghall, Thelnetham impacting around 4 customers…”
Tue 13 Oct
Incident in Wells - reference NOC-3270
SourceResolved 08:20, 14 Oct
“We’re working to fix an issue in Wells impacting around 43 customers. We’ll update this…”
Mon 12 Oct
Incident in Capel St Mary - reference NOCE-13929
SourceResolved 13:45 · Capel St Mary, Woodham Mortimer
“We’re working to fix an issue in Capel St Mary impacting around 30 customers. We’ll…”
Sun 11 Oct
Incident in Kelvedon Hatch - reference NOCE-13862
SourceResolved 22:45
“We’re working to fix an issue in Kelvedon Hatch impacting around 10 customers. We’ll…”
Sat 3 Oct
Incident in Woolavington, Chedzoy, Moorlinch & Bawdrip - reference NOC-3258
SourceResolved 18:40, 6 Oct
“We’re working to fix an issue in Woolavington, Chedzoy, Moorlinch & Bawdrip impacting…”
Tue 29 Sept
Incident in Norfolk - reference NOCE-13421
SourceResolved 18:25, 30 Sept
“We've now resolved the earlier issue in Norfolk. If you are still experiencing problems…”
While you wait
Three things to rule out first
- Restart the routerOff at the wall for 30 seconds, then back on. Fixes more dropouts than anything else.
- Try another deviceIf only one thing can’t get online, that device is the problem.
- Run a speed testSlow or actually offline? Thirty seconds tells you which.
Still not working? Report the fault to Truespeed on 01225 300370 (Mon to Fri 8am to 6pm, Sat 8am to 4pm).
Had enough?
See what else is available at your address.
Truespeed hasn't signed Ofcom's speed code, but consumer law still applies. If you hit a wall, Ofcom's ADR scheme is free to use.
See alternative deals →Is Truespeed working for you right now?
Your browser may ask for your location. All we keep is the postcode area, so your report helps others nearby see it's not just them. Say no and it still counts.
The network
About Truespeed’s network
Truespeed sells 4 speeds today, from 150 Mbps to 900 Mbps, all of them full fibre, so the fibre runs all the way into your home.
Truespeed runs its own network, so a fault on the line is Truespeed's own to fix.
Truespeed isn't signed up to Ofcom's automatic compensation scheme, so ask for a credit if you're left without service. How compensation works
FAQ
Truespeed outage, common questions
Is Truespeed down right now?
Not network-wide. Truespeed's own status page lists a contained incident, and the card above says where and what Truespeed has said about it. Outside that area your connection isn't part of it, so restart your router and try another device first.
Is Truespeed down in my area?
Truespeed's own service status page on truespeed.com lists the faults it knows about. This page shows whether Truespeed has a wider problem right now. If it doesn't and you're still offline, restart the router, then report the fault to Truespeed.
How do I report a Truespeed outage?
Most providers route fault reports through their app or support line. Truespeed's own status page (linked above when one exists) tends to update faster than support staff can, check there first. You can also run our speed test, the result feeds the outage detection model that other Truespeed customers see on this page.
Will I get compensation for a Truespeed outage?
Truespeed isn't signed up to Ofcom's automatic compensation scheme, so there's no automatic payment when the service goes down. Report the fault and ask Truespeed for a credit for the days you were without it. If they won't help, complain, and after six weeks you can take it to the free dispute scheme Truespeed belongs to.
How long do Truespeed outages usually last?
Most outages we've tracked resolve within a few hours. Bigger network-side incidents (a backhaul issue or a regional fibre cut) can run 6 to 12 hours. The page above will move from 'down' to 'issues earlier' once the live signal fades, that's a more reliable timeline than support-staff estimates.
Can I switch from Truespeed mid-contract if their network keeps going down?
Truespeed hasn't signed Ofcom's voluntary broadband speeds code, so there's no set right to leave mid-contract over slow speeds or a service that keeps going down. General consumer law still applies if the service isn't what was sold. Complain to Truespeed first, and if it isn't sorted after six weeks, you can take it to the free dispute scheme Truespeed belongs to.
Why does the tracker say Truespeed is working fine when I'm having issues?
Two reasons. Either your issue is local to your line, building, or Wi-Fi (which won't show up as a wider network outage), or you're an early indicator of an outage that hasn't yet been corroborated by other signals. Run the speed test and use the feedback widget on this page, both feed the model and help confirm whether it's just you or something wider.
More Truespeed tools