Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C censorship-analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • censorship-analysis
  • Issues
  • #40002
Closed
Open
Created Feb 25, 2021 by Cecylia Bocovich@cohoshOwner

Possible new blocking event in Belarus

We heard from a user in Belarus that their obfs4 bridge stopped working. This corresponds with a recent metrics graph that shows a drop in obfs4 usage and increase in meek:

belarus

Private obfs4 bridges worked, so the blocking is almost certainly by IP address. It's still unclear whether this blocking only includes default bridges, or if there is some enumeration of BridgeDB bridges going on as well.

Assignee
Assign to
Time tracking