ZULUUTC / Z
—UTC+00
PHRYKTOR / LIVE WORKSPACE
Operations overview
Your radio, reports, and services at a glance.
Loading your operations dashboard…
Latest inbound
View inbox ↗Most recent message from each radio channel (private messages excluded).
Source health
FEEDSFeed timestamps reflect each source’s collection schedule.
Recent radio activity
Requests ↗Radio acceptance confirms local submission, not remote reception.
Latest Wire release
Archive ↗Docker at a glance
Explore fleet ↗Containers
CPU and memory are sampled every 30 seconds. Network and disk I/O are cumulative counters.
| Container / image | State | CPU | Memory | Network I/O | Started | Restarts |
|---|
Storage
WORKSTATIONPHRYKTOR / MESH EXPLORER
Loading your mesh…
Basemap unavailable. Node positions and the node list remain available.
Saved contacts from your radio
Glow: advertisement timestamp within 5 minutes
Glow: advertisement timestamp within 5 minutes
Map controls
Repeater Companion Room Sensor
All nodes come from contacts stored on this radio. Positions and timestamps are from advertisements, which may be old or relayed. The sampled RF packet view records reception at this radio; it does not provide statewide coverage or prove direct links.
Radio statistics
Dedicated USB observer health updates approximately every 30 seconds. The reporting radio operates separately. Counters are cumulative since the observer restarted.
Known radio contacts
Saved radio contacts, not a list of currently online devices. Routes describe the radio’s stored outgoing path; they do not prove direct reception.
| Contact | Type | Last advertisement | Stored route |
|---|
This legacy sample list may contain older observations. Use Packet explorer for the current 30-day archive. Private message contents are never displayed.
| Received | Packet type | RSSI | SNR | Bytes | Path |
|---|
People requesting reports
Request history
LATEST 150| Requester | Command | Time | Request | Response |
|---|
Source: messages dequeued from this radio by Phryktor’s local listener. No Discord, external mesh website or MQTT inbox feed is used. Public view excludes DMs.
Recent inbox
Open room messages →Latest 200 received events. Use Room messages for the full 30-day public archive.
Latest report by topic
Latest archived content for each topic. Original timestamps show how recently a report was recorded. Public snapshots refresh every minute.
WEATHER DESK / AURORA & FRONT RANGE
Forecast & radar
Plan with the forecast. Track precipitation with observed radar. Check official warnings for affected areas.
NOAA / NWS RADARLoading frame…
CURRENT · follows latest observation
Loading frame…
Loading timestamps…Observed radar · not a forecast
Radar reflectivityLightModerateHeavyIntenseExtreme
Observed precipitation echoes from NOAA/NWS MRMS. Coverage and reporting delays vary; a blank map does not prove clear weather. Current mode checks every minute and follows the latest actual NOAA observation. Replay keeps your chosen frame. High quality uses larger images with categorical colors preserved; it does not increase the source’s physical resolution. Longer loops use saved Colorado frames, retaining up to 24 hours and building history over time.
Aurora forecast outlook
Compare all five cities for the week →Rainfall, dry spells & flood context
Loading observations…
Use official flood outlooks and river forecasts, U.S. Drought Monitor Colorado, and burn-scar flood guidance alongside these observations.
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Loading local monitoring data…
Join #phryktor · scan the QR code
Join #phryktor
Connect your companion radio, then scan this code with the MeshCore app to add the room.
On the same phone? Tap Add room in MeshCore. If your camera does not open the app, use its channel QR scanner. You can also add the hashtag #phryktor manually.
This is a public hashtag room. Adding it does not change your radio settings or share your location.
Loading local monitoring data…
Loading local monitoring data…
OPERATIONS / FRONT RANGE
Connecting to published conditions…
Your local picture
Choose a city, ZIP area, or point on the map. Saved places and routes stay in this browser.
Loading local sources…
Map: warnings · road incidents · cameras · air monitors · fires · reported storm impacts · official emergency areas. Click any point to focus there.
Next 12 hours
Nearby conditions & incidents
Official emergency notices
Transit disruptions
Local incident timeline
Updates are grouped by source and incident ID. Collection disappearance and alert expiry do not confirm resolution.
Read public radio observations → Radio conversations remain separately attributed; they are not treated as official incident confirmations.
Weather & air
Radar ↗Roads & wildfire
Map layers ↗Active weather alerts · Colorado
What changed?
Timeline ↗Data freshness
Network history ↗Storage & backups
SITUATIONAL AWARENESS / COLORADO
Your situation map
Choose your area, turn individual layers on or off, and select a basemap. Your choices are saved in this browser.
Map symbols & interpretation
● Mesh node🔥 Fire⚡ Thunderstorm / lightning🌪️ Tornado❄️ Snow🌨️ Blizzard🧊 Ice🌊 Flood💨 Wind🌡️ Heat🥶 Cold🌫️ Air / visibility🏔️ Avalanche🚧 Roads⚠️ Other alert
Mesh positions are approximate; markers do not show coverage or guaranteed connectivity. Radar shows observed echoes. Smoke is model guidance, not a ground measurement. Fire markers show reported incident locations, not evacuation boundaries. Weather markers show warnings and urgent severe threats; watches and advisories remain in the full alert list. Icons label official alert areas, not exact tornado or lightning locations. No individual lightning-strike feed is connected. Alerts without polygons remain in the alert list.
Air quality monitors · Colorado
EPA AirNow preliminary AQI for ozone and particles, whichever is highest at each monitor. PM2.5 concentration is in µg/m³. Readings vary by location and can be revised.
How to read these charts
Samples are recorded every five minutes. Gaps mean no observation; they are not counted as healthy or failed. Packet counts are differences between continuous radio samples and are unknown after counter resets. Signal values describe the last received sample, not every node. Recently heard means reported within 15 minutes, not a guaranteed reachable node.
View recent samples
Get started with Phryktor
Phryktor combines local radio observations with attributed public sources. Use the master overview for your chosen city, monitoring for data freshness, and source links for official details.
Phryktor: reports and general commands. Wire: Wire reports. #weather: standalone concise NWS forecasts (wx or wx ZIP), weather full and point-specific alerts; separate from Phryktor reports. #bot: ping, test, sig, path, version, hello, joke, dadjoke, dice, roll, coin and magic8. Public, #emergency and other community rooms are observation-only. Direct messages support reports and bot utilities.
- Use your MeshCore radio or its companion app to join the Phryktor channel. Ask the operator for channel setup; channel keys are never published here.
- Send
helpin a supported channel, or sendhelpdirectly to Phryktor. - Try
wx 80018,roads I-70, orsitrep brief. Wait for the radio response before repeating a request.
This website only displays information. The commands below must be sent from your radio app.
Wire reports
The #wirereports channel supports wire, latest, since 3w, and wire YYYY-MM-DD. Requests are limited to one full report with a five-minute cooldown.
Map & status guide
- Recently heard
- An advertisement timestamp saved on your radio falls within the selected time window; it may have arrived through relays.
- Saved contact
- A radio contact with a stored advertisement; it may be old or offline.
- Cluster
- Nearby markers grouped together. Select a cluster to zoom in.
- RSSI / SNR
- Received signal strength / signal relative to noise. These describe reception at the monitoring radio.
- Stale / unavailable
- The last known value may be outdated, or no current observation exists.
Use official alerts and local instructions for emergency decisions. This dashboard is a supplemental community information service.
Supported command reference
Your viewing preferences
Saved only in this browser. No account and no changes to the radio or server.
Choose a viewing mode
Lightweight mobile view
Essential conditions, alerts, road summaries and network status. No map tiles, radar images, or large archives.
Open lightweight view ↗Wall display
Rotate Right now, Situation map, Radar, and Network history with your clock selection.
Situation report
Download a timestamped HTML briefing to save, share, or open and print to PDF. It includes the information currently available, with source ages.
PHRYKTOR / OPEN SOURCE INTELLIGENCE
OSINT desk
Official releases, world reporting, investigations, and public social posts. Follow each item to its original source.
Loading source feeds…
Official statements describe the issuing organization’s position; social posts and news claims are not independently verified by Phryktor. Region tags use headline keywords. Repeated links do not count as independent confirmation.
Free public feeds · checked every 10 minutes · original publication times preserved · source links open externally. Daily briefs are automatically selected headlines, not analyst assessments. No private messages or account credentials are published.
LOCAL RF / 1090 MHz
Air traffic
Aircraft heard by Phryktor’s own antenna, with live positions and recorded flight trails. This map can be used on its own; choose which aircraft types and colors to display.
Live aircraft
Aircraft icons & colors: customize by type above— Recent trail · 15 minFaded: last heard over 30 sec ago
AIRCRAFT DETAILS
Select an aircraft
Choose a marker or a row below to inspect its received flight data.
Aircraft in reception
| Aircraft | Type | Altitude | Speed | Heading | Last heard | Position |
|---|
FLIGHT HISTORY / 90 DAYS
Explore recorded traffic
Five-second samples, saved on the external drive. Choose a UTC hour to explore its flight trails. History starts when this receiver was connected.
Loading archive index…
Source: local RTL-SDR Blog V4, decoded with readsb. Aircraft models and military flags use a locally installed tar1090-db / Mictronics identity reference; it supplies no live flight positions. Categories and operator hints are identified in aircraft details. Signals are collected locally. Only aircraft signals received here appear; reception depends on antenna placement and radio coverage. This receiver listens on 1090 MHz, not 978 MHz UAT. Altitudes are transmitted barometric feet unless unavailable; tracks are degrees true and speed is knots. Gaps in trails indicate missing reception. This display is for situational awareness, not aviation navigation.
FRONT RANGE / SEVEN-DAY OUTLOOK
Seven-day outlook
Choose a city for morning, afternoon and evening/night forecasts. Icons show every supplied condition change, alongside the original forecast text.
Loading weekly forecasts…
NWS forecast for each city center. The current day may be partial. Rain/snow chance is the highest supplied period probability for that day. Morning is 6 AM–noon, afternoon noon–6 PM, and evening/night 6 PM–6 AM in Denver time. Hourly temperature ranges and condition changes use supplied NWS forecasts; missing hours are not filled in. Broader day/night fallback periods are labeled. Forecast values are not live measurements.
Official NWS forecast →Route readiness
Loading source data…
Reception compared with normal activity
Loading source data…
Recovery and verified backup timeline
Loading source data…
Cameras
Public COtrip cameras across Colorado, with saved favorites and available live streams.
Loading…
Mountains
Cameras along Colorado mountain corridors, with available live streams.
Loading…
Rivers & water
Streamflow, gauge heights, and observed changes.
Loading…
Smoke & air
Particle pollution trends, regional model guidance, and official smoke outlooks.
Loading…
Both radios & all services
Reporting and passive reception use separate radios. Confirmation means the collector recently checked the equipment; it does not prove coverage everywhere.
All Docker containers
Every collector and data source
Collection health and source freshness are different. A working collector can receive old data or encounter an unavailable upstream service.
Independent recovery checks
Failure and restart history
Recorded from installation onward. Repair completed means the command finished; verified means the health check passed. Root reboot count appears above.
Source checks and original observations
Official intelligence briefing
Observed airport weather, regional earthquakes, and space-weather context. Each item keeps its source timestamp and link.
Road conditions & traffic incidents
COtrip operator road reports, route weather guidance, closures and incidents. Live traffic speeds and congestion estimates are not supplied by the connected feeds.
Reported traffic incidents
Local intelligence desk
Incident briefings, cameras, source updates, assistance and reviewed community observations in one place.
Priority incidents
Select an incident to see its briefing.
Follow your areas
Updates cover your selected area, saved places and followed road routes. Browser notifications work while this site is open; they do not provide closed-browser push or replace official alert subscriptions.
Outages, shelters & official help
Official finders remain authoritative. Operator-entered entries include a source, observation time and expiry; they do not imply complete coverage.
Community observations
Approved reports are reviewed for publication, not independently verified. Send neighborhood-level observations; avoid names, exact home addresses and private information. This form does not contact emergency services.
Recorded incident timelines
Each timeline follows versions of the same agency/source record. Nearby reports are context, not automatically the same incident. A record disappearing or expiring does not prove resolution.
Source freshness
Current means the collector recently succeeded; it does not guarantee every measurement is recent or complete. Original observation times remain visible. Delayed or unavailable data is not an all-clear.
Camera wall
Pin cameras for a 2, 4, 9 or 16 view display. Select which pinned cameras run live video. Preferences and clock settings stay in this browser. Live feeds use this viewing device’s bandwidth; some cameras offer snapshots only.
Layout and fullscreen clocks
Official COtrip imagery · streams have independent delays; shared refresh does not synchronize source capture times · snapshot timestamps are shown when supplied. Fullscreen applies to this display; Escape exits.
Live mesh rooms
Public messages actually heard or accepted by your local radios. This view reads the archive; it does not send messages or expose private conversations.
Open #emergency · Open #cm-reach · MECP decoder & code reference
MECP messages are translated below their original text. Reports are unverified; tests and drills are labeled. No emergency acknowledgements are sent.
Colorado Mesh channel guide · all eight listed topics available
Checked against Colorado Mesh’s published common-channel directory on October 4, 2026. These channels are already included in Phryktor’s monitored room list; a room may have no locally received messages.
- #testing — Device and connection tests
- #emergency — Emergency and urgent community messages
- #weather — Weather discussion and reports
- #sports — Sports discussion
- #bot — Bot commands and replies
- #jokes — Jokes and casual humor
- #hamradio — Amateur radio discussion
- #cm-reach — Reach-check test session codes
Official community channel guide · Public is the general channel; Phryktor and Wire are additional existing local rooms.
What do #cm-reach codes mean? · Read a code
MHC means Mesh Health Check. A message such as MHC- followed by six hexadecimal digits identifies a reach-test session. People send it to find out which participating receivers hear their message. The digits are random; they do not translate into an emergency, location, route or signal strength.
Below each recorded code, this reader explains its purpose and shows matching local chat entries. Broader results require the test service’s actual observer receipts; they are not embedded in the code. This reader uses only Phryktor’s locally collected public messages.
Protocol / reach-check project documentation · Official Colorado Mesh Range Check · opens separately. Phryktor does not load its API, observer feed or session results.
Loading locally heard messages…
Room
New messages appear at the bottom · source reception time shown.
Camera timelapses
Actual recorded snapshots, starting when recording is enabled. Up to 48 hours within a shared 256 MiB limit. Source gaps remain gaps; past video cannot be reconstructed.
Custom route watch
Follow any road in the statewide camera catalog. Narrow it to a corridor using map points, then see nearby cameras, reported conditions, weather and dated hazard context. Drawn corridors are planning references, not turn-by-turn directions or verified open roads.
TV rotation
Cycle between the situation map, pinned camera wall, incident desk, tagged mesh room and route watch. Configure those views first; saved preferences are used. Start rotation is a user action, and Escape stops it.
Mountain hazard assessments
Dated USGS post-fire debris-flow assessments under specified rainfall scenarios. These are model assessments—not current warnings, active debris flows, evacuation areas or assurances of safe travel.
USGS assessment locations · Basin colors: green = low, amber = moderate, red = high model classification. Classification and rainfall scenario come from the source. No assessed area does not mean no hazard.
Open official USGS assessment dashboard →Incident camera recordings
Actual snapshots preserved near new or changed official weather, fire and closure notices. Notices may describe scheduled work; nearby images do not establish that an incident is visible. Recording starts when a notice is detected, with existing pre-trigger frames only when already recorded.
Observed coverage & data gaps
Coarse cells show collected route activity and available source records. This is not an RF range prediction or proof of message delivery. Receiver and Phryktor positions remain hidden. Gray cells indicate no collected record—not no signal, no station or safe conditions.
Cell sizes are 0.25°; counts use approximate public positions. Mesh counts associate received route metadata with uniquely matched advertised nodes. No circles or connecting paths are inferred around receivers.
Briefing PDF
Download a PDF with your configured situation map, chosen collected notices, actual camera snapshots and their source timestamps. The PDF is generated in this browser. Visible planning notes can appear in the map image.
Configure the situation map and pin cameras first, or choose cameras below. Select up to 10 notices and 6 snapshots. Historical map replay and current camera/report sections are labeled separately.
Collected notices in your Intel desk area
Camera snapshots
Missing images, map layers or source data are listed in the PDF; no replacements are fabricated. Generation may briefly show the situation map. Map tiles retain provider attribution.
Colorado news reader
Local headlines and official updates collected by FreshRSS. Reporting is not independently verified; open the publisher for the complete story.
Choose your feeds · saved on this browser
Select sources below. National and world news are optional. Your selections and bookmarks stay on this browser; no account is needed.
Loading collected headlines…
Feeds checked every 15 minutes; this reader refreshes every 5 minutes. Empty official-alert feeds can mean no active notices. Publication times come from each publisher. Powered by FreshRSS · open source
START HERE
Your Colorado intelligence dashboard
Start with the map, then choose a page for more detail. Use Reading settings to change the theme, text size and map labels. This guide includes real screenshots and steps you can follow.
A few things to know
Check the source and its timestamp before relying on a report. A blank view means no collected data, not an all-clear. Public radio messages are read only; the map shows observations heard by our receivers, rather than confirmed delivery at every node.
Your camera favorites, layout and display settings stay in this browser. Clearing browser storage resets them; another phone or computer has its own choices. Private administration, passwords, radio keys and receiver coordinates are excluded from the public site.
No features match. Try a page name or clear the search.
START SMALL · HELP THE COMMUNITY
Grow the Phryktor mesh
A MeshCore radio lets your phone exchange short messages over LoRa without mobile data. Start with one companion radio. Add a repeater or an observer when you are ready.
Join #phryktor
Connect your companion radio, then scan this code with the MeshCore app to add the room.
On the same phone? Tap Add room in MeshCore. If your camera does not open the app, use its channel QR scanner. You can also add the hashtag #phryktor manually.
This is a public hashtag room. Adding it does not change your radio settings or share your location.
Choose your first radio
Budget: Heltec WiFi LoRa 32 V3
Best if you are comfortable assembling a board, antenna, battery and case. Buy the US-compatible 915 MHz version and the correct antenna. A board alone is not a weatherproof outdoor node.
Manufacturer specification & buying optionsReady handheld: ThinkNode M1
An enclosed nRF52840 handheld with battery and antenna. Confirm the exact hardware is supported in the MeshCore flasher. Some units arrive with Meshtastic firmware; they need matching MeshCore companion firmware to join this mesh.
Manufacturer instructionsSolar: Seeed MeshCore starter kit
A ready companion plus a solar repeater is a simpler outdoor starting point. Check the regional radio variant, mounting, sun exposure and local network settings before ordering.
Manufacturer kit · Solar setup guideThe minimum to get started
- Get a supported companion radio, matching antenna, USB data cable and power. A Bluetooth companion and a phone running MeshCore are enough to begin.
- Attach the antenna before powering the radio. Choose the firmware for your exact board and Companion Bluetooth role in the official flasher. Follow the board’s flashing instructions.
- Install MeshCore and pair your radio. Set a short name. Check the local Colorado community’s current frequency, bandwidth, spreading factor and coding rate; every radio must match. Do not guess these values.
- Choose your privacy settings. Sharing an advert can share your selected name and location. Turn location advertising off if you want to keep your home or receiver private.
- Join the public room
#phryktor. Use the app’s hashtag channel option. The network page shows messages actually heard by this system; silence does not prove nobody received your message. - Send one short introduction and let the network settle. Avoid repeated flood adverts and rapid messages. Receive first; use a test room for testing.
What each role does
Companion: connects your phone to the radio. Repeater: forwards compatible mesh traffic; good height, power and antenna placement matter more than frequent advertisements. Observer: listens and records packets for a map; it is not a repeater or a guarantee of delivery.
Ways to support the mesh
Help a neighbor set up a companion, place a well-powered repeater where it improves coverage, keep batteries and solar panels maintained, and contribute a receive-only observer. Obtain permission for mounting and do not publish other people’s private conversations or precise home locations.
PhryktorCore for Android
The PhryktorCore APK has not been supplied yet. The official MeshCore app is available above.
Contribute an observer
Use a spare supported LoRa radio and an always-on computer or Pi. Your observer listens locally and sends only packet metadata to PhryktorNET. Uploads are authenticated, checked, and held for the owner’s review by default.
- Start with a supported board such as Heltec V3 and an antenna matching the local band. Connect it to your Pi or computer by a USB data cable.
- Follow the detailed observer guide below. Use the supported receiver/logger configuration and match the local radio settings. Give the observer a separate identity; keep precise receiver coordinates private.
- Ask the owner to add your observer in the private admin page. You will receive an observer ID and a secret upload key. Keep the key private.
- Export the documented version-1 JSON metadata: observation ID, receive time, packet type, signal and packet path. Raw payloads, chat text, private messages and secrets are rejected.
- Choose the JSON file below and enter your observer ID/key. The browser signs this batch; the key stays in memory and is cleared after submission.
- The owner reviews the pending batch before sharing it. After review, the owner can enable automatic uploads. Use the documented uploader for continuous operation.
Maximum 128 KiB; 1–250 recent observations. Credentials are never saved in browser storage.