How to read DC pest complaint hotspots before renting

DC publishes 311 service requests through an ArcGIS FeatureServer at maps2.dcgis.dc.gov. RentSift queries layers 21 (2026), 18 (2025), and 16 (2024) in parallel, deduplicates by service request ID, and filters to recent records.

Pest complaints are identified by matching SERVICECODEDESCRIPTION against keywords such as rodent, rat, roach, pest, mice, and mouse. The report then separates requests within ~150 ft of the geocoded search pin from requests in the rest of the 0.25-mile radius.

The useful measure for a renter is not a citywide ranking. It is how many pest-related requests the source returned in the close band versus the wider radius, how recent they are, and what to verify in person. Even the close band is a proximity proxy, not an exact-address or property-level match.

Older multifamily buildings, restaurant corridors, alleys, commercial trash collection, and high resident reporting can all increase 311 pest counts. Dense areas often generate more records because there are more people, more buildings, and more reasons to call 311.

That does not mean every building in a dense neighborhood has a pest problem. A recent request within ~150 ft of the search pin is a stronger proximity signal than a request farther away, but neither establishes a problem at the searched building.

The same density that supports restaurants, transit, and grocery access can also create maintenance pressure. Renters should treat the record as a question to ask management, not as proof about a unit they have not inspected.

Low returned counts can mean fewer problems, lower building density, fewer rental buildings, resolved issues, lower 311 usage, source lag, or a missed geocode. The report should never convert a zero into a cleanliness guarantee.

This is why RentSift shows the source, radius, and scope. A clean-looking result should still be paired with a walkthrough: check trash storage, basement hallways, exterior gaps, and whether management has a written pest-control schedule.

Run an address report for the building's search pin. The complaints section separates requests within ~150 ft of that pin from the rest of the nearby context inside the 0.25-mile radius. The close band can include adjacent properties or imprecise source coordinates and should not be read as exact-building evidence.

Pest pressure near a building is one of the few things a renter cannot fix after move-in. An old complaint might mean the problem was resolved. A recent cluster should prompt direct questions about treatment history, trash handling, and whether the unit has had prior pest work.