incidentsource.com

IncidentSource covers major public safety events drawn from radio traffic, organized by event type, responding agency, and location. Based on its public event feed, coverage centers on U.S. fire, EMS, and rescue activity — including motor vehicle accidents (MVAs), shootings, structure fires, and technical rescues — across multiple states and counties. The platform presents these as a "Recent Major Events" list with date/time, event type, context, and location, updated with a stated 15-minute delay.

Event types covered

The event feed groups incidents into recognizable major-event categories rather than raw call types. From the listed events, the main categories include:

• MVA / Extrication — motor vehicle accidents requiring extrication
• MVA / Major Roadway Shutdown — accidents significant enough to close roads
• Shooting — shooting incidents
• Structure Fire — with sub-levels such as Smoke Showing, Working Fire, Defensive Operations, and Multiple Alarm
• Technical Rescue — specialized rescue operations

This suggests the platform is oriented toward incidents that generate sustained radio activity and clear escalation signals, not routine calls.

Locations and agencies

Coverage is organized by agency and geography. The feed shows incidents attributed to specific fire/EMS/rescue agencies across several states, for example:

So coverage spans multiple U.S. states and counties, with agencies typically being municipal or county fire, EMS, and rescue departments.

How the event list is structured

Each entry in "Recent Major Events" includes:

• Date / Time (in UTC)
• Major Event Type (e.g., Shooting, Structure Fire – Working Fire)
• Context — the responding agency and jurisdiction
• Location — street address or block, city, and state
• View / Play — access to the associated audio

The list displays the last 20 major events with a 15-minute delay. The site also reports rolling 24-hour counts (for example, signals, events, and major events) as a measure of activity volume.

What this means for coverage expectations

If you need awareness of active fire/EMS incidents in the covered jurisdictions, IncidentSource surfaces major events by type and location with linked audio. Two practical limits follow from the evidence:

• Coverage is agency- and feed-dependent — an area appears only if its radio traffic is included.
• The feed is delayed by 15 minutes, so it is suited to situational awareness rather than real-time dispatch.

For a specific area, check whether its fire/EMS agency appears in the event context column; that is the clearest indicator of whether that location is currently covered.

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.

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.

IncidentSource is accessible through three separate entry points, each serving a different need: the Radiant Glow platform for browsing AI-processed event intelligence, a Sign In option for returning users, and Squawster notifications for push-style alerts. An APIs link is also listed on the site for programmatic access. Which one you use depends on whether you want to browse events, receive alerts, or pull data into your own system.

The Three Access Paths

The homepage presents these options directly, and they are not interchangeable — each leads to a different capability.

Opening Radiant Glow

Radiant Glow is the platform itself — the interface where IncidentSource turns raw public safety radio traffic into structured event awareness. Selecting Open Radiant Glow is the path for viewing the live data rather than just receiving alerts.

Once inside, the platform organizes audio, event context, location, and escalation activity. The homepage preview of what this looks like shows a Recent Major Events table with columns for Date/Time, Major Event Type, Context, Location, and a View/Play action.

Signing In

The Sign In option is for existing users. The site does not state whether browsing Radiant Glow requires an account or whether sign-in unlocks additional features — if you need certainty on that, treat sign-in as the safe route for returning users and check the platform directly for guest access.

Getting Notified by Squawster

Get Notified by Squawster is the alert signup path. The homepage pairs it with the line "Squawster Incident Source alerts + Broadcastify audio in your pocket," which indicates alerts are delivered alongside Broadcastify audio. Choose this route if you want to be pushed major-event awareness instead of checking a dashboard.

APIs

The site lists APIs as a distinct option, described under "What we cover." This is the route for programmatic access — pulling event data into your own application or workflow rather than viewing it in the browser. The homepage does not publish endpoint details, authentication methods, or rate limits, so those would need to be confirmed after following the link.

What You'll See Once Inside

Understanding the data model helps you decide which access path fits. IncidentSource reports three live counters, all labeled "Last 24 hours":

• Signals: 170,447
• Events: 27,997
• Major Events: 768

The Recent Major Events view shows the last 20 major events with a stated 15 minute delay. Each row includes:

• Date / Time (UTC)
• Major Event Type — for example, MVA Extrication, Shooting, Structure Fire – Working Fire, Structure Fire – Multiple Alarm, Technical Rescue, MVA Major Roadway Shutdown
• Context — the responding agency, such as NC-Charlotte / Mecklenburg County Fire/EMS or AZ-Phoenix Fire
• Location — street address or block-level location
• View / Play — access to the underlying audio

This structure tells you what "event intelligence" means in practice: a classified event type, the agency context, a location, and playable source audio.

Choosing the Right Path

• If you want to browse and listen: Open Radiant Glow.
• If you already have an account: Sign In.
• If you want alerts without checking a dashboard: Get Notified by Squawster.
• If you're building something: Use the APIs link.

Practical Notes Before You Start

• Expect a 15 minute delay on the major events feed shown on the homepage. If your use case requires real-time awareness, account for that lag.
• Times are in UTC. Convert to your local timezone before acting on a timestamp.
• Locations can be approximate. Several entries show block-level addresses (for example, "12900 block Mysteria Dr") or intersections rather than exact addresses.
• The counters are rolling 24-hour figures, so they change continuously and are not cumulative totals.
• Pricing and account requirements are not stated on the homepage. Do not assume the platform or alerts are free — confirm terms after following the relevant link.

IncidentSource event data is near-real-time, not instant. The platform's Recent Major Events list is labeled with a 15 minute delay, and every event carries a UTC timestamp so you can judge exactly how fresh a given entry is. If your use case requires second-by-second live monitoring, this is a delayed feed; if you need fast awareness of major incidents across many agencies, a 15-minute lag is usually acceptable.

What the site shows about data freshness

The homepage presents three rolling 24-hour counters:

These are aggregate counts over a trailing 24-hour period, which tells you the system is continuously ingesting and classifying radio traffic rather than publishing in daily batches.

The Recent Major Events table is explicitly described as "Last 20 major events · 15 minute delay." That delay figure is the clearest statement of currency on the page, and it applies to the major-event feed.

How to read the timestamps

Each row in the major events list includes a date and time in UTC, for example:

• 2026-10-14 02:22 UTC — MVA Extrication, NC-Charlotte / Mecklenburg County Fire/EMS
• 2026-10-14 02:12 UTC — Shooting, AZ-Phoenix Fire
• 2026-10-14 02:04 UTC — Structure Fire - Working Fire, CA-Verdugo Fire Communications Authority

Two things follow from this:

1. UTC only. You need to convert to your local time zone to compare against your own clock. A 02:22 UTC event is the previous evening in US Pacific time.
2. Timestamps are per event. You can measure the gap between the newest row and the current time to sanity-check the stated delay on any given visit.

What "near-real-time" means in practice

The combination of a 15-minute delay, continuous 24-hour counters, and per-event UTC timestamps points to a system built for rapid awareness rather than live dispatch monitoring. Practical implications:

• Good fit: tracking major incident patterns across regions, catching up on what happened in the last hour, monitoring multiple agencies you can't listen to simultaneously.
• Poor fit: anything requiring you to know about an incident the moment it is dispatched, or to act on a scene in progress.

How to verify currency yourself

1. Open the Recent Major Events list.
2. Note the newest timestamp and convert it to your local time.
3. Compare it against your current local time.
4. The difference should be roughly consistent with the stated 15-minute delay; a much larger gap suggests the feed is lagging or the list has not refreshed.

Common points of confusion

• The 24-hour counters are not live gauges. They are rolling totals, so they will always look "current" even if you are reading a cached page.
• The delay applies to the major events list. The page states the 15-minute figure specifically for that table; it does not claim the same figure for every signal or event in the system.
• UTC timestamps can look "wrong." An event dated later than your local date is normal if you are west of UTC.

IncidentSource is an AI-powered event intelligence platform that converts public safety radio communications into a structured, searchable feed of major events. It listens to radio traffic, uses AI to detect and classify incidents, extracts location and context, and presents everything in a feed with audio playback. If you want situational awareness of fire, EMS, and rescue activity across many jurisdictions without monitoring scanners yourself, this is the mechanism it uses.

The pipeline: from audio to structured event

IncidentSource describes its core function as turning "raw public safety communications into structured major-event awareness." That breaks into four stages.

1. Ingesting radio traffic

The platform monitors public safety radio communications. Its site references Broadcastify audio, and the product framing is "Broadcastify audio in your pocket" — meaning the underlying audio streams come from public safety radio feeds rather than from IncidentSource-operated receivers.

2. AI detection and classification

An AI layer listens to that audio and decides what constitutes a major event. Rather than surfacing every transmission, it filters for incidents worth flagging and assigns a type. In the sample feed, the event types include:

• MVA Extrication
• Shooting
• Structure Fire – Working Fire
• Structure Fire – Multiple Alarm
• Structure Fire – Smoke Showing
• Structure Fire – Defensive Operations
• MVA Major Roadway Shutdown
• Technical Rescue

3. Extracting context and location

For each detected event, the system pulls out the agency and a location string. The feed pairs a jurisdiction with an address or block:

Locations range from precise blocks ("1700 block S 281st Pl, Federal Way, WA") to intersections ("Northwest 53rd Street and Clackmore Road") to "Unknown" when the audio doesn't yield one.

4. Presenting a structured feed

Detected events land in a feed called Recent Major Events, showing the last 20 major events with a 15-minute delay. Each row carries a date/time in UTC, the event type, the agency context, the location, and a View ▶ control that plays the associated audio.

What the platform surfaces at a glance

The homepage also exposes rolling counters, which tell you the scale of what's being processed:

• Signals: 170,447 in the last 24 hours
• Events: 27,997 in the last 24 hours
• Major Events: 768 in the last 24 hours

The gap between "Events" and "Major Events" is the key design point: the AI processes a large volume of activity but escalates only a small fraction to the major-event feed. That escalation step is what the product calls surfacing "what matters quickly."

How to use it

1. Open Radiant Glow, the platform interface referenced on the site.
2. Browse Recent Major Events for the last 20 flagged incidents.
3. Scan the event type, agency, and location columns to find what's relevant to you.
4. Select View ▶ on a row to play the underlying radio audio for that event.
5. Use Sign In for account access, or Get Notified by Squawster to receive alerts. The site also lists Where we cover, What we cover, and APIs as entry points for coverage details and programmatic access.

What to keep in mind

• There is a 15-minute delay on the major-event feed, so this is awareness, not real-time dispatch.
• Coverage is jurisdiction-dependent. The sample feed spans NC, MD, AZ, CA, MO, WA, TX, OH, AL, OK, IL, MA, and LA, but you should check the "Where we cover" section for your area.
• Locations can be incomplete. Some entries show "Unknown," reflecting limits of what the audio contained.
• "Major event" is an AI judgment, not an official classification — treat the feed as a filtered signal, not a verified record.

The practical takeaway: IncidentSource is a filter, not a scanner. It does the listening and triage so you get a short, structured list of significant incidents with the audio one click away.