What is IncidentSource?
Updated
IncidentSource is an AI-powered event intelligence platform that converts public safety radio traffic into structured, real-time major-event awareness. It is built for people who need to know what is happening across fire, EMS, and rescue channels without monitoring scanners themselves. The site describes its core product as "Radiant Glow," which organizes audio, event context, location, and escalation activity into a system designed to surface what matters quickly.
What IncidentSource does
The platform listens to public safety communications and turns raw radio traffic into organized event records. According to the site, it processes:
- Audio — the underlying radio traffic tied to each event
- Event context — what type of incident is occurring (e.g., structure fire, shooting, MVA)
- Location — street-level or block-level addresses where available
- Escalation activity — signals that an incident is growing in severity, such as a working fire becoming a multiple alarm
The goal is situational awareness: instead of scanning dozens of feeds, you see a filtered list of major events with enough context to decide whether to pay attention.
How it is structured
The site presents activity through a live dashboard with aggregate counters and a rolling event list.
| Metric | Example value (last 24 hours) |
|---|---|
| Signals | 170,447 |
| Events | 27,997 |
| Major Events | 768 |
Below the counters, a Recent Major Events table shows the last 20 major events with a 15-minute delay. Each row includes:
- Date / Time (UTC)
- Major Event Type — e.g., MVA Extrication, Shooting, Structure Fire - Working Fire, Technical Rescue
- Context — the responding agency and jurisdiction, such as "NC-Charlotte / Mecklenburg County Fire/EMS"
- Location — a street address or block, e.g., "Asbury Ave, Charlotte, NC"
- View / Play — a link to open the event and its audio
This structure lets you scan by incident type, geography, or agency rather than by raw audio.
Who it is for
IncidentSource fits users who need broad, fast awareness of major incidents rather than deep single-agency monitoring. Typical use cases include:
- Situational awareness for people tracking events across multiple regions
- News and research — identifying major incidents as they develop
- Operational context — understanding escalation patterns (e.g., how many alarms a fire reached)
Because the feed is delayed by 15 minutes and based on public radio traffic, it is not a substitute for official emergency alerts or direct dispatch monitoring.
Access and platform details
The site references several entry points:
- Radiant Glow — the main platform interface
- APIs — for programmatic access to event data
- Squawster — a notification service ("Get Notified by Squawster")
- Sign In — for existing users
The page does not list pricing, subscription tiers, or whether access requires an account. Those details are not stated in the available material, so check the site directly before assuming free or open access.
Key limitation to keep in mind
The 15-minute delay and reliance on public radio traffic mean IncidentSource is an awareness tool, not a real-time emergency response system. For anything requiring immediate action, use official channels.