Tedata egypt ping issue


#1

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\newstar>tracert 1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 3 ms 2 ms <1 ms 192.168.1.1
2 22 ms 25 ms 25 ms host-41.236.117.129.tedata.net [41.236.117.129]

3 40 ms 27 ms 21 ms 10.37.75.1
4 25 ms 26 ms * 10.37.75.2
5 27 ms 31 ms 30 ms 10.37.107.137
6 32 ms 42 ms 37 ms 10.37.24.125
7 28 ms 32 ms 31 ms 10.36.19.169
8 29 ms 42 ms 32 ms host-213.158.191.230.tedata.net [213.158.191.230
]
9 26 ms 30 ms 28 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.

C:\Users\newstar>t


#2

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\newstar>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

DNS request timed out.
timeout was 2 seconds.
*** Request to 1dot1dot1dot1.cloudflare-dns.com timed-out

C:\Users\newstar>


#3

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\newstar>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

DNS request timed out.
timeout was 2 seconds.
*** Request to 1dot1dot1dot1.cloudflare-dns.com timed-out

C:\Users\newstar>nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "cai01"

C:\Users\newstar>


#4

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\newstar>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

DNS request timed out.
timeout was 2 seconds.
*** Request to 1dot1dot1dot1.cloudflare-dns.com timed-out

C:\Users\newstar>nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "cai01"

C:\Users\newstar>tracert 1.0.0.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 93 ms 23 ms 21 ms host-41.236.117.129.tedata.net [41.236.117.129]

3 22 ms 30 ms 23 ms 10.37.75.1
4 258 ms 29 ms 28 ms 10.37.75.2
5 32 ms 29 ms 43 ms 10.37.107.137
6 33 ms 36 ms 31 ms 10.37.41.249
7 28 ms 27 ms 33 ms 10.36.20.101
8 25 ms 29 ms 24 ms 10.36.19.197
9 49 ms 34 ms 33 ms host-213.158.191.230.tedata.net [213.158.191.230
]
10 26 ms 30 ms 31 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Trace complete.

C:\Users\newstar>


#5

thats update of the previous thread because cloudflare is having issue with isp tedata which is known as we hope it get resolved soon


#6

Any news about it ?


#7

It’s almost time for my after lunch nap, so I’m having difficulty focusing.

It looks to me like you’re able to traceroute to both Cloudflare DNS server IPv4 addresses.

You can lookup the POP for 1.1.1.1 (cai01), but not 1.0.0.1. Is this the issue?


#8

Well most likely because sometimes I can’t reach 1.1.1.1 and it turns into slow


#9

Any news about it ?


#10

Thanks for all the information here. I’ve gone back through your previous posts about this issue as well. Can I ask you to clarify a couple things:

  1. How often do you see these timeouts, like you demonstrated on nslookup? Is it every other request? Only on some days?
  2. When you’re seeing these timeouts, does the traceroute still look like the one you posted? As in no packet loss, latency around 30ms, same number of hops?

#11

Isee timeout some days not every time isee no packet loss but number of ping changes means not stable


#12

Any news about it ?


#13

Thanks for the ping here.

We need to determine, when your connection to 1.1.1.1 is timing out, where that failure is occurring. If it’s intermittent, that makes it trickier to do. For Windows, I think the best option out there is WinMTR, although it’s pretty old at this point.

The next time you see one of these timeouts, could you have WinMTR ready to run a traceroute to 1.1.1.1? I’d suggest, to be thorough, that you let it run for 100 packets and provide us with the output. That should give us a better idea where the problem is.


#14

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 58 58 0 4 21 4
host-41.236.117.129.tedata.net - 0 58 58 21 27 107 24
10.37.75.1 - 4 51 49 21 25 44 27
10.37.75.2 - 2 55 54 0 30 78 25
10.37.107.137 - 13 39 34 0 34 85 35
10.38.15.121 - 4 51 49 0 32 84 47
10.36.19.161 - 10 43 39 24 28 59 25
10.37.85.102 - 7 47 44 0 30 82 29
host-213.158.191.230.tedata.net - 13 39 34 0 29 55 26
1dot1dot1dot1.cloudflare-dns.com - 10 44 40 0 32 84 26
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


#15

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 6 6 0 1 2 1
host-41.236.117.129.tedata.net - 0 6 6 22 23 25 22
10.37.75.1 - 50 2 1 0 23 23 23
10.37.75.2 - 50 2 1 0 27 27 27
No response from host - 100 2 0 0 0 0 0
10.38.15.121 - 50 2 1 0 26 26 26
10.36.19.161 - 50 2 1 0 27 27 27
No response from host - 100 2 0 0 0 0 0
No response from host - 100 2 0 0 0 0 0
1dot1dot1dot1.cloudflare-dns.com - 0 6 6 24 26 29 26
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


#16
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 6 6 0 1 2 1
host-41.236.117.129.tedata.net 0 6 6 22 23 25 22
10.37.75.1 50 2 1 0 23 23 23
10.37.75.2 50 2 1 0 27 27 27
No response from host 100 2 0 0 0 0 0
10.38.15.121 50 2 1 0 26 26 26
10.36.19.161 50 2 1 0 27 27 27
No response from host 100 2 0 0 0 0 0
No response from host 100 2 0 0 0 0 0
1dot1dot1dot1.cloudflare-dns.com 0 6 6 24 26 29 26

#17

Any news about it ?


#18

It looks like you’re seeing packet loss starting in your ISP’s internal network. Do you only see this kind of packet loss to 1.1.1.1, or if you run a similar MTR to 8.8.8.8 or 9.9.9.9 do you see similar loss %? Can you share these results with them and see if they can help improve your internet reliability?


#19

Well only on 1.1.1.1 also Itried with them a lot they can’t even help