1. Home
  2. Services
  3. 3 (Three)
3 (Three) three.co.uk

Is 3 (Three) down right now? Live status and outage tracker

Yes, 3 (Three) appears to be down.

Users are reporting a major outage: 294 problem reports in the last hour, far above normal.

Outage Spike in progress since 17:24 Data refreshes every 5 minutes
What you can do
User reports, last 24 hours, 15 minutes a segment: 48 flowing, 37 slow (elevated), 11 jammed (outage)

User reports, last 24 hours

2,275 reports in total, counted in 15-minute windows

  • Normal
  • Elevated
  • Outage
  • Usual level

In the last hour, 294 problem reports came in for 3 (Three), against about 34 at this time on a usual day. Over the last 24 hours there were 2,275 reports, most about internet (66%) and data (22%), from 42 areas led by London and Manchester. A spike in reports is going on now; it started 5 h ago. These are user reports from the UK, where most people report 3 (Three) 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.
Reports, last hour
294
17% on the hour before
Uptime, 24 h
88.54%
2 h 45 min of outage
Last outage
Ongoing
Started 5 h ago
Busiest 15 minutes
99
99 reports, 2 h ago
Last 24 hours

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 ago
    Running for 4 h 45 min
    99peak reports
  • Elevated reports
    Ended 6 h ago
    Lasted 1 h
    25peak reports
  • Elevated reports
    Ended 7 h ago
    Lasted 15 min
    25peak reports
  • Elevated reports
    Ended 8 h ago
    Lasted 1 h
    31peak reports
  • Elevated reports
    Ended 10 h ago
    Lasted 1 h 30 min
    27peak reports
This month

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
Report map

Where 3 (Three) problem reports come from

Each dot is a group of recent reports; bigger dots, more reports.

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.

Last 30 days

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:09
    Still going
    109peak reports
  • Elevated reports
    Wed 28 Oct, 15:24–16:24
    Lasted 1 h
    25peak reports
  • Elevated reports
    Wed 28 Oct, 14:39–14:54
    Lasted 15 min
    25peak reports
  • Elevated reports
    Wed 28 Oct, 13:09–14:09
    Lasted 1 h
    35peak reports
  • Elevated reports
    Wed 28 Oct, 09:39–10:39
    Lasted 1 h
    31peak reports
  • Elevated reports
    Wed 28 Oct, 07:04–07:19
    Lasted 15 min
    12peak reports
  • Elevated reports
    Wed 28 Oct, 06:15–06:32
    Lasted 17 min
    11peak reports
  • Elevated reports
    Wed 28 Oct, 02:43–03:04
    Lasted 21 min
    12peak 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

Troubleshooting

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.

  1. Reload and restart

    Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.

  2. 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).

  3. Update the app

    Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.

Ranked by peak

Biggest 3 (Three) problems so far

  1. 1
    OutageLasted 4 h 52 min
    118reports in 15 min
  2. 2
    OutageStill going, 4 h 45 min so far
    109reports in 15 min
  3. 3
    Elevated reportsLasted 1 h
    35reports 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.

Same 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.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Servers and network

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.

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 30121 ms104.102.19.112
ViennaAustriaUp · HTTP 30185 ms104.102.19.112
MilanItalyUp · HTTP 30161 ms104.102.19.112
ParisFranceUp · HTTP 30137 ms104.75.226.97
AmsterdamNetherlandsUp · HTTP 30126 ms23.218.64.98
MadridSpainUp · HTTP 301196 ms104.75.226.97
WarsawPolandUp · HTTP 301114 ms104.102.19.112
Los AngelesUSAUp · HTTP 30128 ms23.40.168.121
São PauloBrazilUp · HTTP 30132 ms23.45.156.102
SingaporeSingaporeUp · HTTP 30131 ms23.203.73.65
TokyoJapanUp · HTTP 30127 ms23.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.

For your site

Put the 3 (Three) status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

3 (Three) status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/3/"><img src="https://isitdownrightnow.app/badge/3.svg" alt="3 (Three) status" height="20"></a>
Markdown, for README files
[![3 (Three) status](https://isitdownrightnow.app/badge/3.svg)](https://isitdownrightnow.app/services/3/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

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.

Elsewhere

Check other services