[b]CONTEXT[/b] A friend of mine has been getting CENTIPEDE / CURRANT / "servers are not available" errors since early 2025 and never found out why. He tried every fix he could find, with no luck. Today, with the error still happening, we tried a different approach: testing one thing at a time and noting every result, using Claude as a brainstorming partner along the way. After many tests, we found that the problem comes down to which public IP address the line gets when the router restarts. I'd really like everyone still playing to enjoy the game, so I'm sharing the full story here: the symptoms, every test we ran, and the workaround that works for now. Hope it helps! [b]TL;DR[/b] If you're on TIM (Italy) and Destiny 2 keeps giving you [b]CENTIPEDE[/b] (CURRANT, or other connection issue related errors) at launch or [b]"Destiny 2 servers are not available"[/b] during Signing In, check the first two numbers of your public IPv4 address. In our tests the game failed whenever the line had an address starting with [b]87.20[/b] or [b]87.21[/b], and worked on the very same line and PC with addresses starting with [b]79[/b]. Getting a new IP from your router, or using a VPN, works around it. Router settings, DNS, port forwarding and network cards made no difference. [b]SYMPTOMS[/b] - CENTIPEDE / CURRANT at startup, other connection error even in chat while playing, on and off since early 2025 - Mobile hotspot: mostly works (occasional CURRANT) - VPN: works with no errors at all. The VPN used in this trouble shooting was "Mysterious VPN" (so called) - Setup: friend's setup with PC/Steam, TIM fiber with the TIM Hub Pro router. The second household (mine) had a different router and a different PC (same ISP, same router model, same region) and no problems while loggin or playing [b]WHAT DID NOT HELP[/b] Changing DNS (e.g. Cloudflare), port forwarding, lowering the router's security settings, a static local IP for the PC, switching between two different network cards, IPv6 (not in use). [b]KEY TESTS[/b] - Mobile hotspot: works. Bypassing the fiber line and its IP mostly fixes it. - VPN: works. A different exit IP fixes it. - VPN exits on other TIM lines (two regions, residential and business): work. TIM's network in general reaches Bungie fine. - Reboot router only: CENTIPEDE, with an 87.21.x.x address. - Reboot again: works, with a 79.x.x.x address. - Second household, never had issues (it was on 79.x): rebooted its router without touching anything else, got an 87.20.x.x address, and login failed immediately. [b]The problem follows the IP range, not the hardware or the settings.[/b] - "retail" vs "business" label in TIM's hostname: no pattern. - Geolocation of all the ranges: all in Italy, so not a geo-block. [b]THE UPnP FALSE LEAD[/b] Toggling UPnP and rebooting the TIM Hub looked like a fix. It wasn't. Every reboot reconnects the line and TIM usually assigns a new public IP, so UPnP got the credit for what was really just an IP change. [b]WHERE THE CONNECTION BREAKS[/b] In Windows Resource Monitor (resmon > Network tab > tick destiny2.exe), during a failing session the PC keeps sending to a Bungie game server and gets nothing back (about 1 B/s out, 0 B/s in). At the same time, Akamai's CDN and other Bungie services reply normally. In a working session, traffic flows both ways with a server in the same Bungie address block, so it's not a "bad server" assignment. Public routing data (RIPEstat) shows that Bungie's game server prefixes (AS394073) are reached only through Akamai Prolexic (AS32787), Akamai's DDoS protection service. TIM (AS3269) announces the affected ranges normally. [b]Most likely cause:[/b] a Prolexic filter dropping traffic for those TIM ranges, or a broken return path toward them. This part is not confirmed. [b]Confidence:[/b] dependence on the IP range: high. Missing server replies: medium-high (one snapshot). Prolexic as the cause: medium. Only 87.20/87.21 affected: low (small sample; other ranges or other ISPs may be hit too). [b]HOW TO CHECK IF YOU'RE AFFECTED[/b] Find your public IPv4 with any "what is my IP" site. Please don't post your full IP anywhere: the first two numbers are enough. Or open PowerShell (Start > type PowerShell), paste these three lines and press Enter. It only shows the first two numbers: [quote]$ip = (Invoke-RestMethod https://ipinfo.io/json -TimeoutSec 10).ip $first, $second, $rest = $ip.Split('.') if ("$first.$second" -in '87.20','87.21') { Write-Host "$first.$second.x.x -> known problem range: reconnect your router" -ForegroundColor Red } else { Write-Host "$first.$second.x.x -> not a known problem range" -ForegroundColor Green }[/quote] [b]WORKAROUNDS[/b] 1. [b]Get a new IP.[/b] In the TIM Hub web panel, disconnect and reconnect the internet connection (or reboot the router), then check again. Repeat until you're outside 87.20 / 87.21. 79.x addresses worked in every test we ran. Once you have a good one, avoid unnecessary reboots. 2. [b]VPN.[/b] Any exit outside the affected ranges should work. Pick a nearby server to keep latency down. 3. [b]Mobile hotspot[/b] as an emergency option. Less stable, expect the occasional CURRANT. Router setup: UPnP on, no manual port forwarding, no DMZ. Bungie advises against combining UPnP with port forwarding. [b]TO BUNGIE[/b] Could you check whether the TIM (AS3269) ranges 87.20.x.x and 87.21.x.x are being filtered on the way to your game servers? This was reproduced in two households with different routers and PCs: game server traffic gets no reply only while the line is on those ranges. [b]EVERYONE ELSE:[/b] if you're on TIM or another Italian ISP, please reply with your ISP, [b]only the first two numbers[/b] of your IP (e.g. "87.21"), the result (works / CENTIPEDE / other error) and date/time. More reports make this harder to ignore. A logging script and how to report it to TIM are in the first reply. [b]EDIT:[/b] Since the ISP can change your IP while you're online, me and my friend go the [b]95.x.x.x[/b] IPs and when still got the same problems. CENTIPEDE happens 80% of the times with this IP ranges. Sometimes you can log in the game and even play smoothly but if you close and re-open the game or change planet / location the connection can break again and show you the error while trying to connect. If anything new happens, the post will be updated (or a comment will be added).