AdguardTeam / AdguardTeam/AdGuardDNS
Routing regression for AdGuard DNS Free Anycast from Azerbaijan (Azfiber)
- Linguagem predominante
- Go
- Estrelas
- 952
- Forks
- 82
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
### Platform
Android
### Protocol
Regular
### Do you use AdGuard app?
No I don't
### Your configuration
Device: Samsung Galaxy A40
Android: 11
ISP: Azfiber (Azerbaijan)
Connection: Wi-Fi
AdGuard DNS Free
Assigned DNS servers:
94.140.14.49
94.140.14.59
### Traceroute to AdGuard DNS
Traceroute to 94.140.14.14
1. 192.168.101.1 - 2.08 ms / 1.76 ms / 2.61 ms
2. 172.16.100.250 - no reply
3. 172.16.74.1 - no reply
4. 109.235.192.101 - 8.71 ms / 7.70 ms / 7.23 ms
5. 10.240.164.38 - no reply
6. * - no reply
7. 187.16.210.94 - no reply
8. 79.127.195.140 - no reply
9. 94.140.14.14 (dns.adguard-dns.com) - 265 ms / 264 ms / 264 ms
### Issue Details
Previously, after a routing optimization by the AdGuard team, latency from my ISP (Azfiber, Azerbaijan) to AdGuard DNS was around 63 ms.
Recently, the latency increased significantly.
The automatically assigned AdGuard DNS Free servers (94.140.14.49 and 94.140.14.59) both consistently respond with approximately 265–275 ms latency.
The issue is persistent and reproducible.
### Expected Behavior
Traffic from Azfiber (Azerbaijan) should be routed to the nearest AdGuard Anycast PoP with latency similar to the previous 63 ms.
### Actual Behavior
AdGuard DNS Free
94.140.14.49: ~265–275 ms
94.140.14.59: ~265–275 ms
Packet loss: 0%
For comparison:
Cloudflare (1.1.1.1): ~13 ms
Google DNS (8.8.8.8): ~46–52 ms
### Screenshots
### Additional Information
This worked correctly before.
After a previous routing optimization, latency was approximately 63 ms from the same ISP.
It now appears that the Anycast routing has regressed.
Could you please check the routing/BGP announcements for traffic coming from Azfiber (Azerbaijan)?
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Avaliação
Esta issue ainda não foi avaliada.