Discord not working: why it happens and what to do

Sites open, videos play, messengers work — but Discord is not working: the app hangs on loading, channels do not load, messages do not go out. Reinstalling changes nothing, and a friend in the next district has no trouble at all. Below — why this happens, how to tell “one app is silent” from “the network is down” in a couple of minutes, what our measurement from five machines and an open database of tests run by volunteers showed — and what these numbers do not say.

Why Discord does not work when the internet does

“Not working” for an app and “not working” for the network look the same but are built differently. Let us go through what happens when you open Discord.

Discord has not one address but several, and the roads to them differ. There is the website. There is the service the app asks, when it starts, where to connect. There is the persistent-connection server — new messages reach you through it. There are the servers for images and files. And there are separate voice servers, which work quite differently from everything else. Each of these roads can break on its own. Hence the familiar pictures: “the website opens but the app hangs on loading”, “messages go through but images do not”, “there is text but no voice”. These are not contradictions — they are different roads.

First the phone looks up the address, then it knocks on it. These are two different steps, and they break separately. Looking up the address is quick and inconspicuous; establishing a connection to that address is a separate step, and that is the one that most often fails for people. From the outside it looks like “the app froze”: it is waiting for an answer that does not come. Why even a ping can go through at the same time, we covered using Telegram as the example.

Every network has its own road. Your path to Discord’s servers and your friend’s path are two different routes, even if both of you have the same provider. Hence the most galling part: it works for them and not for me, and both are telling the truth. Below you will see how differently even the networks of one and the same provider behave.

The conclusion this section was written for: if everything else on the network works and only Discord is silent — both in the app and in the browser — reinstalling it is usually pointless. It is not the app that breaks but the road to it.

How to tell your case apart in a couple of minutes

The check has one purpose: to separate “something is wrong with Discord itself” and “something is wrong in my phone” from “something is wrong on the way to its servers”. You need no terminal. Go in order and note the answers.

1. Check whether Discord is down for everyone. It has its own status page — discordstatus.com. If it reports an outage, the cause is not your network and not your phone: all that is left is to wait. If it says “All Systems Operational”, go on. That is exactly what it said at the time of our measurement.
2. Open something else on the same network. Any site, any other feed. If it opens, you have internet, and the problem is not “the internet is gone”.
3. Open Discord in a browser — at discord.com. If the browser is as silent as the app, it is definitely not the app. If it works in the browser but not in the app, look at the app itself: update it and check whether it has been routed around the tunnel.
4. Switch networks. From Wi-Fi to mobile data and back, within the same minute. A different result on the two networks means the phone and the app have nothing to do with it — a particular network is to blame.
5. Try a second device on the same network. If it is silent there too, it is not the phone.
6. Turn on the tunnel and restart Discord. Restart it, do not just switch back to it: the app may have been holding on to an old failed attempt. If it works after that, the bottleneck was on the road; if not — the reasons are covered below.

Our measurement: from a datacentre in Russia, Discord opens

We do not retell the news — we measure what we can reach ourselves. On 24 September 2026, between 07:55 and 08:15 Moscow time, from each of our machines we contacted four Discord addresses: the website, the service the app asks where to connect, the persistent-connection server and the image server. And in the same minute, from the same machine, control addresses that have nothing to do with Discord.

The Russian row is the main difference from Telegram. Two days earlier we measured Telegram with a similar instrument, and from the same machine in Russia a connection to it was not established once — 21 attempts out of 21. With Discord it is exactly the other way round: three rounds with a pause, and every time everything opened — the website, the app’s service, the connection server and the image server. The encrypted connection was set up in nine hundredths of a second — the same order as from abroad.

What follows from this. What people run into, our machine in Russia does not reproduce. It stands in a datacentre and reaches the internet through the hosting company’s network, while people go through the networks of home internet providers and mobile carriers. That does not mean all is well for people: it means one has to look where they actually connect. We have no machines there, but open measurements from there exist — they are the next section.

What volunteers see on home and mobile networks

OONI (Open Observatory of Network Interference) is an open, non-profit project that has been collecting measurements of website reachability around the world since 2012. The measurements are made by volunteers: they install the free OONI Probe app on a phone or computer, and it tests a list of sites from their own home or mobile connection. All results are published openly — anyone can look at them in OONI Explorer (search for the site discord.com and the country “Russia”).

How a test works. The volunteer’s app looks up the site’s address, establishes a connection and requests the page, while the project’s control server does the same from another network in the same minute. If they match, the result is “normal”. If they differ, it is an “anomaly”: a different address, a connection that was not established, or a different answer.

What the database holds for discord.com. Tests from Russia for 1–23 September 2026, via the project’s open interface, queried on 24 September:

This is not one bad day: on each of the 23 days, anomalies were more than two thirds of the tests. For comparison, telegram.org in the same database over the same days — 15,915 anomalies out of 19,051 tests. By volunteer tests the two services look alike, while from our datacentre they are opposite. That is exactly why a measurement from a datacentre must not be passed off as a picture of what happens at home.

The picture depends heavily on the network. Here are the largest networks by number of tests in the same sample. The network number is its name in the open registry; you can find it by that number in OONI Explorer.

Look at the two Rostelecom rows: in one of its networks anomalies are more than nine tenths, in the other fewer than half. MegaFon has 545 of 547 in one network and 129 of 226 in another. Hence one of the answers to “my friend has the same provider and it works for them”: a provider is not one network for everyone, and the roads of its networks differ.

What a tunnel changes here

A tunnel does not repair your road — it changes where it ends: the request to Discord goes out to the internet from the address of our server, not from your provider’s network. In the same hour on 24 September we brought up a real tunnel to the Netherlands line — not “on paper” but with an instrument: the configuration was issued, the handshake went through in a couple of seconds, the packet size was 1397 bytes, and the exit address matched the address of the Netherlands server. And from that address, according to the table above, Discord answers within hundredths of a second. Through the same tunnel we also checked the path to Discord’s address itself: 20 packets out of 20 got there and back.

This has to be read strictly. We did not measure the end-to-end path “phone → tunnel → the Discord app” as a whole. We have two links measured separately: traffic leaves from the server’s address, and from the server’s address Discord answers. A chain of two measured links and a measured chain are not the same thing, and we will not pass one off as the other.

And one more thing. The first half of the road — from your device to our server — remains yours. If your network does not let the tunnel itself through, it will not come up, and then everything said above is beside the point. That case is the third one in the next section.

The tunnel is on, and Discord still does not work

The most galling case. It has five explanations; they are different and are checked one at a time, and almost all of them you can check yourself without leaving the phone.

1. Discord has been routed around the tunnel. Apps of this kind have split tunneling: the selected apps do not go through the tunnel but the way they did before. If Discord ended up on that list, the tunnel is on but nothing has changed for it, and the icon in the notification shade is misleading. In our app the setting is called “Split tunneling”, and the app’s main screen has a preset bar with a ready-made set, “RU Apps” — Russian services that a tunnel only gets in the way of (how it is turned on). If the app sees that you go online from Russia, it turns this set on by itself once and tells you so directly. Discord is not in it — we checked this on 24 September 2026 against the list on our server itself, where the app gets it from, and against the backup copy in the production build, not from memory. So in our app Discord goes through the tunnel by default. It is worth looking through the whole list: the set is ours, but the ticks in it are yours.

2. Packet size. A recognisable sign: messages go through, but images, videos and screen sharing do not load or stop halfway. Small packets get through, large ones do not. This is not about Discord at all, and it is not fixed inside it: how it works and what to adjust — in a separate write-up. In our measurement the tunnel came up with a packet size of 1397 bytes — a chosen value, not a random one, and it is chosen precisely for cases like this.

3. The network does not let everything through, and the tunnel is not among what it lets through either. It happens that on mobile data a small set of services opens and the rest does not, and the connection to us does not come up either. The sign: neither Discord nor the VPN works, yet a couple of familiar pages open just fine. This is a separate mechanism, and we have covered it in detail — why only part of the internet opens. If the trouble is on home internet, start with the write-up on home networks, and for mobile data — with the write-up on mobile internet.

4. The tunnel did not actually come up. The icon is there but there is no connection — that happens too. It takes a minute to check: four step-by-step checks — has the address changed, is traffic flowing. If it has not changed and is not flowing, go on here: the tunnel will not connect, it worked and stopped, the app will not start. And if all of them are silent at once, that is when no VPN connects, and that case is covered there in full, together with what is happening with the connection today.

5. Discord is silent on the computer, and the tunnel is on the phone. A tunnel on the phone works only for the phone: the computer next to it goes online as before. We do not have our own apps for Windows and Mac yet. A third-party desktop app can take the same subscription link, but we have not tested it there with a live connection — so we cannot say anything about Discord on a computer. That is written down as it is in the help centre.

Why we have anything to say about this case at all: the app does not travel by one road. If the first one fails, it tries the next by itself, and the person does not have to choose anything by hand — how the connection steps work is covered separately.

What we do not promise

In plain words, so that nothing extra can be read into the sections above.

• That a particular service will work for you. We make no such promises about any service or any app. What you get depends on your network, your hour and your route — and those we have not measured and cannot measure.
• That voice will work. We did not measure Discord’s voice at all, and no conclusions about it can be drawn from this article.
• That our numbers are a picture of the country. One machine in one datacentre is one address and one route. Volunteer tests are those who chose to run them. We draw no shares, no percentages and no “what works where” maps.
• That tomorrow will be like today. The measurement was taken on one day, within a quarter of an hour. The network changes faster than articles come out, and we do not rewrite this page every evening.
• That we answer for carriers and home internet providers. The first half of the road — from your device to us — remains entirely yours, and no tunnel remakes it.

What we really can do is answer for our own stretch of the way, measure it and show it as it is, together with what the measurement does not say. And let you check for free, because on your network the answer will be your own anyway.

What we tested

• Where Discord answers from — from five machines. 24 September 2026, 07:55–08:15 Moscow time: our machines in Russia, the Netherlands, Poland and Germany, and a work machine in Moscow that reaches the internet through Kazakhstan. Four Discord addresses plus control addresses from the same machine in the same minute — without them an “all answered” row would prove nothing.
• The Russian row — three times. Three rounds with a pause, and every time all four addresses answered. One successful answer can be chance; three in a row no longer are.
• Both the address and the name. We asked one and the same address under Discord’s name and under someone else’s name — the answer was the same. So from that machine neither gets in the way.
• That “not found” is normal. The persistent-connection server answers a plain request with “not found”: it expects a special, long-lived connection, not a page. What matters is that the encrypted connection to it was established — that is exactly what we checked, and we did not mistake its answer for a fault.
• The open OONI database — at the source. A query to the project’s open interface on 24 September: the website reachability test, country — Russia, site — discord.com, 1–23 September 2026, the total and the breakdown by network and by day. The network names were checked against the open address registry, not guessed from the number.
• A live tunnel — with an instrument, not on paper. A real connection to the Netherlands line was brought up: the configuration was issued, the handshake went through, the packet size was 1397 bytes, the exit address matched the server’s address, and the path to Discord’s address through the tunnel was alive — 20 packets out of 20.
• Our own “RU Apps” set — against the list on the server the app takes it from, and against the backup copy in production build 0.7.33: Discord is in neither, checked on 24 September 2026.
• Discord’s status page — at the time of the measurement it said “All Systems Operational”: the service itself had no outage.
• We did NOT measure the sign “messages go through, images do not” here — it is how networks work in general, and we call it exactly that; our own packet-size measurements live in a separate write-up.

What we do not know

It is more honest to list it than to stay silent: the measurement is a one-off, and exactly as many conclusions can be drawn from it as it holds.

• Voice, the microphone, calls and screen sharing. Discord’s voice goes to separate servers and travels differently from messages. Neither our instrument nor the volunteer tests touched it. If your microphone does not work in Discord while text goes through, this article is not about your case, and we will not make up an answer.
• Discord on a computer. We have no app of our own for Windows and Mac, and we have tested nothing on a computer with a live connection.
• The end-to-end path “phone → tunnel → Discord”. Neither from a phone nor through a mobile carrier. We have two measured links, not a measured chain.
• What is on your network. Our machines stand in datacentres, and the volunteer tests are not the whole country and not your home. We do not answer for other people’s networks and do not paint a portrait of the country.
• Why it is so. We see that Discord opens from a datacentre, while on home and mobile networks tests more often differ from the control ones — and we do not see whose decision that is or for how long. We do not invent explanations.
• What tomorrow will bring. Roads change without warning, sometimes within a day. Our measurement is a quarter of an hour on 24 September 2026, and nothing more.
• How long it lasts for you. Our connection log does not keep which sites and services you visit — so we have nothing to answer this question with.

Short answers

Why does Discord not work if the internet does? Because “the internet works” is about the road in general, while Discord needs a road to its particular servers. That road can break separately from everything else: other sites open, yet a connection to Discord is not established. Where exactly it breaks depends on your network.

What to do if Discord is not working? In order: check Discord’s status page, open another site, open Discord in a browser, switch networks, try a second device, turn on the tunnel and restart the app. All the steps and what each answer means — above.

Discord not working today — is it down for everyone? That is visible on its own status page, discordstatus.com. If it reports an outage, it is for everyone. If it says “All Systems Operational”, the service itself works, and the cause is on the road from your network.

Will a VPN help if Discord is not working? We will not promise that about any service. The mechanics are these: a tunnel changes the address the request leaves from — and if the cause was the road, another road may turn out better. If the cause is your own stretch — the Wi-Fi, the carrier’s network, the device itself — a tunnel does not change that.

Will reinstalling Discord help? If it is silent both in the app and in the browser while the rest of the network works — almost certainly not. It is not the app that breaks but the road to it; reinstalling does not touch the road.

My friend has the same provider, and everything works for them — why? Because “the same provider” does not mean “the same network”. In the open test database, two networks of the same provider can show opposite pictures — the numbers are above. It is easy to check — by switching networks within the same minute.

The microphone does not work in Discord — is that the same thing? No. Voice goes to other servers and travels differently from messages, and we did not measure it. This article is about the case where Discord does not load at all.

And if Discord does not work on a computer? A tunnel on the phone does not touch the computer. We have no apps of our own for Windows and Mac, and we have tested nothing on a computer with a live connection — what there is, is written in the help centre.

Does your measurement mean Discord opens in Russia? No, and we will repeat it on purpose: it opens for our machine in a datacentre at one hosting company. Home and mobile networks are different roads, and there, according to volunteer tests, the picture is different. There is not a single share “for the country” in this article.