AdGuard had 44 outages in the last 2 years totaling 469h 33m of downtime — averaging 1.8 incidents per month.
There were 44 AdGuard outages since August 13, 2024 totaling 469h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.
Users may experience slow or failed downloads of AdGuard distribution packages caused by an ongoing incident on the CDN provider side. Some regions and platforms can be affected intermittently while traffic is being rerouted and mitigations are applied.
The incident has been resolved
In Russia, AdGuard websites are partially unavailable.
The incident has been resolved
Some users may receive errors on filters update due to CDN issues. We're currently investigating the situation
The incident has been resolved
We are investigating the reasons for the delay in displaying query logs.
All missing logs were delivered
Due to global traffic rerouting in Southeast Asia, some AdGuard DNS users may experience increased DNS resolution times. We are monitoring the situation and working to mitigate the impact.
We applied manual routing adjustments to stabilize the load. No downtime was observed during the incident.
We have detected an issue affecting our email delivery system. As this affects transactional emails (notifications, password resets, confirmations), all services are currently impacted.
The issue has been fully resolved, and the email service is back to normal. We have confirmed that no emails were lost; however, there was a slight delay in their delivery. All queued messages have now been successfully processed. We apologize for the inconvenience.
Due to a temporary issue with one of our internal systems, the VPN service may not work properly, particularly when trying to load or display the list of server locations.
The internal system in question is opertational, the issue has been resolved, and we don't expect any lingering impact.
Due to network issues in Singapore DC some users may have connection issues. We are currently invetigating
We didn't receive an information from our DC, but networking was restored. Most users shouldn't have any issues now, we're working on a full service restoration.
All locations and servers are now in operational mode
We are seeing global connectivity issues in South America that may impact AdGuard DNS availability.
We are currently mitigating traffic overload in SA location
We continue to restore service availability.
Issue was resolved. AdGuard DNS is fully operational.
There are issues with loading static content on AdGuard websites for users in RU region. We are currently investigating
The issue was resolved
We’re investigating global connectivity issues affecting multiple regions and causing degraded service performance.
The incident has been resolved
Fix was already implemented. Service is restoring right now. We are monitoring the situation.
This incident has been resolved.
Read our [blog](https://adguard-vpn.com/en/blog/redis-kubernetes-vpn-incident-post-mortem.html) to see what happened
We're currently investigating the issue
The issue is identified. We are applying the fix to restore the service.
The issue has been resolved. We will continue to monitor the situation and will provide a more detailed update regarding the causes of the incident at a later date.
You can find more technical details about this incident in [our blog](https://adguard-dns.io/en/blog/partial-adguard-dns-outage-11-25.html)
We are currently observing connectivity issues affecting AdGuard DNS servers in Singapore. We are working to identify and mitigate the issue.
Issue was identified. We are currently working on service restore.
Fix was implemented, we're monitoring now
Issue was resolved
We’re experiencing an outage affecting access to the site from EU region. The issue originates from an upstream network provider, causing intermittent failures and timeouts. Our systems are operating normally, but external connectivity is degraded. We’re monitoring the situation and will restore full availability as soon as the upstream provider resolves the problem.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently observing connectivity issues affecting AdGuard DNS in Miami, FL and working to mitigate the issue
This Incident has been resolved
We’re performing a hardware upgrade on our servers in Johannesburg. All traffic is temporarily rerouted to our European points of presence, which may slightly increase latency for users in the African region over the next 60 minutes.
We’ve started a hardware upgrade.
This Incident has been resolved
We are currently observing connectivity issues affecting AdGuard DNS in the Southeast Asia region. The disruption is caused by network problems among several backbone providers operating in the area.
We are continuing to investigate this issue.
According to our monitoring, the issue has been resolved, but we continue to observe the situation.
This Incident has been resolved
We are performing scheduled hardware upgrades on our servers in Chicago. We do not anticipate any outages, but as a precaution, part of the IPv4 traffic will be rerouted through other North American locations.
We're currently performing hardware upgrade
This Incident has been resolved
We're currently investigating the issue which causes a severe delay in query log updates in private AdGuard DNS service. We presume that no logs have been lost, and they will arrive when the issue is solved.
The issue has been identified, currently restoring missing query logs.
At this moment we can confirm the following: * No query logs were missed * Some query logs for 23.09.2025 are delivered twice - we will implement the fix today * Some old and new logs are shown in control panel with significant delay - we await resolving in the next 2-3 hours
All missing logs are now visible in UI. We are working on a deduplication of 23.09.2025 logs
All logs for 23.09.2025 will be refilled
All missing logs will become visible in the next 90 minutes
A fix has been implemented and we are monitoring the results.
This incident has been resolved. We will add postmortem soon
We are currently experiencing a delay in the display of DNS query logs. DNS resolution itself is fully operational and unaffected — this issue does not impact filtering or performance. Our team is working on resolving the problem.
This incident has been resolved.
We're currently investigating the issue of some DNS query logs not being visible on the dashboard and query log page for some clients.
While the investigation is still ongoing, we're confident that no query logs are lost, and they are currently appearing on client's dashboard and query logs page with a delay of approximately 30 minutes.
The issue has been resolved. All missing queue logs should now be visible on the query log page, and all stats on the dashboard should match accordingly
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.