The United States has a gun violence data problem — not a shortage of shootings, but a critical failure of infrastructure to track, report, and surface them in real time. The information exists. What's been missing is the pipeline to make it useful.
The Federal Data Lag That's Costing Lives (and Decisions)
The FBI's Uniform Crime Report — the official federal benchmark for crime statistics in the United States — is published with an 18-month lag. When researchers, insurers, developers, and policymakers reach for national gun violence data today in early 2026, the best they can get from the FBI is a snapshot from mid-2024. That's not a data point. That's a history lesson.
The problem deepened when the FBI transitioned from its legacy Summary Reporting System (SRS) to the National Incident-Based Reporting System (NIBRS) in 2021. The transition was the right long-term move — NIBRS captures far more granular incident data — but in the short term, it created a reporting gap. Major agencies including the NYPD failed to submit data that year, leaving a hole in the national record and making the 2021 figures nearly unusable for trend analysis. The result: the country's most consequential crime data system was effectively blind during one of the most volatile years for violent crime in recent memory.
Other national trackers have tried to fill the void. The Gun Violence Archive, a nonprofit, compiles incident-level shooting data from news sources, police blotters, and social media — and is among the most cited sources in journalism. But its coverage is uneven, its methodology is reactive rather than systematic, and it still can't tell you what happened at 1130 North Pulaski Road at 11pm last Tuesday. That level of resolution requires something different.
Why City-Level Aggregates Are the Wrong Unit of Analysis
The reflexive move in gun violence discourse is to rank cities. Chicago. Baltimore. New Orleans. The top-ten-most-dangerous lists that get recycled endlessly in political arguments and real estate conversations. These rankings have a seductive simplicity — and they're almost always misleading.
A city-level homicide rate tells you almost nothing about where in a city the risk is concentrated. In Baltimore, for example, gun violence is heavily concentrated in a handful of zip codes. A family moving to Roland Park and a family moving to Cherry Hill are not making the same safety decision, but city-level statistics treat them identically. The same dynamic plays out in every major American city: the aggregate masks the neighborhood-level reality by orders of magnitude.
The Real-Time Crime Index (RTCI), maintained by AH Datalytics at realtimecrimeindex.com, has made important progress on the timeliness problem. It aggregates reported crime data from hundreds of law enforcement agencies nationwide with roughly a 45-day lag — dramatically better than the FBI's 18-month window. But even the RTCI explicitly warns against using its data for city-to-city rankings. The coverage is uneven. Not every city submits. Methodology varies by department. And critically, the RTCI operates at the agency level — not the address level.
For public safety data to be genuinely actionable, you need address-level resolution. You need to know not just that a city had 400 shootings in the last 60 days, but where those shootings happened — and whether a specific address, neighborhood, or corridor is in the blast radius.
ShootingsNear.me: What Real-Time Hyperlocal Data Actually Looks Like
SpotCrime built ShootingsNear.me as a companion tool to demonstrate exactly this: what happens when you apply a real-time, address-level data feed specifically to gun violence. The platform currently tracks shooting incidents across 12 U.S. cities, updated daily, with a rolling 60-day window.
The current data — 6,463 shooting incidents recorded across those 12 cities in just 60 days — is striking not just for its volume, but for what the distribution reveals.
Shooting Incidents — Last 60 Days (ShootingsNear.me)
Source: ShootingsNear.me — SpotCrime data. 12 cities tracked. Updated daily.
The Seattle Anomaly — and What the Data Is Actually Capturing
If you looked at that table and did a double-take at Seattle — 1,293 incidents, nearly 400 more than San Antonio in second place, more than five times Chicago's count — you're not alone. Seattle doesn't typically appear near the top of any gun violence ranking. So what's going on?
The answer illustrates something fundamental about how crime data works in practice. SpotCrime's data is sourced directly from police department incident reports, which means coverage quality varies based on how consistently and completely each department submits. Seattle's Police Department has historically maintained strong public data transparency and comprehensive incident reporting. Other cities on the list may be undercounting due to reporting gaps, department methodology differences, or delayed uploads.
This is not a flaw in the system — it's important signal. Any analyst, developer, or platform building on crime data needs to understand that raw incident counts are not apples-to-apples comparisons across jurisdictions. They reflect both the underlying reality and the quality of the reporting infrastructure. Chicago's 224 incidents are not evidence that Chicago has dramatically fewer shootings than Seattle. They more likely reflect a difference in what data is being captured, submitted, and surfaced.
This is precisely why SpotCrime normalizes and verifies its data before serving it through the API — and why neighborhood safety ratings incorporate multiple signals rather than raw incident counts alone.
How Developers and Platforms Are Using Shooting Data
The use cases for hyperlocal shooting data break down into three broad categories: consumer safety applications, professional risk assessment, and research and policy tooling.
Consumer safety apps.Family safety platforms, neighborhood alert systems, and personal security tools are increasingly integrating real-time crime feeds. The value proposition is clear: parents want to know if there was a shooting near their child's school. Commuters want to know if their usual route has seen elevated incidents. Renters evaluating a new apartment want to understand the safety profile of the surrounding blocks — not the city average.
Real estate and property platforms.Crime data has become one of the most-requested features on real estate portals. neighborhood safety score, SpotCrime's neighborhood safety rating, is designed specifically for this integration: a normalized, explainable score that can be embedded in a property listing without requiring the platform to become a crime data analyst. When a buyer sees a safety score, they want to know it's based on real incident data at an address level — not a zip-code approximation built from 18-month-old FBI tables.
Corporate security and executive protection.Enterprise security teams tracking executive travel, commercial real estate assessments, and site risk analysis are among the most sophisticated consumers of crime API data. For these users, the question isn't whether a city is safe — it's whether a specific hotel, office building, or conference venue has seen elevated violent incident activity in the past 90 days. That requires address-level data and recent trend lines, not annual statistics.
The Technical Architecture of a Real-Time Shooting Feed
Building a real-time shooting tracker at scale is not a web-scraping project. The data ingestion pipeline has to handle thousands of police department feeds — each with its own format, update cadence, and classification schema — and normalize them into a unified incident model. A “shooting” in one jurisdiction's records might be classified as “aggravated assault with a firearm,” “shots fired,” or “person shot” in another.
SpotCrime ingests incident data from law enforcement agencies covering 22,000+ U.S. cities and applies classification normalization to map these varied descriptions into consistent crime type categories. The result is an address-level incident database that's updated as new reports become available — not monthly, not annually, but continuously.
For developers querying the SpotCrime API, this means you don't have to build the normalization layer. You get a consistent response schema regardless of which jurisdiction you're querying: incident type, coordinates, address, date and time, and — where available — case status. Combined with neighborhood safety score and 36-month trend data, the API gives you both the real-time snapshot and the longitudinal context needed to understand whether an area is trending safer or more dangerous.
The Bigger Picture: Real-Time Crime Data as Critical Infrastructure
America had a historic homicide decline between 2022 and 2025 — murder rates fell to roughly 14,000 annual homicides by 2025, levels not seen in decades. That's genuinely good news. But the decline in aggregate statistics doesn't mean gun violence is evenly distributed, consistently tracked, or adequately understood at the neighborhood level.
The cities at the top of the ShootingsNear.me data — Baltimore, Indianapolis, New Orleans, Detroit — are cities where gun violence remains concentrated, often in the same corridors and zip codes that have borne the burden for decades. A national crime drop doesn't automatically translate into safety for a family on a specific block in West Baltimore or the near-east side of Indianapolis.
This is the gap that hyperlocal crime data infrastructure exists to close. Not to replace FBI statistics or public health surveillance, but to add the resolution layer that federal data can't provide. Real-time, address-level incident feeds make it possible to build applications that give people accurate, actionable safety information — not three-year-old national averages or politically motivated city rankings.
As SpotCrime's ongoing litigation against the LAPDmakes clear, access to accurate, timely crime data is increasingly a public interest issue, not just a commercial one. When police departments withhold or delay incident reporting, the damage isn't just to news organizations or researchers — it degrades the quality of every downstream safety tool, from insurance models to family safety apps to the AI agents increasingly being tasked with assessing risk in the physical world.
The infrastructure for better gun violence data exists. The demand for it — from developers, platforms, researchers, and the public — is growing fast. Closing the gap between what's possible and what's currently available is, at its core, what real-time crime data APIs are for.
Access Address-Level Crime Data
Real-time incidents · neighborhood safety ratings · 36-month trends · 22,000+ US cities. Normalized and verified — because raw data isn't enough.