Anomaly
Tor is likely blocked
Belarus
Country
AS42772
Network
October 06, 2021, 04:36 AM UTC
Date & Time
Circumvention
Runtime: 4m 28.7s
On October 06, 2021, 04:36 AM UTC, Tor did not appear to work on AS42772 in Belarus.
The OONI Probe Tor test failed in performing certain measurements. More details are available through the network measurement data provided below.
This suggests that Tor may have been blocked on this network.
However, false positives can occur.
Tor Browser Bridges
7/15 OK
Tor Directory Authorities
0/10 OK
Name | Address | Type | Connect | Handshake |
---|---|---|---|---|
moria1 | 128.31.0.39:9101 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
moria1 | 128.31.0.39:9131 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
gabelmoo | 131.188.40.189:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
gabelmoo | 131.188.40.189:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
Faravahar | 154.35.175.225:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
Faravahar | 154.35.175.225:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
maatuska | 171.25.193.9:443 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
maatuska | 171.25.193.9:80 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
dannenberg | 193.23.244.244:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
dannenberg | 193.23.244.244:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
longclaw | 199.58.81.140:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: No connection could be made because the target machine actively refused it. | N/A |
longclaw | 199.58.81.140:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
bastet | 204.13.164.118:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: No connection could be made because the target machine actively refused it. | N/A |
bastet | 204.13.164.118:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
2d7292b5163fb7de5b24cd04032c93a2d4c454431de3a00b5a6d4a3309529e49 | 193.11.166.194:27020 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
3fa772a44e07856b4c70e958b2f6dc8a29450a823509d5dbbf8b884e7fb5bb9d | 192.95.36.142:443 | obfs4 | N/A | |
dizum | 45.66.33.45:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
dizum | 45.66.33.45:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
49116bf72d336bb8724fd3a06a5afa7bbd4e7baef35fbcdb9a98d13e702270ad | 146.57.248.225:22 | obfs4 | N/A | |
4a330634c5d678887f0f7c299490af43a6ac9fa944a6cc2140ab264c9ec124a0 | 209.148.46.65:443 | obfs4 | N/A | |
548eebff71da6128321c3bc1c3ec12b5bfff277ef5cde32709a33e207b57f3e2 | 37.218.245.14:38224 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
5aeb9e43b43fc8a809b8d25aae968395a5ceea0e677caaf56e1c0a2ba002f5b5 | 193.11.166.194:27015 | obfs4 | N/A | |
Serge | 66.111.2.131:9001 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
Serge | 66.111.2.131:9030 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
75fe96d641a078fee06529af376d7f8c92757596e48558d5d02baa1e10321d10 | 45.145.95.6:27015 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
tor26 | 86.59.21.38:443 | or_port_dirauth | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
tor26 | 86.59.21.38:80 | dir_port | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
99e9adc8bba0d60982dbc655b5e8735d88ad788905c3713a39eff3224b617eeb | 38.229.1.78:80 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
9d735c6e70512123ab2c2fe966446b2345b352c512e9fb359f4b1673236e4d4a | 38.229.33.83:80 | obfs4 | N/A | |
b7c0e3f183ad85a6686ec68344765cec57906b215e7b82a98a9ca013cb980efa | 193.11.166.194:27025 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
b8de51da541ced804840b1d8fd24d5ff1cfdf07eae673dae38c2bc2cce594ddd | 85.31.186.26:443 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | N/A |
bc7bc5fb57052ee5252e807443b9ab67307dbdb5ce79187c4360182a300dd0f8 | 144.217.20.138:80 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: No connection could be made because the target machine actively refused it. | N/A |
d2d6e34abeda851f7cd37138ffafcce992b2ccdb0f263eb90ab75d7adbd5eeba | 85.31.186.98:443 | obfs4 | N/A | |
f855ba38d517d8589c16e1333ac23c6e516532cf036ab6f47b15030b40a3b6a6 | [2a0c:4d80:42:702::1]:27015 | obfs4 | unknown_failure: dial tcp [scrubbed]: connectex: A socket operation was attempted to an unreachable network. | N/A |
fa69b2ee7a7c8975af2452ecd566f67a6459d397a4cefc30be86a670675cdc23 | 51.222.13.177:80 | obfs4 | N/A |
Resolver
Resolver ASN
AS42
Resolver IP
74.63.24.246
Resolver Network Name
WoodyNet
Report ID
20211006T043648Z_tor_BY_42772_n1_yXQb52itnWQoDaBM
Platform
windows
Software Name
ooniprobe-desktop-unattended (3.10.0-beta.3)
Measurement Engine
ooniprobe-engine (3.10.0-beta.3)