3 (Three) outages and problems
In the past 24 hours, 2,275 user reports came in for 3 (Three). Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 88.54% uptime for the day.
The most recent spike big enough to count as an outage was under 15 minutes ago. The busiest 15-minute window of the day had 99 reports, about 2 hours ago.
-
Outage
Ongoing, started 5 h agoRunning for 4 h 45 min99peak reports
-
Elevated reports
Ended 6 h agoLasted 1 h25peak reports
-
Elevated reports
Ended 7 h agoLasted 15 min25peak reports
-
Elevated reports
Ended 8 h agoLasted 1 h31peak reports
-
Elevated reports
Ended 10 h agoLasted 1 h 30 min27peak reports
3 (Three) in October 2026
- Problem reports in October (since 27 October)
- 2,737
Monthly report for October 2026
What people said was wrong in recent problem reports for 3 (Three), as a share of those reports:
- 66% Internet
- 22% Data
- 9% No Signal
- 2% Voice calls
Where 3 (Three) problem reports come from
Recent reports came from 42 areas. The most came from around London, Manchester and Glasgow. Share of recent reports by area, named after its biggest town:
- 36% London
- 25% Manchester
- 6% Glasgow
- 5% Newcastle upon Tyne
- 5% Birmingham
- 4% Sheffield
From 2,305 recent problem reports. Big cities always send the most, so reports from many places point to a widespread problem, and one area far ahead of the rest can mean a regional one. Town names: GeoNames.
3 (Three) problem spikes, last 30 days
Since 27 October, 3 (Three) had 2 outage spikes and 7 periods of elevated reports. The longest lasted 4 h 52 min, on 27 October.
-
Outage
Wed 28 Oct, 17:24–22:09Still going109peak reports
-
Elevated reports
Wed 28 Oct, 15:24–16:24Lasted 1 h25peak reports
-
Elevated reports
Wed 28 Oct, 14:39–14:54Lasted 15 min25peak reports
-
Elevated reports
Wed 28 Oct, 13:09–14:09Lasted 1 h35peak reports
-
Elevated reports
Wed 28 Oct, 09:39–10:39Lasted 1 h31peak reports
-
Elevated reports
Wed 28 Oct, 07:04–07:19Lasted 15 min12peak reports
-
Elevated reports
Wed 28 Oct, 06:15–06:32Lasted 17 min11peak reports
-
Elevated reports
Wed 28 Oct, 02:43–03:04Lasted 21 min12peak reports
1 earlier spike in this period.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 27 October 2026. Monthly reports for all services
How to fix 3 (Three) not working
When 3 (Three) itself is having trouble, these steps won't bring it back, but they will rule out anything on your side:
Your browser tries to reach three.co.uk over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not 3 (Three).
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Biggest 3 (Three) problems so far
-
1
OutageLasted 4 h 52 min118reports in 15 min
-
2
OutageStill going, 4 h 45 min so far109reports in 15 min
-
3
Elevated reportsLasted 1 h35reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as 3 (Three)
Since 27 October, all 9 of 3 (Three)'s spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- ESPN Fantasy Football9 times
- TalkTalk7 times
- Astound7 times
- AT&T7 times
- Straight Talk7 times
- ADP6 times
How many of 3 (Three)'s spikes overlapped one of theirs.
During the latest spike
3 (Three): Wed 28 Oct, since 17:24
- ESPN Fantasy Football, outage,27 Oct 19:50 to 22:09
- TalkTalk, outage,3 spikes, 08:54 to 21:53
- Character.AI, outage,12:24 to 22:09
- Honda Link, outage,12:24 to 22:09
- ADP, outage,13:39 to 22:09
- OpenAI, outage,14:24 to 18:39
- Adobe Connect, outage,15:09 to 17:54
- YouTube, outage,15:09 to 22:09
117 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
3 (Three) IP address, servers and network
- IPv4 address
- 23.45.100.103
- IPv6
- Not offered
- Network
- AS16625 · Akamai Technologies, Inc., registered in the United States
- Served through
- Akamai
- DNS hosted by
- its own name servers (cscdns.net)
- HTTPS certificate
- Issued by DigiCert Ireland Limited, valid until 19 Apr 2027 (172 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 101 ms
Checked from our server in Frankfurt, Germany, 1 h ago, for www.three.co.uk. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from three.co.uk. Fastest from Frankfurt (21 ms), slowest from Madrid (196 ms). Every location connected through Akamai Technologies, Inc. (AS16625), using 7 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 21 ms | 104.102.19.112 |
| ViennaAustria | Up · HTTP 301 | 85 ms | 104.102.19.112 |
| MilanItaly | Up · HTTP 301 | 61 ms | 104.102.19.112 |
| ParisFrance | Up · HTTP 301 | 37 ms | 104.75.226.97 |
| AmsterdamNetherlands | Up · HTTP 301 | 26 ms | 23.218.64.98 |
| MadridSpain | Up · HTTP 301 | 196 ms | 104.75.226.97 |
| WarsawPoland | Up · HTTP 301 | 114 ms | 104.102.19.112 |
| Los AngelesUSA | Up · HTTP 301 | 28 ms | 23.40.168.121 |
| São PauloBrazil | Up · HTTP 301 | 32 ms | 23.45.156.102 |
| SingaporeSingapore | Up · HTTP 301 | 31 ms | 23.203.73.65 |
| TokyoJapan | Up · HTTP 301 | 27 ms | 23.206.236.220 |
Checked with check-host.net from its servers in these cities 1 h ago, for three.co.uk. Time is how long each server took to load the page.
How we track 3 (Three)
The status on this page comes from user-submitted problem reports for 3 (Three), counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for 3 (Three), so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. 3 (Three) doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.