G.Network outages and problems
In the past 24 hours, 133 user reports came in for G.Network. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 94.79% 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 20 reports, about 2 hours ago.
-
Outage
Ongoing, started 2 h agoRunning for 2 h 15 min20peak reports
G.Network in October 2026
- Problem reports in October (since 29 October)
- 130
Monthly report for October 2026
What went wrong
What people said was wrong in recent problem reports for G.Network.
Share of 12 recent reports that said what was wrong.
Where G.Network problem reports come from
The map shows where recent problem reports for G.Network came from in the UK. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
G.Network problem spikes, last 30 days
Since 29 October, G.Network had 1 outage spike.
-
Outage
Fri 30 Oct, 09:03–11:18Still going21peak reports
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 29 October 2026. Monthly reports for all services
How to fix G.Network not working
When G.Network 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 g.network 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 G.Network.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as G.Network
Since 29 October, G.Network's only spike 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.
During the latest spike
G.Network: Fri 30 Oct, since 09:03
- Archive of Our Own, outage,29 Oct 07:55 to 11:17
- Sunrise, outage,07:32 to 10:32
- Lloyds Bank, outage,08:32 to 10:32, 11:02 to 11:17
- DITO Telecommunity, outage,08:41 to 09:32, 10:47 to 11:02
- Chess.com, outage,08:47 to 09:32
- Ladbrokes, outage,08:47 to 09:47
- Coral, outage,08:48 to 09:18
- DeepSeek, outage,09:17 to 09:32
27 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.
G.Network IP address, servers and network
Checking g.network from our server…
How we track G.Network
The status on this page comes from user-submitted problem reports for G.Network, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for G.Network, 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. G.Network 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.