Weird situation

[SauRoNZA]

Traceroute for https://gofile.io

Remove the https:// otherwise it will never work.

 

[elf_lord_ZC5]

Ignore the linux stuff. From the command line, try

nslookup gofile.io

That will do a DNS lookup using your current DNS server

Then try:

nslookup gofile.io 1.1.1.1

If the first one fails and the second one works, set your DNS to 1.1.1.1

Will give that a shot

 

[elf_lord_ZC5]

Microsoft Windows [Version 10.0.19045.3930]
(c) Microsoft Corporation. All rights reserved.

C:\Users\ME>tracert gofile.io

Tracing route to gofile.io [151.80.29.83]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 25 ms 34 ms 17 ms 10.11.65.193
4 * * * Request timed out.
5 36 ms 19 ms 19 ms 10.195.18.1
6 27 ms 19 ms 18 ms 196.250.239.56
7 188 ms 179 ms 179 ms 154.66.247.217
8 179 ms 180 ms 185 ms 154.66.247.234
9 168 ms 163 ms 155 ms 154.66.247.99
10 193 ms 181 ms 176 ms 154.66.247.85
11 175 ms 179 ms 179 ms ovh.mrs.franceix.net [37.49.232.27]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 201 ms 199 ms 199 ms ns3048708.ip-151-80-29.eu [151.80.29.83]

Trace complete.

C:\Users\ME>

 

[elf_lord_ZC5]

Microsoft Windows [Version 10.0.19045.3930]
(c) Microsoft Corporation. All rights reserved.

C:\Users\ME>nslookup gofile.io
Server: homerouter.cpe
Address: fe80::32aa:e4ff:fea4:97a4

Non-authoritative answer:
Name: gofile.io
Addresses: 51.38.43.18
151.80.29.83
51.178.66.33


C:\Users\ME>

 

[WAslayer]

The traceroute and nslookup results indicate that there might be an issue with the route to gofile.io from your network. The traceroute shows timeouts at several hops, indicating that the connection is not reaching its destination effectively.

Possible explanations could be network congestion, routing issues, or restrictions by your ISP. The fact that your cellphone and laptop connect via a VPN suggests that the VPN is providing an alternate route, bypassing the issues present in the direct connection.

To resolve this, you might want to contact your ISP, share the traceroute results with them, and inquire if there are any known issues or restrictions to gofile.io. They may be able to provide more insights or suggest solutions to improve the direct connection. Additionally, you can continue using the VPN as a workaround until the direct connection issue is resolved.

The traceroute is fine.. the timeouts on the several hops are just devices that don't respond to ping requests..

What matters is whether the destination IP address responds, which it does, so there is an established and working route to the server..

We can conclude from the working traceroute then, that there is something likely at the network or application layer blocking the request for some reason..

 

[elf_lord_ZC5]

The traceroute is fine.. the timeouts on the several hops are just devices that don't respond to ping requests..

What matters is whether the destination IP address responds, which it does, so there is an established and working route to the server..

We can conclude from the working traceroute then, that there is something likely at the network or application layer blocking the request for some reason..

I can now reach gofile.io again. Normally.


It seems that BEIN Sports had a blanket blocking order out, during AFCON to stop pirate streams. I suspect that routing to gofile.io got caught in the fallout, as they are in France where the blocking took place. Happened upon an article on this while browsing. Not certain, but may explain the issue.