Repository navigation
fix(data): azirevpn's canary date - #219
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Category
Data update
Overview
Two-week recheck of AzireVPN. The only thing that moved is the warrant canary, which was signed again on 29 October and still says no warrants.
Everything else matches: 179 servers in 62 locations across 36 countries, prices unchanged, the blog's last post is from July, NVD has nothing on it, and the legal links still go to Malwarebytes' policy. The server list names an ISP per location (Datapacket, xTom, Arelion and so on), but that's upstream transit, so the "we own 100% of our server infrastructure" claim still stands as claimed.
Sources
Issue number
None
Additional info
No conflicts of interest.
Footnotes
AzireVPN warrant canary ↩
AzireVPN servers ↩
AzireVPN security ↩