# NOAA Space Weather Alert Monitor

Export official NOAA space-weather bulletins for satellite, radio and grid research. Filter product IDs or message text, preserve source wording and compare saved bulletin changes.

Canonical product page: https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/

## Example input

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

## Ready-to-use input recipes

These are downloadable JSON configurations. They do not start runs or represent public Apify saved tasks. Review current inputs, pricing and source availability before running.

[Default input](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/input.json) · [Input schema](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/input-schema.json) · [Saved output capture](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/evidence.json)

### Read three recent NOAA space-weather bulletins

Retrieve three recent official bulletins with unchanged message text, issue times, product IDs and source links.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/recipe-1.json) · [Example evidence](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/recipe-1.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 3 saved rows. This does not establish current availability.

### Find radio-related NOAA bulletins

Filter the retained official feed for the literal word radio. This does not independently rank severity or current validity.

```json
{
  "messageContains": "radio",
  "maxResults": 3,
  "comparePrevious": false
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/recipe-2.json) · [Example evidence](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/recipe-2.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 3 saved rows. This does not establish current availability.

### Compare K04W geomagnetic bulletins

Track the latest K04W source bulletins. The first run establishes a baseline; issue timestamps remain distinct from observation time.

```json
{
  "productIds": [
    "K04W"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "geomagnetic-bulletins"
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/recipe-3.json) · [Example evidence](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/recipe-3.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 3 saved rows. This does not establish current availability.

[All example inputs](https://mayd-it.com/data-tools/actors/noaa-space-weather-alert-monitor/examples/index.json)
## Choose this tool

Satellite and communications analysts, GNSS-dependent operations researchers, grid-risk reporting teams and automation builders who need traceable official bulletins.

Useful output columns: `title`, `productId`, `messageCode`, `serialNumber`, `issuedAt`, `observationAgeHours`, `sourceFreshness`, `comparisonStatus`, `sourceUrl`.

## Practical workflow

Run the default to review three recent bulletins and their issue timestamps. Filter by an exact source product ID or a literal term such as radio or geomagnetic. Join the full official bulletin to your own incident workflow; use comparisons to spot source text changes.

## Check the fit

The retained feed is not a complete historical archive and its window can change. A bulletin in the feed is not necessarily still active; validity, extensions and cancellations remain in the original message. No independent hazard ranking, predicted business loss or operating recommendation is generated. Official sources and established emergency channels take precedence for safety decisions.

## Real output sample

One selected row from a 2026-11-21 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: pxhYfztsQq0anN2Zv. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "noaa-swpc:K04W:2026-11-19T01:18:16.670Z",
  "title": "EXTENDED WARNING: Geomagnetic K-index of 4 expected",
  "productId": "K04W",
  "messageCode": "WARK04",
  "serialNumber": "5457",
  "issuedAt": "2026-11-19T01:18:16.670Z",
  "observationAgeHours": 67.06,
  "sourceFreshness": "issued_within_72_hours",
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://services.swpc.noaa.gov/products/alerts.json",
  "url": "https://services.swpc.noaa.gov/products/alerts.json",
  "observedAt": "2026-11-21T20:21:47.727Z"
}
```




## Full guide

![NOAA Space Weather Alert Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/noaa-space-weather-alert-monitor-7170b60c7459.png)

# NOAA Space Weather Alert Monitor

<!-- MAYDIT-BANNER -->

Export official NOAA space-weather bulletins for satellite, radio and grid research. Filter product IDs or message text, preserve source wording and compare saved bulletin changes.

**Built for:** Satellite and communications analysts, GNSS-dependent operations researchers, grid-risk reporting teams and automation builders who need traceable official bulletins.

## Start with three real observations

Run the default input to collect a small, traceable source window. No source API key, login, proxy or paid source subscription is required. The Actor exports actual public source records and reports source failures without creating paid diagnostic rows.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

Open the dataset for JSON/CSV, **SUMMARY** for coverage and **RUN_REPORT** for a readable result. A successful bounded run does not prove the full source universe was collected.

## Three practical recipes

### Read three recent NOAA space-weather bulletins

Retrieve three recent official bulletins with unchanged message text, issue times, product IDs and source links.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

### Find radio-related NOAA bulletins

Filter the retained official feed for the literal word radio. This does not independently rank severity or current validity.

```json
{
  "messageContains": "radio",
  "maxResults": 3,
  "comparePrevious": false
}
```

### Compare K04W geomagnetic bulletins

Track the latest K04W source bulletins. The first run establishes a baseline; issue timestamps remain distinct from observation time.

```json
{
  "productIds": [
    "K04W"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "geomagnetic-bulletins"
}
```

## Understand the result

Each row preserves the official `message` text, `productId`, `messageCode`, source `serialNumber` when provided and UTC `issuedAt`. `title` is the first nonempty source line after Issue Time. No independent severity, impact probability or hazard score is invented.

`observationAgeHours` is age at collection; `sourceFreshness` distinguishes issue times within or beyond 72 hours, a transparent display threshold rather than a NOAA service guarantee. `activeStatus` remains `not_inferred`: an old warning, extension or cancellation can remain in the feed. Read the complete message for valid-from/until text and consult the official product page and NOAA scale explanations. This feed is not a historical archive.

`productIds` filters exact official IDs. `messageContains` performs case-insensitive literal text matching. `maxAgeHours:0` turns off age filtering; another value applies it to the source issue timestamp. `maxResults` selects the latest matching bulletins, ordered by issue time. SUMMARY reports the newest/oldest feed issue time and matching count. A valid empty filter result is not a source error.

| Output | Purpose |
| --- | --- |
| `recordId`, `sourceUrl` | Stable source identity and a link to the official data. |
| `observedAt` | Retrieval time, separate from source issuance/publication. |
| `comparisonStatus`, `changedFields`, `previous` | New, changed or unchanged source fields on requested comparisons. |
| `SUMMARY` | Selected coverage, source errors, limits and history status. |

## Changes you can trust

Run the same selection and `snapshotName` sequentially with `comparePrevious:true`. The first complete run establishes a baseline in the named `noaa-space-weather-alert-monitor-history` store. `onlyChanges:true` also enables comparison and can correctly emit zero rows on unchanged repeats. Observation time and age alone never create changed records.

History advances only after confirmed output from a complete selected window. Source errors, interrupted output, exhausted charge allowance, deadlines and concurrent history writers prevent baseline replacement. Prior records are preserved; absent source records never imply removals, cancellations or a resolved operational condition. This Actor does not schedule itself or send alerts automatically; use your own saved task, schedule or integration.

## Use with other Mayd It Actors

- [Vendor Incident Feed Monitor](https://apify.com/maydit/vendor-incident-feed-monitor): Correlate official space-weather bulletins with your vendors’ published incidents without inferring causation.
- [GDACS Disaster Alert Monitor](https://apify.com/maydit/gdacs-disaster-alert-monitor): Keep terrestrial disaster alerts and space-weather bulletins in separate, source-labelled operational feeds.

Keep source identities and timestamps when joining datasets. Correlation is a research observation, not proof of causation.

## Pricing and bounds

Standard event pricing: **$0.002 per confirmed saved observation**, plus **$0.00005 Actor Start**. Three rows total **$0.00605** in Actor event charges. Plan discounts and any applicable Apify platform charges are separate. A comparison with zero changed rows can still incur start/platform usage. Reports and errors are never paid dataset rows. Set a maximum total charge in Run options.

The default is three rows with a 60-second whole-run budget (30–120 seconds allowed). Each official request has a 20-second timeout and a 2 MiB response cap, within the remaining deadline. A 502/503/504 can receive one bounded retry after 500 ms; access denials, rate limits, malformed data and exhausted budgets are not bypassed. The actual platform timeout is also respected. Maximum output is 100 bulletins from the retained official feed.

## Source limits and provenance

- The retained feed is not a complete historical archive and its window can change.
- A bulletin in the feed is not necessarily still active; validity, extensions and cancellations remain in the original message.
- No independent hazard ranking, predicted business loss or operating recommendation is generated.
- Official sources and established emergency channels take precedence for safety decisions.

[Official source documentation](https://www.swpc.noaa.gov/products/alerts-watches-and-warnings) · [Source data and interpretation](https://services.swpc.noaa.gov/products/alerts.json) · [Source field definitions](https://www.swpc.noaa.gov/noaa-scales-explanation)

Source: NOAA/NWS Space Weather Prediction Center. Independent of and not endorsed by NOAA or NWS. Preserve the original message and timestamps when redistributing. This tool is not an emergency alerting service and must not be the sole source for safety-critical decisions.

Report reproducible issues in the Actor’s Issues tab with a non-sensitive input and run link.

## Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [Vendor Incident Monitor - Public Outage Feeds](https://apify.com/maydit/vendor-incident-feed-monitor)

Place official space-weather advisories beside separately reported vendor incidents.

1. Review issue times, parsed validity and the original NOAA message.
2. Run the vendor incident monitor against selected supported status feeds.
3. Present the observations side by side for operator review with their source links.

Temporal overlap does not establish causation, local disruption or an active incident. Official operator instructions take precedence.

### [GDACS Disaster Alert Monitor - Event Revisions](https://apify.com/maydit/gdacs-disaster-alert-monitor)

Build a broader source-labeled situational-awareness dashboard.

1. Export NOAA space-weather messages and their issue times.
2. Run GDACS separately for its supported terrestrial disaster alerts.
3. Keep event type, validity, location scope and source explicit in the combined dashboard.

NOAA space-weather products and GDACS events have different severity scales and geographic scope. Neither feed is a substitute for emergency services.
