Twitter (X) is not working: reasons and how to access it in 2026

IfTwitter is not working right now — the feed is not loading, the app is hanging, or the site simply won't open — it's likely not an issue with your device. In Russia, access to X (formerly Twitter) has been restricted and slowed down through DPI at the provider level since 2022. But before reaching for a VPN, it's worth figuring out: is this a global platform failure, deliberate throttling, or something on your end?

Let's break it down step by step — from simple to complex.

Why Twitter (X) is not working right now: quick diagnosis

The first question to ask yourself: is this a problem with X as a platform, or is the traffic being cut off before it even reaches the servers? The symptoms vary, and the answer determines what to do next.

Failure on X's side or a problem on your end: how to check in 2 minutes

Go to downdetector.com and search for Twitter/X. If there are thousands of complaints in the last hour — the platform is down globally, and no VPN will help here, just wait. If there are few or no complaints at all, the problem is on your side or with the provider.

Another quick test: turn off Wi-Fi and try to load X through mobile internet (MTS, Beeline, MegaFon, T2). If it works through mobile but not through your home router, it's almost certainly DPI from the provider or other network settings. If it doesn't work anywhere — it's either a global failure or throttling is applied both ways.

Blocking and throttling by the provider (DPI, Roskomnadzor)

DPI (Deep Packet Inspection) is a technology for deep traffic inspection. The provider installs special equipment that analyzes each data packet and can slow down or block traffic to specific services. This is how X's throttling works in Russia.

An important nuance: X is not completely blocked, as Telegram was blocked in 2018-2019. Traffic is being throttled — this is a different mechanism. Therefore, you can see the interface, read cached tweets, but new content is not loading or loads very slowly.

Local reasons: cache, outdated app, DNS, network

Sometimes Twitter is not working for trivial reasons: a full app cache, an outdated version of the X client, a hung DNS resolver, or a glitchy router. This can be resolved in five minutes and without a VPN. These cases are in the minority, but it's worth checking first.

How to distinguish provider blocking from a regular failure

DPI throttling has specific symptoms that are hard to confuse with a regular app glitch or server downtime.

Signs of DPI throttling: text loads, media does not

The most characteristic sign: text tweets display, while images and videos either do not load at all or take minutes to load. This is not a coincidence. Text content is light, a few kilobytes. Media files are megabytes. DPI equipment specifically targets heavy traffic because it's more efficient for "throttling" without complete blocking.

Other symptoms: timeouts when refreshing the feed, endless loading spinner, notifications arrive but the feed does not update, videos freeze on the first second. If you recognize at least two of these symptoms — it's DPI, not an app bug.

Checking through different networks and providers

Try accessing X through a hotspot from a different operator's smartphone. If you have Rostelecom at home — try through MTS or vice versa. Different providers use different DPI equipment and apply different policies. Sometimes, X works decently with one operator, while it hardly opens with another.

If possible — check X through a corporate VPN or work network. Corporate networks often go through foreign nodes, and then the provider's DPI does not come into play.

What ping and traceroute show (without technical jargon)

Open the command prompt (Windows: Win+R → cmd, Mac: Terminal) and enterping twitter.com. If pings are going through, but are high — 300–500 ms and above — the traffic is intentionally being slowed down. Normal ping to X servers from Russia is about 80–150 ms through the usual route.

Traceroute (tracert twitter.com on Windows ortraceroute twitter.com on Mac/Linux) is not necessary to check — it will show where the packet is "slowing down," but interpreting the result without experience is difficult. A ping test and checking through another network is sufficient.

Basic ways to fix access (without VPN)

Honestly: if the problem is with DPI throttling, these methods won't help. But they resolve local issues — which account for about 20-30% of cases when people complain that X is not working. So first, we check the simple things.

Clearing the app cache and updating X

Android: Settings → Apps → X → Storage → Clear cache. Not "clear data" — that will remove authorization. Only cache. After that, restart the app.

iPhone/iOS: Remove the app X and reinstall it from the App Store. iOS does not allow clearing app caches selectively, so reinstallation is the only option. Authorization will be saved if you have Keychain enabled.

Also, check the app version. Old versions of client X on Android sometimes stop working after API updates on the platform side — this is not a block, but simply an outdated client. Update X to the latest version in Google Play or App Store.

Changing DNS to 1.1.1.1 / 8.8.8.8

DNS blocking is the most primitive way to restrict access to a site. The provider returns an incorrect IP address in response to a request for twitter.com. Changing DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) sometimes helps.

Android 9+: Settings → Network → Private DNS → enterone.one.one.one.

iPhone/iOS: Settings → Wi-Fi → tap on your network → DNS → add 1.1.1.1.

Windows 11: Settings → Network → Adapter properties → IPv4 → DNS server: 1.1.1.1.

Mac: System Preferences → Network → Advanced → DNS → add 1.1.1.1.

It is important to understand: against DPI throttling, changing DNS is almost always useless. DPI operates not at the DNS level, but deeper — it analyzes the traffic itself after the connection is established. DNS helps only if the provider uses the simplest DNS blocking method.

Network reboot, disabling power saving

Reboot the router (turn it off, wait 30 seconds, turn it on). It sounds trivial, but it helps with stuck connection tables. On Android, also check if the system is optimizing app X in the background — sometimes aggressive power saving interrupts the app's connection to the internet. Go to Settings → Battery → Battery optimization → find X → select "No restrictions."

Why mobile internet sometimes works, but Wi-Fi does not

This is a classic situation with DPI throttling. Your home provider (for example, Rostelecom or MGTS) applies stricter throttling settings than the mobile operator. Or vice versa — the mobile operator has newer equipment with better traffic inspection. Providers purchase DPI hardware from different vendors, configure it differently, and the results vary for everyone.

How to regain access to Twitter (X) via VPN

If basic methods did not help, and you have confirmed that the issue is traffic throttling — you need a VPN. But not just any. Only certain protocols work against DPI.

Which protocols actually bypass DPI: VLESS/XRay, Shadowsocks, Amnezia (AmneziaWG)

Against modern DPI equipment, protocols that mask traffic as regular HTTPS or random data are resistant:

• VLESS/XRay with XTLS-Reality — masks traffic as requests to legitimate HTTPS sites. One of the most resilient methods as of 2026. DPI sees a regular TLS connection, indistinguishable from a browser.
• Shadowsocks + obfs4 plugin or v2ray-plugin — encrypts and obfuscates traffic, making it look like random data flow. It has been tested for a long time and works reliably.
• AmneziaWG — modified WireGuard with altered packet headers. It removes the characteristic signature of WireGuard, which DPI uses to detect it.

NvoVPN supports these protocols — you can try it as one of the options. But in general, any provider that supports VLESS/XRay or Shadowsocks with obfuscation will work.

Why WireGuard and OpenVPN are sometimes blocked by signature

Standard WireGuard has a characteristic handshake pattern — the first connection packet looks specific. DPI systems can recognize and block it. The same goes for OpenVPN: it has a fixed signature in the packet headers, which is not difficult to detect.

IKEv2 is also not an ideal option, although it is used less frequently for blocking. But if the provider deliberately configures the equipment to block VPN traffic, IKEv2 will be the first to go under the knife after WireGuard and OpenVPN.

Therefore, classic protocols are suitable for countries without active DPI blocking of VPNs, but in Russia, their reliability has decreased.

Setup on Android and iPhone/iOS: step by step

Android (VLESS via v2rayNG client):

1. Install v2rayNG from Google Play.
2. Obtain the configuration file or link from your VPN provider.
3. In v2rayNG, click “+” → “Import configuration from clipboard” (if you have a link) or select a file.
4. Click on the added server, then the start button (triangle at the bottom). On the first launch, Android will ask for permission to create a VPN connection — allow it.

iPhone/iOS (Shadowsocks via Shadowrocket client):

1. Shadowrocket costs $2.99 in the App Store — it is the standard client for obfuscated protocols on iOS.
2. Add a server: click “+” → enter the server details (host, port, password, encryption method).
3. Return to the main screen, press the connection toggle. iOS will ask for permission for the VPN profile — confirm it.

Setup on Windows, Mac, and router for all devices

Windows and Mac — most VPN services provide ready-made applications. If your provider supports VLESS or Shadowsocks, check if it has a native application. An alternative for Windows is the Nekobox or Hiddify client, for Mac — ClashX.

Router — the most convenient option: the VPN is set up once, and all devices on the home network automatically work through it. Suitable for routers with OpenWrt or Keenetic firmware. Keenetic has built-in support for WireGuard and OpenVPN, but for VLESS/XRay you will need to use the Entware package and configure it manually — this is for experienced users.

Access to X on Smart TV and Apple TV

Smart TV and Apple TV do not support VPN clients directly (except for rare exceptions). There are two ways: the first — set up a VPN on the router, then the TV will automatically receive protected traffic. The second — configure smart DNS or proxy on the router only for Twitter/X traffic, without affecting the rest of the traffic.

What to do if the VPN does not help or X is still lagging

VPN is connected, but the feed still does not load or lags — this is a separate problem, and it has several causes.

VPN is connected, but the feed does not load: change the protocol and server

First — change the server. Try a server in another country: Netherlands, Finland, Germany, Singapore. Sometimes a specific IP address of the VPN server gets on the blocklist — not in Russia, but at the level of the X platform itself, which sometimes blocks ranges of IPs of commercial VPNs.

Second — change the protocol. If you are using WireGuard and it is unstable, switch to VLESS or Shadowsocks. If your provider offers several protocols to choose from — try them one by one.

Third — change the port. Some providers block standard VPN ports (UDP 51820 for WireGuard, TCP 443 for OpenVPN). If your VPN service allows you to choose a non-standard port — use it.

Conflict with antivirus, firewall, and system DNS

Antiviruses Kaspersky, ESET, and Dr.Web sometimes conflict with VPN clients — intercept traffic through their own network driver and interfere with the tunnel operation. Try temporarily disabling the web protection of the antivirus (not the entire antivirus, just the network filtering module) and check if the situation has changed.

Corporate and student networks — a separate story. They often have their own firewall that blocks VPN protocols regardless of the provider. In this case, the only option is VLESS through port 443 (it is indistinguishable from HTTPS) or Shadowsocks with obfuscation. Double NAT in corporate networks can also break WireGuard UDP tunnels.

When the client X is at fault, not the network

It can also happen: the VPN works, other sites open quickly, but X lags. This may be a global failure on the platform's servers. Check downdetector.com — if everything is red there, it means Twitter is not working for everyone, and it is not related to your network or VPN.

Also check: X opens normally in the browser (chrome or safari), but not in the app? This indicates an outdated client or a bug in a specific version of the app. The app and the browser version go through different paths — the mobile app has its own HTTP client, which may cache old connection settings. Reinstall the app.