Routing Issue [North Macedonia] Request timed out!

Diagnostic Tool Result

Hello, I have a fiber connection 100/100

why are these routing issues in MK?

tracert 1.1.1.1

Routenverfolgung zu one.one.one.one [1.1.1.1]
über maximal 30 Hops:

  1    <1 ms    <1 ms    <1 ms  192.168.100.1
  2     1 ms    <1 ms     1 ms  89.205.46.1.robi.com.mk [89.205.46.1]
  3   113 ms     2 ms    11 ms  89.205.126.1.robi.com.mk [89.205.126.1]
  4     4 ms     4 ms     4 ms  80.77.144.145
  5    13 ms    13 ms    13 ms  80.97.248.54
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 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     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Ablaufverfolgung beendet.

tracert 1.0.0.1

Routenverfolgung zu one.one.one.one [1.0.0.1]
über maximal 30 Hops:

  1    <1 ms    <1 ms    <1 ms  192.168.100.1
  2    <1 ms     1 ms     1 ms  89.205.46.1.robi.com.mk [89.205.46.1]
  3     2 ms     1 ms    <1 ms  89.205.126.1.robi.com.mk [89.205.126.1]
  4    11 ms     3 ms     3 ms  80.77.144.145
  5    14 ms    13 ms    13 ms  80.97.248.54
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 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     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Ablaufverfolgung beendet.



ping 1.1.1.1

Ping wird ausgeführt für 1.1.1.1 mit 32 Bytes Daten:
Antwort von 1.1.1.1: Bytes=32 Zeit=12ms TTL=59
Antwort von 1.1.1.1: Bytes=32 Zeit=12ms TTL=59
Antwort von 1.1.1.1: Bytes=32 Zeit=14ms TTL=59
Antwort von 1.1.1.1: Bytes=32 Zeit=12ms TTL=59

Ping-Statistik für 1.1.1.1:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 12ms, Maximum = 14ms, Mittelwert = 12ms


nslookup example.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Nicht autorisierende Antwort:
Name:    example.com
Addresses:  2606:2800:220:1:248:1893:25c8:1946
          93.184.216.34

nslookup example.com 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Nicht autorisierende Antwort:
Name:    example.com
Addresses:  2606:2800:220:1:248:1893:25c8:1946
          93.184.216.34

nslookup example.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Nicht autorisierende Antwort:
Name:    example.com
Addresses:  2606:2800:220:1:248:1893:25c8:1946
          93.184.216.34
		  
		  
nslookup -class=chaos -type=txt id.server 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Nicht autorisierende Antwort:
id.server       text =

        "OTP"

nslookup -class=chaos -type=txt id.server 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Nicht autorisierende Antwort:
id.server       text =

        "OTP"
		
nslookup -type=txt whoami.Cloudflare.com ns3.Cloudflare.com
Server:  UnKnown
Address:  162.159.0.33

whoami.Cloudflare.com   text =

        "89.205.46.71"

Looks all right to me. A timing out trace route is not necessarily an issue.

You seem to be able to reach the service, it resolves fine, and responds within reasonable time.

Oh so request timed out is not a problem?
but the ping requests are very high
for comparison 8.8.8.8.

ping 8.8.8.8
Ping is executed for 8.8.8.8 with 32 bytes of data:
Answer by 8.8.8.8: Bytes = 32 Time = 5ms TTL = 56
Answer by 8.8.8.8: Bytes = 32 Time = 5ms TTL = 56
Answer by 8.8.8.8: Bytes = 32 Time = 5ms TTL = 56
Answer by 8.8.8.8: Bytes = 32 Time = 5ms TTL = 56
Ping Statistics for 8.8.8.8:
     Packets: Sent = 4, Received = 4, Lost = 0
     (0% loss),
Approximately Times in millisec .:
     Minimum = 5ms, maximum = 5ms, mean = 5ms

Not necessarily, depends all on what the routers inbetween do.

Very high is very subjective :slight_smile:

12 milliseconds is actually quite a good figure. Your ISP might put you on a better route when it comes to Google, but seven milliseconds really are not that much of a difference.

In your case you seem to be routed to Romania.

That’s exactly what I mean, I’m going to Romania from Macedonia. That’s do bad …

Cloudflare does not have a datacentre in North Macedonia. The most suitable one will be Sofia but your ISP does not seem to route you in that direction. Thats something you need to clarify with your ISP I am afraid.

But again, 12 milliseconds is a good figure.

He seems to go to Sofia, though. Look at the 1.1.1.1 diagnostic tool, it says SOF.

Via HTTP. DNS goes to OTP.

Oh, didn’t scroll far enough… Seems extremely strange to have that difference.

How could I improve the DNS connection to Sofia

Considering you are in North Macedonia and you are going to another country, even if relatively close by means that you won’t be getting any better than this. Maybe going to Sofia will shave off a ms or two, but won’t be much.

The only chance would be talking to your ISP and figuring out why this discrepancy between HTTP and DNS traffic.

Okay, I’ll talk to the provider about what’s going on with HTTP and DNS traffic, but these people are very complicated.

Thank you

And I have to think about DNS over TLS or DNSCrypt.

I’m being monitored safely, in this country!!!

Sofia is not necessarily giving you a better latency. But again, 12 milliseconds is everything but a bad timing. In any case, this will be something you need to clarify with your ISP.