Can you open https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html from mainland China?
No.
It's blocked — 100% of the last 1 conclusive tests failed in mainland China.
Access www.washingtonpost.com with GreatFireVPN →Frequently asked questions
Is https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html blocked in mainland China right now?
As of the last test on 2026-07-25, https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html is 100% blocked in mainland China, based on GreatFire's live Great Firewall measurements.
Why is https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html blocked in mainland China?
It's blocked — 100% of the last 1 conclusive tests failed in mainland China.
Since when has https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html been blocked?
GreatFire has recorded interference with https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html from mainland China since 2019-06-03.
How can I access https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html from mainland China?
You need a circumvention tool such as a VPN. GreatFireVPN, built by GreatFire, is designed to bypass the Great Firewall and reach sites like www.washingtonpost.com.
https://www.washingtonpost.com/world/asia_pacific/prosperity-repression-mark-china-30-years-after-tiananmen/2019/06/02/e93f6504-85ac-11e9-9d73-e2ba6bbf1b9b_story.html · JSON