Click here for information about the native app.

Update: 5/20/26

• I’m still making adjustments to the new SDR software configuration. Overall, I’ve been pleased with how it performs. I did have to rethink the audio post-processing to get the levels right, and I’m still not completely settled on how I want to handle the actual decode/capture/commit to file process.
• I ran into an issue where audio was being delivered out of order post-capture following an update Monday evening, which continued into a complete fiber optic outage for about the first six hours of Tuesday morning. Both issues were resolved.
• The new configuration currently monitors, decodes, and records six P25 sites on the AWIN system, and has allowed me to add a number of new talkgroups to the system.
• I changed the default Incident Feed display (in the Alerts & Notifications menu) to filter out any detected incident or statistical anomaly notification that has been “resolved” by the system. 
• Speaking of detected incidents and anomalies, I’ve been compiling detection data and will tighten up the detection logic soon. Some of the detected “incidents” make absolutely no sense whatsoever, mostly because I’m the one writing the code.
• Added a live, continuously updating status display for the AWIN system (in the main menu). I’m pretty happy with it, too. 
• I still have to come up with a help section.
• The CAP+ system in St. Francis County is still driving me crazy.
• The Evening Times posted something about EAN on their Facebook page a couple of weeks ago, which I appreciate greatly. I’m not on social media but I could tell something was up because of a sudden increase in traffic to the site. That’s usually how people find out about EAN – word of mouth.
• I feel like this is a good place to point out that I don’t do this for money. I don’t have anything for sale. You can’t pay for any sort of upgraded access. I don’t advertise on this site. 
• If you know someone who may find this site interesting or beneficial, please share it with them!
• Feel free to contact me (admin@eastarknet.com) if I can be of assistance.

Update: 5/9/26

• I moved the West Memphis AWIN site from my hardware radios to my SDR machine early this morning. This should mean virtually zero missed calls from West Memphis, Marion, and the rest of Crittenden County.
• I’m using different software for all the P25 sites now. If things sound different than what you’re used to hearing on AWIN, that’s why. I will, of course, have to do some fine-tuning but the new software is holding its own so far. We’ll see how it does when atmospheric conditions get weird.
• Tone-outs now have an audio clip posted with the notification in the incident notification feed. 
• Added tone detection and an option for notifications for the smaller fire departments in Crittenden County. Go to “Alerts & Notifications” in the main menu, and then go to the “Notification Settings” tab to enable them.
• Made some minor aesthetic improvements.
• I’m still working with the incident detection and statistical anomaly notifications. If you have these notifications enabled, expect random weirdness.
• Help section will be in the works soon. 
• Drop me a line (admin@eastarknet.com) if you have any questions or feedback.

Update: 4/30/26

• I’ve more or less gotten the initial version of the new statistical system in place. Select “Statistics” from the main menu. It’s fairly basic but as I build more of a dataset, it’ll become more comprehensive. I’ve added an option to alert you when traffic patterns for a given talkgroup exceed certain parameters. It basically asks, “is this amount of traffic normal for this talkgroup for this timeframe on this day of the week?” If not, it sends a notification.
• I’ve also been tinkering with automated incident detection. It uses the same dataset as the statistics, but only the most recent data snapshot to maintain a real-time overall “awareness” of how the current radio traffic patterns compare not only to themselves historically, but also to each other in the context of the overall current picture. I have a framework in place with the most basic version of the logic in place, and I’m currently expanding on that to make it smarter and less prone to false positives. Right now, when it flags something it has determined to be a possible incident, it sends a notification. You may also choose to receive these notifications.
• The settings for receiving notifications to your device(s) are located under “Incident Notifications” in the main menu. Select the “Notification Settings” tab. If you scroll to the bottom, you’ll see the new options.
  Please note that I will be making a considerable number of changes to the logic that drives the new notifications as I further develop and refine them and you may experience wild results, hence the “experimental” labels.
• As always, if you know someone who might find this site useful, please share it with them. 
• If you have any questions or comments, or if I can help you with an issue, email me at admin@eastarknet.com.

Update: 4/18/26

• The pursuit of the stolen Marion Police unit on Monday the 6th revealed that neither my server hardware nor my software configuration could handle a sudden, heavy demand.  As a result, I have significantly upgraded the physical server and implemented new software packages and configurations. These changes should result in faster load times, decreased latency, and an overall improved experience; and the server should never become overwhelmed and grind to a halt again. If you encounter any issues or errors, please email me (admin@eastarknet.com).
• I did some work on my little weather widget to make it a little less ugly. The data it displays comes from my on-site weather station.
• I was in the process of doing a complete redesign of the statistics reporting system when I stopped to deal with the server upgrades. Now that the upgrades are complete, I can get back to work on the statistics. I do a lot of my work-in-progress development/testing on this page, if you want a preview.
• There are a few more cosmetic and performance tweaks to make.
• I still have actual “radio stuff” to do, I just want to get the server/website completed. I’ve got to figure out a way to get the West Memphis AWIN site over to my SDR machine. Every agency in Crittenden County is being handled by two hardware radios right now. They are fantastic radios (SDS200, if you’re interested) and are doing a stellar job with the not-always-ideal signal I’m getting on my Yagi antenna from about 35 miles away. Nevertheless, they are only capable of decoding one talkgroup at a time and that means missed calls when the system gets busy. I also have the issue of the signal from one of the St. Francis County CAP+ system’s three transmitters being significantly weaker than the other two. This has been driving me crazy since February.

Update: 3/31/26

• Severe weather season is here. If you think someone would benefit from the information available here, please let them know. I’m not on social media. It’s too social for my tastes. Google searches and word of mouth are the two ways people find out about EAN.
• I’ve made some cosmetic changes to the site in an attempt to make it look more uniform and (hopefully) easier to navigate. I’ll eventually unify everything so it looks and acts like it all belongs together. I’m a “function over form” kind of guy but I do understand how important aesthetics are to the overall user experience. I’m still working on it, just like everything else around here.
• The live activity map is new. It was my first foray into incorporating GeoJSON into a coding project and I’m pretty happy with it. It’s essentially an extension of the Live Talkgroup Activity grid display that shows a “where” with the “who.”
• I moved the 10-Codes into a modal window that opens on top of everything else, instead of taking you to a completely different page.
• I reworked the entire incident/fire tone-out notification system.  It’s all in a modal window now, as well. The incident feed is back, after a long hiatus. Controls for push notifications have been moved to a tab in the Incident Notifications menu. Notifications are delivered quicker now. Tapping a push notification on your device now does something useful, instead of just taking you to the site.
• If you see/experience anything weird with the site or have any questions, please email me (admin@eastarknet.com).
• I haven’t done much in the way of actual “radio stuff” lately because I’ve spent so much time working on the website. I did a limited amount of testing with a different SDR setup and was able to get it configured enough to confirm it does work, but I have done zero testing and haven’t used in an actual “live” setting. I still need to figure out the St. Francis County CAP+ site once and for all. I also need to see if I can do better with the DMR systems in Wynne. I’m pretty sure I’m overloading the front end on both of these and need to add some attenuation.

Update: 3/13/26

• Someone emailed me with a question about connecting to my server with the Rdio Scanner mobile app. I added a screenshot to the section at the bottom of the page that might help. For listening on any device other than a computer, the app is the way to go.
• The Live Talkgroup Activity grid display (on the main page of the site) is project that started out as an idea for a basic visual indicator of traffic across all the systems I monitor. After about a week of working on it a few hours a day, it turned into what you see now. I’m pretty happy with it. I absolutely did not design it with mobile devices in mind as the primary display. It works on phones but I designed it to run in a desktop browser. It is meant for dispatch/communications centers, emergency operations centers, and radio/data nerds (like me). It’s all custom JS/PHP/CSS code. The information is generated from data that already exists in my database. Things like the Talkgroup Traffic Spike indication are dependent on logic that is somewhat rudimentary (because I developed it) and will be refined over time. This, like most of my projects, will never really be “complete.”
• I added a few things to the listener map.
• The issues with the St. Francis County CAP+ system persist and continue to affect FCPD, FCFD, and EMSA. Anything on 155.175 is hit or miss. The other two frequencies that make up this system are fine. This is the Frankenstein’s Monster of radio systems. The difference on the waterfall display on my SDR machine for 155.175 versus 158.7975 is night and day. No amount of signal processing is going to be able to fix it, this is purely an RF issue at this point. I’ll try to do some testing soon to see what, if anything, I need to do to improve the RF situation. Probably something that relates to messing with an antenna/coax, which is one of my least favorite activities.
• I now do some audio processing that helps maintain more consistent audio by raising low levels and lowering high levels across all systems.
• I’m considering a different architecture for the way I’m handling everything on the SDR machine, which would mean new software and a new configuration (and the headaches and growing pains that come with a new way of doing things), but may also mean an overall better system that’s less prone to weirdness and will scale easier.
• I’m not on social media (every platform is a dumpster fire). If you find this website useful, tell someone else about it!
• Drop me a line at admin@eastarknet.com if there’s anything I can do for you.