In our work at the U.S.-Mexico border, we regularly hear about abuses or improper law enforcement behavior by U.S. security agencies. But so often, whatever happens gets overtaken by the next events, forgotten.

I wanted to start damming up this steady, alarming stream going by us all the time. So, many months ago, I set up a new WordPress install, and my staff and I started throwing into it everything we’ve seen and heard since 2020 about abuses committed at the border.

The result is a database that we’re hosting at borderoversight.org. It has more than 220 entries so far, fully cited. We’ve captured these events and allegations, and organized them by category, place, agency, victim, and “accountability status.”

I’m not exactly “proud” of what we’ve created here. Actually, trying to read through it is a monstrous experience. There’s only so many use-of-force incidents, high-speed vehicle pursuits, spied-on U.S. citizens, Facebook slurs, non-return of belongings, dangerous deportations, and timid oversight that one can take in a single sitting. The picture is grim.

I don’t want this to be viewed, though, as an attack on the individuals who’ve chosen to build a career as a Border Patrol agent or CBP officer. I have met many agents and officers, and found nearly all to be decent and honorable people. But take CBP and Border Patrol as a whole, and something changes. Organizational cultures are powerful.

Our maintenance of borderoversight.org will be continuous: a database is never “done,” but we’ll use it to spin off a lot of other materials and carry out further work on what’s causing this problem and how to reform it.

I hope you find it useful as we work for greater accountability and cultural change at these agencies.

Here are some resources:

  • We added a page with links to reports about the border: from WOLA, from the U.S. and other governments, from non-governmental colleagues, and from the media. Organized by category. More than 270 of them so far are at borderoversight.org/reports.

And here’s a quick video explaining this work: