They keep publishing the obituary before the body's cold.
Gartner's take, from May: by 2027, 40% of enterprises will demote or decommission their autonomous AI agents because of governance gaps they only discover after a production incident. (Gartner press release, May 26, 2026; the analyst is Shiva Varma.) Not because the models failed. Because nobody was watching the permissions.
Then this month: BCG's Steven Mills — partner, managing director, and the firm's chief AI ethics officer — warned that companies are accelerating agentic AI deployment with "no idea how to manage risk." His line: "Get governance wrong, and every bit of value you've built with experimentation and early wins could unravel because of a single incident." (Fast Company, Sept 2026.)
Mills's prescription is interesting. He says there's no fixed design for good corporate AI risk management, but the starting point is separating use cases that are inherently low-risk — those can be approved automatically — from the ones that carry real risk and need deep human review. Plus a real budget for governance and a senior executive accountable for AI safety.
Read that again. It's an org chart's answer to a practical problem: committees, stage gates, a budget line, an executive with a title.
Here's the thing. I run a version of this every night, and it's none of those things. No committee. No governance budget. One man and a phone.
I run six AI seats on my business — a personal agent, an ops chief of staff, a publishing-desk agent, and three build seats. They read my email, draft my outreach, design automations, run research while I sleep. The governance model fits on a sticky note:
Two-way doors swing. One-way doors don't.
A two-way door is anything reversible — analysis, research, drafting, staging. My agents walk through those on judgment, and I mean it: momentum wins, I don't want a report, I want the work done.
A one-way door is anything you can't take back — money moves, sends, publishes, deletions, credentials. Every one of those stops at the gate. And the gate isn't a process. It's my tap. Structural, not procedural. A draft can sit ready for three weeks; it doesn't send until I say so.
That's it. That's the whole model that Gartner's 40% are supposedly spending governance budgets to build. Varma even names the failure mode: companies treat governance as binary — locked down or fully trusted. The doors model isn't binary. It's proportional. Reversible work flows, irreversible work waits. Small decisions move at tap speed instead of committee speed.
There's a second piece, and it matters: autonomy is earned through clean observation, never granted up front. Nothing in my shop graduates to auto-pilot on day one. New automations start in shadow — run the behavior, take no action — and only earn real permissions after clean observation. Seven clean shadow days before something auto-archives. Three clean days before a migration cutover. The machine proves it's safe by being watched being safe.
And before anything goes out — anything — it runs a sensitive-token scrub, like a virus list: exact matches block, fuzzy matches queue for a human. Official facts only. Never invented rankings, features, or quotes.
That's the enterprise governance problem, solved by one operator with six agents, and it's cheaper and faster than every framework Mills is recommending because there's no committee in the middle. The human review he prescribes for high-risk uses? Mine takes one tap. Low-risk automatic approval? Mine doesn't even need approval — it's a two-way door.
Proof's not in the framework. It's in this morning. Two vendor outreach waves went out — Eastern at 7:54, Pacific at 9:07 — drafted by the seats, sent on my tap, nothing auto-fired. A storm-triggered vendor automation is being designed this afternoon with the gate baked into the spec: it can search impact areas and draft outreach, it cannot send. Overnight research runs while I sleep and lands in a brief I read over coffee. Six seats working, zero production incidents, zero surprises in my inbox.
I'm not saying enterprises should run their AI program from a phone. They can't — scale demands the org chart. I'm saying the org chart versions keep failing on the exact axis the doors model gets right: they try to govern everything the same way, so everything either crawls or crashes. Separate the reversible from the irreversible, put a real human's tap on the irreversible, make everything else prove itself in shadow before it earns anything, and scrub before you publish.
The big shops are about to learn this at scale. The 40% who don't will be the decommissioned ones. The ones who do will discover what I already know: governance that moves at tap speed isn't less governance. It's the only kind fast enough to keep up with the machines.
The best product in the recall pile is not another alert feed. It is the thing that reads the label on the box still sitting on the counter and tells you, this week, whether that lot is in a live file.
That is not a slogan. It is how a CPSC jump, a food-event jump, and cheap vision models rhyme. Three different agencies. One failure mode. The notice exists. The household never matches it to the object they already bought.
The files got busier. Matching did not.
RecallBench, which mirrors the official agency feeds nightly, had U.S. agencies logging 305 CPSC consumer-product recalls in 2024 and 420 in 2025. By mid-September 2026 the same feed already showed 434 CPSC events year to date. Combined FDA and USDA-FSIS food recall events went from 516 in 2024 to 642 in 2025, a 24 percent rise. NHTSA logged 996 vehicle recall campaigns in 2025 and 645 more through mid-September 2026. One of those 2026 campaigns, a Ford and Lincoln tail-light file posted 20 February 2026, named 4,381,878 potentially affected vehicles.
Those are event counts, not vibes. The agencies publish them. The household still has to notice the UPC, the lot code, the establishment number, or the VIN, then walk that string into four different search boxes. Most people do not. The box goes in the pantry. The car stays in the driveway. The notice dies in a feed.
That gap is the product.
Stop treating these as four micro-SaaS names
The X idea mill keeps splitting this into vertical slogans. One bot that watches FDA enforcement. One that watches CPSC. One that watches NHTSA. One that OCRs receipts for tax. Cute. Wrong cut.
The customer does not wake up wanting a “food-safety SaaS.” They wake up because something they already paid for might be in a file, and they cannot reconstruct the match from memory. The category is match-to-object. A frozen dessert with a foreign-object notice. A car with a tail-light campaign. A crib with a CPSC action. A lot code on a deli salad.
If you build four checkers you will raise four small rounds and lose to the shop that treats the photo of the object as one input.
The wedge is a free photo. Not a platform.
Do not start with an account, a pantry graph, or a “safety operating system.” Start with a moment the customer already has in their hand.
Photograph the back of the package. Photograph the VIN plate. Photograph the receipt that still has the UPC. Thirty seconds later: match, no match, or need a clearer lot line. If it is no match, you still captured a labeled object. If it is a match, you show the agency page, the date, the class when the agency uses one, and a draft of the next step — return, repair, or claim. The customer sends it. The model does not.
That is the only honest first offer. No seat fee to see the first answer. You get paid later, on volume of matches that turn into returns, dealer appointments, or warranty work, or on the B2B scoreboard that names which SKUs and which plants keep showing up.
Do not mix food, toys, and vehicles in the first ninety days of go-to-market copy. Pick one door. Grocery is the fastest photo. VIN is the cleanest identifier. Toys and infant gear are the highest-fear door. Pick one and keep the human on anything that files, refunds, or tells a dealer to book a repair.
Why this is buildable now
Two years ago the input was the problem. Lot codes are tiny. UPCs sit under glare. VINs live on a dirty plate. That slop is now the default diet for multimodal models. They can pull a GTIN off a phone photo. They can read a lot line that a human squints at. They still lie. They do not need to be trusted with the claim. They need to be trusted with the first pass against a public file.
The other half of why now is volume plus structure. The FDA enforcement feed, the FSIS notices, the CPSC announcements, and the NHTSA campaigns file are already machine-readable enough to mirror nightly. RecallBench is doing that work in public as of 16 September 2026. You do not need a new behavior from the agencies. You need to sit on files that already exist and on objects people already photograph when they unpack a bag.
Greg Isenberg’s recent mill posts keep landing on photo-as-data and on domain harnesses. The micro-SaaS accounts keep shipping isolated .ai names for consent logs and trial watchers. Combine the photo primitive with the public-file primitive. Do not ship another isolated watcher.
How the company actually compounds
The first dollar is a return, a free dealer fix, or a warranty claim the customer would have missed. That is not the business. The business is the labeled corpus.
After a few thousand matched photos you know which brands produce repeat Class I food events. You know which infant-gear SKUs show up in CPSC files after a holiday spike. You know which VIN prefixes cluster in campaigns that dealers are slow to schedule. That is a B2B product retailers, 3PLs, insurers, and dealership groups will pay for — not because they love dashboards, because the report names the SKU before the next truck leaves.
Consumer volume trains the matcher. Enterprise contracts pay for the map. Do not sell the map before you have closed real matches for real people. A dashboard of “possible exposures” is how this idea dies in a sales deck.
What not to build
Do not build a medical diagnostic. A lot-code match is not a diagnosis. If the file is foodborne illness, point at the agency notice and a clinician. The model drafts the “what the notice says.” A person owns anything that sounds like advice.
Do not build a class-action mill that auto-files. Irreversible steps — claims, attorney retainers, dealer work orders, customs or medical filings — need a human signer. Models draft. People own the send.
Do not brand this as “AI for pantry safety in the agentic era.” That sentence is how you attract the wrong first ten customers. Brand the outcome. The object in the house, checked against the live file, before the box is gone.
A build order that will survive contact
Week 1–2: one checker. Photo in, match or no-match out. No account required to see the first answer. Start with UPC plus lot, or VIN, not both.
Week 3–4: a next-step draft — return script, dealer scheduling note, warranty email — with a human signer. Contingency or per-closed-match only.
Month 2: add the second identifier in the same customer’s drawer. If you started on grocery, add the receipt. If you started on VIN, add the glove-box campaign letter.
Month 3: publish the first ugly internal scoreboard. Which brands, which plants, which VIN prefixes, which holiday weeks. That scoreboard is the seed of the B2B SKU.
If you cannot get a stranger to photograph one label this week, you do not have a company. You have a thesis.
Why this is worth writing, and building
Most idea-mill posts describe a feature. This one describes a shift in who does the tedious work of matching. The matching used to require a person who already reads FDA.gov for fun. It now requires a model that can read the label and a person who will send the claim.
Recovery and match businesses endure because the first action is free and the downside of a miss is visible. That is rare. Most software asks for a seat fee before it has proven a hit. This one pays for itself on the first closed match or it does not deserve a second conversation.
Someone will own the system of record for objects that already sit in houses and still sit in live agency files. The threads will keep proposing a new .ai name for each agency. Ignore the names. Match first. Keep the map.
Will Tygart — Tygart Media. This is the idea-mill series.
This is a live Wednesday morning snapshot of U.S. local-storm activity as of early Wednesday, September 16, 2026. Overnight convection across the south-central Plains into the Midwest produced wind and hail. The Storm Prediction Center 1300 UTC Day 1 outlook holds a Marginal Risk of isolated strong to severe thunderstorms across parts of the Midwest/Ohio Valley and Utah into far northwest Colorado. No convective watches are valid. The Weather Prediction Center Day 1 Excessive Rainfall Outlook holds a Moderate Risk over portions of southern and central Arizona and the Sacramento Mountains of New Mexico. There is no named tropical cyclone threatening U.S. land.
These are county- and ZIP-scale thunderstorms and flash-flood pulses, not a mainland hurricane landfall. Restoration exposure this morning is leftover wind and hail from last night plus water on the Missouri River system and a new monsoon-style flood ticket in Arizona and New Mexico this afternoon. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this morning
SPC issued the 1300 UTC Day 1 Convective Outlook at 0745 AM CDT. Valid 161300Z–171200Z. Headline: isolated strong to severe thunderstorms appear possible today across parts of the Midwest/Ohio Valley and Utah/far northwest Colorado. Risk-area population centers listed by SPC include Columbus, Pittsburgh, Akron, Salt Lake City, and Dayton. Categorical risk is Marginal only. No Slight Risk. No tornado probabilities in the 1300 UTC package.
Current convective watches: none. Most recently issued watch was Severe Thunderstorm Watch 669, already expired. That is the overnight close. Do not treat 669 as a live product.
WPC Day 1 excessive-rainfall language for the period beginning 12Z Wednesday has shifted the organized water story west. The Moderate Risk that covered northeastern Kansas into northwest Missouri on Tuesday is now the just-hit and river-flood desk. Today’s Moderate Risk is over southern and central Arizona and the Sacramento Mountains of New Mexico, with a high-end Slight Risk across much of Arizona into southern Utah and southwestern Colorado. Isolated flash-flood prospects remain possible later today across parts of Illinois, Indiana, and Ohio if cells train on the residual front.
Hotspot 1 — Indiana into Ohio and the upper Ohio Valley
A convectively augmented mid-level vorticity maximum over Illinois and northwest Indiana is forecast to track east across the Ohio Valley and southern Great Lakes. Mid-level westerlies stay modest, generally 20–30 kt. SPC expects additional convective development this afternoon across parts of Indiana into Ohio as a moist low-level airmass destabilizes. Poor lapse rates aloft should limit updraft strength. Locally damaging winds are the hazard if loosely organized clusters form and spread east through early evening, then weaken with loss of heating.
Overnight LSRs already put trees and lines down in Kosciusko and Noble counties in Indiana, plus a measured 65 mph gust near Wallen in Allen County. Northern Indiana and Wilmington, Ohio, offices issued overnight flash-flood warnings for heavy rain of 1.5 to 3 inches in parts of Grant, Blackford, Adams, Wells, and Mercer counties. Those products expired this morning. The water is still on the ground.
Restoration read: wind first this afternoon if clusters organize. Water first in the counties that already took 2–3 inches before dawn. Stage tarps and tree crews in the Indianapolis–Fort Wayne–Dayton–Columbus belt before late afternoon, not after the first warning.
Hotspot 2 — Southern and central Arizona, Sacramento Mountains of New Mexico
This is today’s organized flood ticket. WPC upgraded Day 1 excessive rainfall to Moderate Risk over portions of southern and central Arizona and the Sacramento Mountains. Guidance continues to print 2–3 inches, locally higher, where storms focus on the Mogollon Rim, south-central Arizona including the Phoenix metro and surrounds, southern Utah slot-canyon country, the San Juans of Colorado, and the Sacramentos. Rates above 1 inch per hour for multiple hours are in the discussion. Burn-scar debris flow remains the life-safety language on higher terrain.
SPC did not hang severe probabilities over Arizona and New Mexico on the 1300 UTC outlook. Modest lapse rates, cloud cover, and only marginal deep-layer shear keep the severe-wind/hail threat limited. Gusty outflow is still possible. Water is the story.
Restoration read: extraction and drying on a 24–48 hour mold clock if cells stall over the same ZIP. Photograph interiors only when it is safe. Do not drive flooded washes.
Hotspot 3 — Utah into far northwest Colorado, plus leftover Kansas–Missouri water
On the southeast periphery of a closed upper low over northern California, 35–45 kt of southwesterly mid-level flow persists across the Great Basin. Ongoing storms over eastern Utah and northwest Colorado are in a strongly sheared but weakly unstable environment. SPC leaves room for isolated severe hail or gusts if cells or small clusters can form with filtered afternoon heating. Limited heating should keep the overall severe risk marginal. Grand Junction issued an overnight flash-flood warning for the Lee Burn Scar in central Rio Blanco County; that product expired before dawn.
Kansas and northwest Missouri are no longer the new Moderate Risk. They are the just-hit desk. Overnight LSRs include 2.00-inch hail at Edgerton, Kansas; 1.75-inch hail west of Cairo, Missouri; trees, wires, and power poles in Richmond, Ray County; wires down around Greenwood, Pleasant Hill, Lake Winnebago, and west of Raytown; and a small building damaged north of Clifton Hill. Kansas City/Pleasant Hill has flood warnings on the Grand River near Chillicothe, Sumner, and Brunswick with crests later this week. That is channel water from Tuesday night, not a new watch.
Just hit
SPC preliminary storm reports for the 15/1200Z–16/1159Z window show no tornadoes. Hail clustered from the Texas South Plains through the Kansas City metro into Peoria County, Illinois (1.50 inches near Alta). Wind included 75 mph at McConnell Air Force Base in Sedgwick County, Kansas, with wall panels ripped at a plant nearby; 71 mph at Alva, Oklahoma, and railroad cars overturned east of Avard; 70 mph near Morton, Texas; an RV flipped west of Smyer, Texas; 67 mph at Junction, Utah; trees and lines in Congerville and Brimfield, Illinois; power lines down near Humble City and Eunice, New Mexico.
Tuesday afternoon’s Storm Tracker already covered the Kansas–Missouri Moderate flood risk while it was live. This morning’s desk treats that corridor as aftermath plus river-flood follow-through.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this morning
IN / OH / upper Ohio Valley
Isolated damaging wind, leftover flash flood
SPC Marginal; overnight FFWs expired
Afternoon clusters possible
Southern/central AZ, Sacramento Mtns NM
Flash flood, debris flow on burn scars
WPC Moderate excessive rainfall
Today’s organized water ticket
Eastern UT / NW CO
Isolated hail/gusts, burn-scar runoff
SPC Marginal
Afternoon cells possible
NE KS / NW MO / Grand River
River flooding, wind/hail damage
Flood warnings; LSRs overnight
Just-hit / in channel
TX South Plains / NW OK / south-central KS
Measured severe gusts, isolated hail
LSRs overnight; no watch now
Aftermath
Atlantic / Gulf vs. U.S. mainland
No named cyclone
NHC: no tropical cyclones
Quiet on the mainland coast
What this means for restoration teams
Wind at 60–75 mph is roof, siding, gutter, and tree-on-structure work. Two-inch hail is a roof-survey ticket in Johnson County, Kansas, and neighboring ZIPs. Flash flooding on the Arizona–New Mexico Moderate Risk is wet drywall and a same-night extraction clock if water is inside. Grand River crests later this week are a separate staffing problem from today’s monsoon cells. Do not send one crew to both stories without checking which county has a warning now.
For teams near the Ohio Valley Marginal: stage before mid-afternoon local. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside.
What this is not
This is not a Slight Risk day, not a live watch, and not a U.S. mainland hurricane landfall. NHC reports no tropical cyclones in the Atlantic, eastern Pacific, or central Pacific as of this morning. A trough several hundred miles east of Bermuda has only a low chance of development and is not a land threat today. The work, if it verifies, will be scattered: a wind swath through an Indiana or Ohio county, a flooded wash in Arizona or New Mexico, leftover river water in north-central Missouri.
Looking ahead
SPC Day 2 (Thursday) currently carries no severe thunderstorm areas. WPC Day 2 holds Slight Risks of excessive rainfall for portions of the north-central Plains, Upper Midwest, and southwestern U.S. The next Storm Tracker update should re-check the 1630 UTC Day 1 outlook and any new watches rather than assuming this morning’s Marginal stays the last word.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center Sep 16, 2026 1300 UTC Day 1 Convective Outlook (Gleason/Mead); current convective watches (none valid; last issued Watch 669); SPC preliminary storm reports for 20260915 1200 UTC–20260916 1159 UTC; Weather Prediction Center Day 1 Excessive Rainfall Outlook and discussion; National Weather Service warning text including Wilmington OH, Northern Indiana, Grand Junction, Kansas City/Pleasant Hill, Quad Cities, and Lubbock; National Hurricane Center 800 AM EDT Tropical Weather Outlook, September 16, 2026.
This is a live Tuesday afternoon snapshot of local storm-type events across the United States as of Tuesday, September 15, 2026. The Storm Prediction Center 2000 UTC Day 1 Convective Outlook keeps a Marginal Risk of severe thunderstorms from the south-central Plains into parts of the Midwest. No convective watches are in effect. The organized story this afternoon is water: the Weather Prediction Center Day 1 Excessive Rainfall Outlook holds a Moderate Risk from northeastern Kansas into northwest Missouri, with a high-end Slight Risk wrapping the Kansas City metro and I-70 corridor.
These are county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Restoration exposure tonight is flash-flood water first, then isolated wind-driven roof and tree work where the front fires cells. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this afternoon
SPC issued the 2000 UTC Day 1 outlook at 2:55 p.m. CDT Tuesday, September 15, 2026, valid through 7:00 a.m. CDT Wednesday. The categorical call is Marginal. Population centers listed in the risk area include Indianapolis, Kansas City, Wichita, St. Louis, and Toledo. Summary language: strong to locally severe thunderstorms may occur from the south-central Plains into parts of the Midwest this afternoon and evening, with at least isolated damaging wind gusts possible. SPC explicitly opted against a categorical upgrade. As of the SPC watches page update Tuesday afternoon, no watches are currently valid. The most recently issued watch was Tornado Watch 669 on Monday.
Mesoscale Discussion 2300, issued 1:59 p.m. CDT, covered the Texas Panhandle into central Kansas. Watch issuance probability was 20 percent. Language: thunderstorm coverage increasing; sporadic strong gusts, with a locally greater chance of 50–65 mph from northwest Oklahoma into south-central and east-central Kansas. Most probable peak wind up to 60 mph; hail up to 1.25 inches. A watch was not anticipated. By late afternoon the current-MCD page showed no mesoscale discussions in effect.
WPC’s Day 1 Excessive Rainfall Outlook, updated 1556 UTC Tuesday and valid 16 UTC Tuesday through 12 UTC Wednesday, is the higher-confidence overlay. Moderate Risk covers portions of northeastern Kansas into northwest Missouri and clips far southeast Nebraska along the Missouri River. Guidance supports 2–3 inch areal averages and locally 3–5 inches from just north of Topeka toward St. Joseph. Flash-flood guidance is already low after morning rain. A high-end Slight Risk surrounds that core, including the Kansas City metro and I-70. A separate Slight Risk remains over eastern Arizona and western New Mexico on monsoon-style cells.
National Hurricane Center: no tropical cyclones in the Atlantic. Tropical Depression Fifteen-E is weakening well out in the eastern Pacific (about 15.7°N, 125.0°W, 30 mph). Post-tropical Norbert is a remnant low far from U.S. land. Neither threatens the U.S. mainland this afternoon.
Hotspot 1 — Northeast Kansas into northwest Missouri
This is the live flood desk. WPC broadened the Moderate Risk on the 16Z update to match an uptick in amounts and coverage near the Kansas–Nebraska–northwest Missouri juncture. Cold front slides southeast; best heavy-rain window is late afternoon through overnight as the low-level jet injects moisture along a boundary-parallel flow. Neighborhood probabilities for greater than 1 inch per hour have run 40–70 percent for several hours in the core.
Cities and counties to watch: Topeka and northeastern Kansas counties north of I-70; St. Joseph and neighboring northwest Missouri counties; far southeast Nebraska along the Missouri River; the Kansas City metro on the high-end Slight, not inside the Moderate core but close enough that a southward shift matters.
Restoration read: water first. Stage extractors and drying kits for basements, slab leaks, and low-water crossings that fail after dark. Morning rain already lowered flash-flood guidance. Photograph interiors only if it is safe. Do not treat Kansas City the same as St. Joseph without checking which county has a warning now.
Hotspot 2 — South-central Kansas, northern Missouri, and the cold-front wind line
SPC’s 20Z update said locally greater potential for a couple of damaging or severe wind gusts may exist across south-central Kansas and northern Missouri where guidance shows greater storm coverage on the cold front. Enhanced deep-layer shear is displaced north of the boundary; better thermodynamics sit farther south. That split is why the outlook stayed Marginal. Earlier MCD 2300 language pointed at northwest Oklahoma into south-central and east-central Kansas for 50–65 mph gusts if cells organize.
Cities and counties to watch: Wichita and south-central Kansas; northwest Oklahoma; northern Missouri counties along and north of the front; scattered cells from the Texas Panhandle east-northeast toward Illinois as convective temperatures are reached.
Restoration read: isolated wind, not a line you staff like a Slight-plus-watch night. Tarps and tree crews if a Severe Thunderstorm Warning verifies. Hail is secondary and limited by warm temperatures aloft.
Hotspot 3 — Four Corners / Southwest rain and leftover Plains wind tickets
Isolated to widely scattered thunderstorms had formed across the Four Corners by about 1930 UTC. SPC notes weak buoyancy in a deep, well-mixed boundary layer — enough for an isolated strong to perhaps severe cell, not a concentrated severe area. WPC keeps a Slight Risk of excessive rainfall over eastern Arizona and the western half of New Mexico, with locally 2–3 inches in the hardest terrain.
Yesterday’s organized wind corridor is already tickets. SPC storm reports for the 1200 UTC September 14–15 window include measured gusts of 87 mph near Guide Rock, Nebraska; 83 mph near Smith Center, Kansas; 77 mph near Amy, Kansas; 76 mph near Beatrice, Nebraska; 75 mph near Elmwood, Nebraska; plus trees and power lines in Cass and Lancaster Counties, Nebraska, Clarinda and Ames, Iowa, and other High Plains points. Today’s 1200 UTC-forward LSR page still showed no tornado, hail, or wind reports as of this afternoon scan. That can change after dark.
Restoration read: Southwest is flash-flood and outflow in terrain. Nebraska–Kansas–Iowa wind from Monday night is roof, siding, and tree-on-drop work already on the books.
Just hit
Monday evening’s Tornado Watch 669 (western into central Iowa, far northwest Missouri, eastern Nebraska, effective 4:50 p.m. until midnight CDT Monday) is closed. The gust and tree reports listed above are that corridor. Iowa river and urban water from the last two days can still be in the channel even if today’s new Moderate Risk sits farther southwest. Today’s new work, if it verifies, is flash flooding on the Kansas–Missouri Moderate Risk plus isolated wind along the front. No new U.S. mainland tropical landfall.
Pulse table
Region
Main threats
SPC / NWS level
Status this afternoon
NE Kansas / NW Missouri / SE Nebraska
Flash flood, training heavy rain
WPC Moderate excessive rainfall
Live flood overlay; evening peak
Kansas City / I-70 corridor
Heavy rain, urban flooding
WPC high-end Slight
Watch the southward shift
South-central KS / N Missouri / NW OK
Isolated damaging wind
SPC Marginal; MCD 2300 watch unlikely
No watch; scattered cells
Plains–Midwest Marginal envelope
Isolated wind, lightning
SPC Marginal (~166,470 sq mi)
Disorganized vs Monday night
Eastern AZ / western NM
Flash flood, strong outflow
WPC Slight
Afternoon–overnight terrain cells
NE / KS / IA just-hit wind
Roof, trees, service drops
Monday Watch 669 closed
Aftermath tickets
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
NHC quiet on the mainland
Quiet
What this means for restoration teams
Water on a Moderate Risk with already-wet ground is wet drywall and a 24–48 hour mold clock, plus vehicles in flooded crossings. Isolated 50–65 mph gusts are roof, siding, gutter, and tree-on-structure work in a single county, not a regional wind event. Monday night’s 70–87 mph measured gusts in southern Nebraska and north-central Kansas are the jobs already called in.
For teams near Topeka, St. Joseph, and Kansas City: stage extraction before the overnight training window, not after the first flooded intersection. Property owners should photograph damage if it is safe, call the carrier, and start extraction the same night if water is inside. Turn around, don’t drown.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. SPC did not upgrade to Slight. No convective watch is out this afternoon. Tropical Depression Fifteen-E and remnant Norbert are Pacific and offshore. The work tonight, if it comes, will be scattered: a flooded county in northeast Kansas or northwest Missouri, an isolated wind swath on the front, leftover tree jobs from Monday night. That is the local-storm pattern this desk should staff.
Looking ahead
SPC Day 2 remains generally quieter on organized severe over the central United States. A Marginal Risk of severe thunderstorms is flagged Wednesday morning across the Great Salt Lake / Salt Lake City vicinity. Along the remnant front from the Ohio Valley into the lower Missouri Valley, scattered strong storms are possible Wednesday afternoon in weak shear, without a 5 percent severe-wind area on the 0600 UTC Day 2 package. Day 3 language available this afternoon showed no severe thunderstorms. Watch the next Storm Tracker update rather than assuming tonight’s flood core is the last line of the week.
Sources and how to verify
Primary sources dated Tuesday, September 15, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook (issued 2:55 p.m. CDT); SPC Current Watches page (no watches valid; last watch 669); Mesoscale Discussion 2300; SPC storm reports for 20260914 and 20260915; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 1556 UTC; National Hurricane Center public page as of 21:06 UTC. Morning desk on the same calendar day: Storm Updates, Tuesday morning, September 15, 2026.
Open field playbook. No patent. Copy it. Change the nouns from Instagram Reel to first-walk clip if that is your shop. If it stops you from treating a faster poll as a strategy, good.
License: do what you want. Attribution nice, not required. Tygart Media is not a OneUp partner, reseller, or affiliate. Links below go to official product doors. No tracking parameters. No referral codes. No reprint of the vendor email body.
Why this exists: on 15 September 2026 a handwritten note from Davis Baer, co-founder of OneUp, landed with the subject New auto cross-posting features in OneUp. Three product facts. The source check moved from every two hours to every one hour. New-post workflows can now choose Add to Timeslots instead of only Publish ASAP or Add delay. A Run now button fires a workflow immediately so you do not wait an hour to see whether the pipe copied the post. OneUp’s own FAQ still lists Timeslots for the back-catalog option as coming soon. That is the vendor record. The operator problem is the slot, not the clock.
Direct answer
OneUp auto cross-posting watches a Source account on Instagram, Facebook, or TikTok and copies qualifying posts to Destination accounts the product supports. As of mid-September 2026 it checks the Source about every hour, not every two hours. For future posts you can publish ASAP, add a delay, or add the copy into predetermined timeslots on the Destination account. Run now tests the workflow without waiting for the next poll. Image workflows and video workflows stay separate. Keyword include/skip filters from August 2026 still apply. Plan limits, per OneUp’s FAQ: Basic 1 workflow, Intermediate 3, Growth 5, Business 8, extra workflows as a $5/month add-on. Official APIs only. Timeslots on “Cross-post existing posts” is not claimed live here. The Destination clock is still not a local service page.
FAQ that names the poll, sources, and workflow counts: Cross-posting FAQ
Timeslots help (includes the cross-posting “Add to Timeslots” line): Timeslots help
If you do not run the tool, do not scrape the email for a screenshot library. This page does not republish Davis’s pitch or the trial offer.
1. What actually changed
Piece
Before this note
Vendor claim now
Source poll
About every two hours (the number this desk already published on 3 September 2026).
About every one hour.
When the copy publishes
Publish ASAP or Add delay.
Those two, plus Add to Timeslots on new-post workflows.
Prove the pipe
Wait for the next poll.
Run now fires the workflow immediately.
Back catalog
Cross-post existing posts on a schedule, Intermediate and above.
Same option. Timeslots on that option: coming soon, per the vendor note.
A one-hour poll is hygiene. It cuts the lag between a Source post and a Destination copy. It does not decide whether 11:07 p.m. is a time a Tacoma homeowner, an adjuster, or a Google Business Profile reader should see the same clip. ASAP with a shorter fuse is still a reprint machine. The slot is the gate.
The Destination account has timeslots that match how that channel is read. LinkedIn at lunch. Neighborhood Facebook in the evening. Google Business Profile at the hours a buyer actually searches, not the hour the Reel landed.
The Destination post is a pointer. The record lives on your domain and on the Business Profile.
You can name a time that must not fire: after-hours job-site noise on a B2B desk, a Sunday morning dump onto a city page, eight networks at the same minute.
Do not treat Run now as:
Permission to publish. It is a test of the pipe.
A substitute for reading the Destination after the copy lands.
Proof you have distribution. Proof is a cited answer or a booked job.
3. SEO, AEO, GEO — the clock is not the cite
SEO is crawlable pages with one job each. A Destination post scheduled for 1:30 p.m. is still a feed object. It expires. The service page does not. Cross-posting moves the clip. It does not invent the page.
AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers quote pages that state the question, answer it in the first screen, and keep entities clean. Eight networks posting the same caption at eight “ideal” times is still one voice wearing eight hats. Timing does not create a cite.
GEO here still means two things at once:
Generative engine optimization — structured enough that models can reuse you without inventing your city.
Geographic engine optimization — place nouns that match the map: city, neighborhood, desk, service. And, on this drop, when a place-bound channel is allowed to speak.
A timeslot is how you stop a 10:14 p.m. Source Reel from landing on a Google Business Profile at 10:14 p.m. just because the poll finally saw it. The hour is the gate. The page on your domain is the cite.
4. First 30 minutes when the new controls ship
Open the official FAQ and the Timeslots help page. Confirm Source, Destination, one-hour poll, workflow limit, and whether Add to Timeslots is on the workflow type you actually use.
Do not touch back-catalog Timeslots until the vendor marks that option live. The 15 September note said coming soon for “Cross-post existing posts.”
Keep the caption tokens from the filter pass. Include-list what may travel. Skip-list interiors, minors, named carriers, unfinished estimates.
Build Destination timeslots per channel, not one national grid. A LinkedIn desk and a neighborhood Facebook page do not share a 1:30 p.m. / 6:45 p.m. pair just because the email used that example.
Use Run now on a throwaway Source post with a skip token you can see. Confirm the Destination, the time, and the link to your domain. Then delete the test.
Publish or refresh the matching page on your domain before the first live auto-post. The Destination post points at the page. The page does not point at a disappearing feed.
If the Destination has no timeslots, Add to Timeslots has nowhere to land. Create the slots first. OneUp’s Timeslots help is the door for that step.
5. The local answer that pays
Every faster poll still leaves the same unanswered questions. Write them as pages, not captions.
Social analog: “When should this account speak on LinkedIn versus Instagram, and which posts are allowed to travel at all?”
Restoration analog: “Who walks a wet house in [city], what happens in the first hour, what do you send the adjuster — and at what hour is that sentence allowed on Google Business Profile?”
Name the place. Name the service. Name the next action. Name the channel. Name the hours that channel may speak. That is the cite.
Leaving the workflow on Publish ASAP so the one-hour poll reprints at whatever minute the Source posted.
Copying the email’s 1:30 p.m. / 6:45 p.m. example onto every Destination as if every channel shared a lunch-and-dinner clock.
Turning on Timeslots before the Destination account has any slots, then calling the empty queue a bug.
Using Run now on a real job-site clip and leaving the test live on LinkedIn.
Assuming back-catalog Timeslots already shipped. The vendor said coming soon. Do not invent the toggle.
Letting Destination feeds become the only public record. Feeds rot. Domains stay.
Calling an hourly unfiltered workflow “GEO strategy.” GEO is place + cite + when the place-bound channel may speak.
7. The sentence that pays the shop
“The tool can copy a post faster now. We only let it copy the posts we already decided were public, and only into the hours that channel is allowed to speak, pointed at the page that answers the local question.”
Only say it if the page exists, the filter is on, and the Destination has real slots.
8. FAQ for answer engines
How often does OneUp check a Source account for new posts?
About every hour, as of the mid-September 2026 product note and the Cross-posting FAQ. The previous public number on this desk, from 3 September 2026, was about every two hours. RSS feeds are a different pipe and are not this interval.
What does Add to Timeslots do in a cross-posting workflow?
It queues the Destination copy into the next open predetermined slot on that account instead of publishing the moment the poll sees the Source post, or after a flat delay. OneUp’s Timeslots help confirms the option on cross-posting workflows. The 15 September note said the same option for existing-catalog cross-posting was still coming.
What does Run now do?
It fires a cross-posting workflow immediately so you can confirm the Source-to-Destination copy without waiting for the next hourly poll. Treat it as a test button. Read the Destination after it runs. Do not use a private job clip as the test object.
Does a faster poll help local SEO or AI answers?
No, not by itself. Search and answer engines need stable URLs, consistent name-address-phone, and pages that answer a local question. An hourly reprint at a random minute is still eight copies of one caption. Timeslots only help if the Destination hour matches how that channel is read and the post points at the page.
Which platforms can OneUp use as a Source?
Per OneUp’s FAQ: Instagram, Facebook, and TikTok. Destinations can be any network the product supports. Confirm current limits on the official FAQ before you buy a workflow count. Image and video still need separate workflows.
9. What this is not asking
No meeting. No partnership badge. No unofficial screenshot pack. No reply-for-a-trial pitch. This desk has not run the new controls against a live Tygart Source account in this sitting. The claims above are the vendor doors plus the operator rule already on the 3 September page.
OneUp already knows how to shorten a poll and attach a slot. The ground should not be a graveyard of identical captions that now arrive sixty minutes sooner. Open the official door if you run the tool. Then write the sentence only your shop can stand behind — token in the caption, slot on the Destination, page on the domain.
This is a live Tuesday morning snapshot of local storm-type events across the United States as of Tuesday, September 15, 2026. Overnight the organized wind corridor that ran northern Kansas, southern and eastern Nebraska, and western and central Iowa is the just-hit desk. This morning the Storm Prediction Center holds a Marginal Risk of severe thunderstorms from the south-central Plains into parts of the Midwest. The louder national product is flood: the Weather Prediction Center Day 1 Excessive Rainfall Outlook carries a Moderate Risk over portions of northeastern Kansas into northwest Missouri, with a high-end Slight wrapping the Kansas City metro and the I-70 corridor.
These are county- and ZIP-scale thunderstorms and flash-flood cells, not a mainland hurricane landfall. Restoration exposure today is leftover wind damage from last night plus a new heavy-rain ticket on already-wet Kansas and Missouri ground. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this morning
No Storm Prediction Center convective watch is in effect. Tornado Watch 669, issued late Monday evening, expired at 0500 UTC Tuesday (midnight CDT). Severe Thunderstorm Watch 668 from Monday afternoon is also down. The 1300 UTC Day 1 Convective Outlook (issued 7:28 a.m. CDT) is Marginal only. SPC language: strong to locally severe thunderstorms may occur from the south-central Plains into parts of the Midwest this afternoon and evening, with at least isolated damaging wind gusts possible. A Slight upgrade was considered for eastern Kansas into Missouri if an organized cluster can form, but the 1300 UTC package left probabilities at Marginal.
WPC’s 0800 UTC Day 1 Excessive Rainfall Outlook is the headline product. A Moderate Risk covers northeastern Kansas into northwest Missouri and clips the far southeast corner of Nebraska along the Missouri River. Guidance centers the heaviest totals just north of Topeka toward St. Joseph, with 2 to 3 inches areal-average and locally 3 to 5 inches possible. Kansas City and the I-70 corridor sit in a high-end Slight. A broader Slight Risk extends south along the cold front on the High Plains and northeast into Midwest counties that already took rain overnight. A separate Slight Risk remains over eastern Arizona and western New Mexico on monsoon-style cells.
National Hurricane Center: there are no tropical cyclones in the Atlantic. Tropical Depression Fifteen-E and Tropical Depression Norbert are both well out in the Pacific and not a U.S. mainland landfall threat.
Hotspot 1 — Northeastern Kansas into northwest Missouri (flood)
This is today’s primary new ticket. WPC coordinated a Moderate Risk with the Topeka and Kansas City weather forecast offices after neighboring counties already saw localized flash flooding earlier in the event. Precipitable-water anomalies of +2 to +3 standard deviations and flash-flood guidance that is already lowered set up 1-inch-per-hour rates after late-afternoon initiation. Best window is late afternoon through tonight as a low-level jet reloads the boundary. Training west-southwest to east-northeast is the mode that fails streets, underpasses, and small creeks first.
Cities and counties to watch: Topeka and the northeastern Kansas counties north of I-70; St. Joseph and neighboring northwest Missouri counties; the Kansas City metro as a high-end Slight, not the Moderate core; far southeast Nebraska along the river.
Restoration read: water first. Extraction and drying on a 24-hour clock if cells train over the same ZIP that already took rain Monday night. Do not treat Kansas City as the Moderate core unless WPC or the local office upgrades it later today.
Hotspot 2 — South-central Plains into the Midwest (Marginal wind)
A surface cold front will slide slowly south-southeast across the central Plains and mid-Mississippi Valley through this evening and stall late. Dewpoints in the 60s to low 70s sit ahead of it from the southern High Plains to the southern Great Lakes. SPC expects storms to develop roughly 20–23Z along much of the front. Loosely organized clusters with damaging wind are the primary severe concern, more so where heating is stronger on the southern and central Plains. Isolated hail is possible if a marginal supercell can hold from eastern Kansas into Missouri. Population under the 5 percent wind contour includes Wichita, Kansas City, St. Louis, Indianapolis, and Chicago.
Restoration read: isolated 60 mph-class gusts and trees on service drops, not a regional wind event. Stage in the counties that already have a Severe Thunderstorm Warning, not the entire Marginal contour.
Hotspot 3 — Southwest scatter and leftover Iowa water
WPC keeps a Slight Risk of excessive rainfall over eastern Arizona and the western half of New Mexico. Isolated 2 to 3 inch cores on terrain are possible. SPC does not have severe probabilities over the Four Corners this morning; gusty outflow and small hail remain possible but unorganized.
Iowa is yesterday’s and last night’s water still in the channel. NWS Des Moines had a Flash Flood Warning into 9:00 a.m. CDT this morning for parts of Dallas, Madison, Adair, Cass, Audubon, and Guthrie counties after 1 to 3 inches already on the ground. That is extraction work already on the books, not a new watch.
Just hit
Preliminary Storm Prediction Center local storm reports from the 1200 UTC Monday to 1159 UTC Tuesday window show a long wind corridor and almost no hail. One landspout was reported near Arboles, Colorado. No tornado path damage is in the filtered LSR set as of this morning desk.
Measured wind highlights overnight: 87 mph 3 NE Guide Rock, Webster County, Nebraska; 83 mph 3 SE Smith Center, Smith County, Kansas; 77 mph 4 NNW Amy, Lane County, Kansas; 76 mph 4 N Kendall, Hamilton County, Kansas, and again 2 NNW Beatrice, Gage County, Nebraska; 75 mph 5 ESE Elmwood, Cass County, Nebraska; 74 mph 4 SW McClelland, Pottawattamie County, Iowa; 73 mph 1 N Shelby, Shelby County, Iowa; 71 mph near Richfield, Morton County, Kansas. Tree and power-line damage reports came in from Cass and Lancaster counties in Nebraska, Clarinda and Ames in Iowa, plus scattered tree work in Hinds County, Mississippi, and a power pole down in Tucson, Arizona. That is Monday night’s wind ticket. Today’s new work, if it verifies, is flash flooding on the Kansas–Missouri Moderate Risk.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this morning
NE Kansas / NW Missouri / SE Nebraska
Flash flood, training heavy rain
WPC Moderate excessive rainfall
Afternoon through tonight
Kansas City / I-70 corridor
Heavy rain, urban flood
WPC high-end Slight
Tonight
S-central Plains into Midwest
Isolated damaging wind, isolated hail
SPC Marginal
20–23Z initiation
Northern KS / NE / western–central IA
Wind damage, trees, leftover water
LSRs overnight; Watch 668/669 expired
Just-hit / aftermath
SW Iowa (Des Moines CWA)
Flash flood from overnight rain
FFW into 9 a.m. CDT
Morning water
E Arizona / W New Mexico
Terrain flash flood, gusty outflow
WPC Slight
Afternoon cells
Atlantic vs. U.S. mainland
No landfalling tropical cyclone
NHC quiet on the Atlantic
Quiet
What this means for restoration teams
Last night’s 70–87 mph gusts are roof, siding, gutter, and tree-on-structure work in Webster and Smith counties, the Kansas High Plains, Gage and Cass in Nebraska, and Pottawattamie and Shelby in Iowa. Photograph in daylight if it is safe. Today’s new ticket is water on the Topeka–St. Joseph axis. Heavy rain on already-wet ground is wet drywall and a 24–48 hour mold clock. Iowa southwest counties that sat under the early-morning flash-flood warning are extraction first, not a new severe-wind desk.
Do not staff the entire SPC Marginal contour as if it were yesterday’s Slight. Yesterday’s Slight verified as a wind line. Today’s organized threat is rainfall rate, not shear.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. Watch 669 is expired. SPC left the Day 1 package at Marginal because an organized cluster is still too uncertain. The work today, if it comes, will be scattered: a flooded intersection north of Topeka or around St. Joseph, a wind swath in an eastern Kansas or Missouri county if a cluster does organize, leftover trees from last night’s Nebraska–Iowa line. That is the local-storm pattern this desk should staff.
Looking ahead
SPC Day 2 is Marginal again Wednesday morning near the Great Salt Lake / Salt Lake City vicinity for hail and wind on a shortwave. Day 3 is no severe. WPC will reissue the excessive-rainfall outlook later this morning; treat the Moderate contour as live until that update. The next Storm Tracker desk will catch any watch that fires on the Kansas–Missouri boundary this afternoon.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center 1300 UTC Day 1 Convective Outlook for Tuesday, September 15, 2026; SPC current watch page (Tornado Watch 669 expired 0500 UTC); SPC preliminary local storm reports for the 20260914 reporting day; Weather Prediction Center Day 1 Excessive Rainfall Outlook issued 0800 UTC Tuesday; National Weather Service warning text including Des Moines flash-flood warning IAC001-009-029-049-077-121; National Hurricane Center Tropical Weather Outlook showing no Atlantic tropical cyclones.
This is a live Monday afternoon snapshot of local storm-type events across the United States as of Monday, September 14, 2026. The Storm Prediction Center 2000 UTC Day 1 Convective Outlook holds a Slight Risk of severe thunderstorms across northern Kansas and southern and eastern Nebraska into western and central Iowa. Severe Thunderstorm Watch 668, issued at 3:45 p.m. CDT, covers western and northern Kansas and south-central Nebraska until 10:00 p.m. CDT. The Weather Prediction Center Day 1 Excessive Rainfall Outlook, valid 12 UTC Monday through 12 UTC Tuesday, keeps a Moderate Risk over portions of central and southwestern Iowa.
These are county-scale thunderstorms and flash-flood pulses, not a U.S. mainland hurricane landfall. Restoration exposure tonight is wind-driven roof and tree work in the watch, isolated hail, a conditional tornado in the eastern Nebraska–western Iowa corridor if a surface-based supercell holds, and interior water where Iowa cells train. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this afternoon
Watch 668 is the organized wind desk. SPC issued it at 3:45 p.m. CDT Monday, September 14, 2026, for portions of western and northern Kansas and south-central Nebraska, effective until 10:00 p.m. CDT. Primary threat language is scattered damaging winds and isolated significant gusts to 80 mph, plus isolated large hail to 1.5 inches. High-based storms are expected to continue in a hot, well-mixed environment and spread northeast near a pre-frontal trough.
The 2000 UTC Day 1 outlook, issued 3:00 p.m. CDT by Karstens and Wendt, did not change the categorical Slight Risk. Summary language: scattered strong to severe thunderstorms should occur across parts of eastern Nebraska into western and central Iowa this afternoon and evening. Large hail, severe wind gusts, and tornadoes all appear possible. Severe thunderstorm winds will also be possible across northern and western Kansas. An 18z Omaha sounding showed about 2,232 J/kg MUCAPE as destablization spread north into central and eastern Nebraska. SPC still expects an elongated area of convection from north-central Kansas into south-central and eastern Nebraska and west-central Iowa, favoring supercells early, then a quick transition to clusters and line segments. Exact initiation remains uncertain in recent HRRR and RRFS runs. No SPC mesoscale discussion was in effect as of mid-afternoon UTC; Watch 668 is the current watch product.
WPC’s Day 1 excessive-rainfall discussion, issued 3:40 a.m. EDT Monday, September 14, 2026, maintains a Moderate Risk over portions of central and southwestern Iowa, coordinated with the Des Moines forecast office. HREF blended-mean QPF of 3–5 inches is cited near Des Moines and points south and southwest, with neighborhood probabilities of 60–80 percent for more than 3 inches and 3-hour flash-flood-guidance exceedance probabilities of 50–70 percent. A broad Slight Risk still covers much of the Midwest from the Door Peninsula through eastern Nebraska, plus a separate Slight Risk over the Southwest west of the I-25 corridor.
Hotspot 1 — Eastern Nebraska into western and central Iowa
This is the Slight Risk core. SPC places 5 percent tornado probabilities over parts of eastern Nebraska near Omaha, Lincoln, Council Bluffs, Bellevue, and Fremont, with 2 percent tornado probabilities extending toward Des Moines, Sioux City, Ames, West Des Moines, and Ankeny. Fifteen-percent wind and hail contours overlap the Omaha–Lincoln–Council Bluffs corridor. A 40–50 kt nocturnal low-level jet is forecast to increase effective storm-relative helicity this evening. SPC notes lingering low-level inhibition on RAP soundings and says it remains unclear whether convection will fully tap that shear. A sustained surface-based supercell in that environment would conditionally be capable of a strong tornado. Weak instability farther east in eastern Iowa should limit the severe risk deeper into the night.
Cities and counties to watch: Omaha, Lincoln, Bellevue, Fremont, and Council Bluffs; Sioux City, Fort Dodge, Ames, Des Moines, West Des Moines, and Ankeny; counties along and just ahead of the cold front from southeast Nebraska into west-central Iowa.
Restoration read: wind and hail first if supercells hold, then water if the same cells train on the WPC Moderate footprint. Stage tarps, generators, and extraction pumps before dark. Treat a tornado warning as a narrow local survey, not a regional event.
Hotspot 2 — Watch 668: western and northern Kansas, south-central Nebraska
The watch box runs roughly 45 miles north and south of a line from 145 miles southwest of Hill City, Kansas, to 50 miles east of Hastings, Nebraska. That is high-based, mixed-layer convection along the pre-frontal trough, not the same supercell corridor as Omaha. Primary threats are damaging wind, isolated 80 mph gusts, and hail to about 1.5 inches through 10:00 p.m. CDT.
Cities and counties to watch: Hill City, Hays, and northern Kansas counties in the watch outline; Hastings, Grand Island, and south-central Nebraska counties in and near the box. Confirm the county list on the Watch 668 outline update at SPC before you pre-position.
Restoration read: dry-microburst and outflow wind on roofs, siding, and center-pivot country. Photograph in remaining daylight only if it is safe. Hail claims will be isolated, not a swath unless a cell stays surface-based longer than expected.
Hotspot 3 — Central and southwestern Iowa flood Moderate, plus Southwest rain
The flood desk is Iowa. WPC introduced a small Moderate Risk for this Day 1 period because CAM guidance clustered 3–6 inch totals south of I-80, with urban streets and low-water crossings the first failures. A broader Slight Risk still covers eastern Nebraska through much of the Midwest. Expectation is scattered flash flooding tonight into early Tuesday morning.
The Southwest Slight Risk covers eastern Arizona, much of New Mexico west of I-25, and southwestern Colorado. PWATs are cited near the 95th–99th percentile. That is monsoon-style heavy rain on complex terrain and remnant burn scars, plus strong outflow, not the Plains watch.
Restoration read: Iowa is water and a 24–48 hour mold clock if 3-inch cores verify in town. The Southwest is localized washouts and urban flooding, not a CAT roster.
Just hit
SPC storm reports for the 12 UTC Monday, September 14, 2026 through 12 UTC Tuesday window showed no tornado, hail, or wind LSRs at the time of this afternoon desk. That is a quiet start to the convective day, not a forecast of a quiet evening. Last night’s 12 UTC Sunday–Monday window still holds the tickets already on the board: tree and wire work across Ohio, Pennsylvania, New York, and West Virginia from Sunday’s upper Ohio Valley–Northeast line; a roof peeled in Fox Township, Carroll County, Ohio; microburst-style trees and minor roof damage near Cloverport, Hardeman County, Tennessee; 1.00-inch hail near Sterling, Johnson County, Nebraska, and in Cascade and Judith Basin counties, Montana; a 61 mph gust near Patagonia, Arizona.
Sunday’s organized wind corridor is yesterday. Today’s new work, if it verifies, is Watch 668 and the eastern Nebraska–Iowa Slight Risk plus Iowa flash flooding.
Pulse table
Region
Main threats
SPC / NWS level
Status this afternoon
Eastern NE / western–central IA
Hail, damaging wind, conditional tornado
SPC Slight (2000 UTC)
Live Slight; initiation still uncertain
Western / northern KS, south-central NE
Damaging wind to 80 mph, hail to 1.5 in
Watch 668 to 10 p.m. CDT
Live watch
Central / southwestern Iowa
Flash flood, 3–6 in cores possible
WPC Moderate excessive rainfall
Tonight into Tuesday morning
Midwest Slight (Door Peninsula to eastern NE)
Scattered flash flood
WPC Slight
Overnight
E AZ / NM west of I-25 / SW CO
Heavy rain, outflow, burn-scar flood
WPC Slight
Afternoon–evening cells
Eastern North Carolina
Isolated gusty wind, small hail
Local / no categorical severe area
Isolated
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
NHC: no Atlantic TCs
Quiet on the mainland coast
What this means for restoration teams
Watch 668 wind at 65–80 mph is roof, siding, gutter, and tree-on-structure work in Kansas and south-central Nebraska. The Slight Risk east of that box is the same plus a conditional tornado and large hail if a supercell holds from Lincoln–Omaha into western Iowa. Iowa’s Moderate flood risk is wet drywall and a same-night extraction clock if the 3-inch HREF signal verifies south of I-80. Do not send one crew to both the watch box and Des Moines without checking which county has a warning now.
For teams in or near Watch 668: stage before sunset, not after the first warning. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. National Hurricane Center products as of Monday afternoon, September 14, 2026, show no tropical cyclones in the Atlantic. Tropical Storm Norbert is in the east-central Pacific about 1,125 miles east of Hilo, Hawaii, with 40 mph winds and a weakening trend. Tropical Depression Fifteen-E is about 785 miles southwest of the southern tip of Baja California. Neither threatens U.S. mainland land. The work tonight, if it comes, will be scattered: a wind swath in the Kansas–Nebraska watch, a hail or tornado report in the eastern Nebraska Slight Risk, flooded intersections south of I-80 in Iowa.
Looking ahead
The SPC Day 2 Convective Outlook issued 12:14 p.m. CDT Monday, September 14, 2026 (valid 12 UTC Tuesday through 12 UTC Wednesday) is a Marginal Risk in a corridor from Kansas into western Ohio. Summary language: scattered strong thunderstorms may occur from the Great Lakes southwestward through the lower Missouri Valley Tuesday afternoon and evening, with at least isolated damaging wind gusts possible. Shear is forecast to be weak. Storms should be primarily short-lived, with a few clusters near the front. Watch the next Storm Tracker update rather than assuming Watch 668 is the last line of the week.
Sources and how to verify
Primary sources dated Monday, September 14, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook; Severe Thunderstorm Watch 668; SPC current watches and today’s LSR page (no reports in the 12 UTC Monday window at desk time); Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0733 UTC; National Hurricane Center Atlantic and East Pacific public pages. Morning desk on the same calendar day: Storm Updates: Eastern Nebraska–Iowa Slight Risk, Iowa Flood Moderate — Monday, September 14, 2026 (Morning).
The travel idea mill keeps shipping seat-map tools and expense apps. The actual product this year is narrower. It tells a passenger, in the gate line, whether the delay already triggered a cash refund under federal rules — before they tap the voucher.
That is not a travel dashboard. It is a verdict on money that already left the card.
The rule is not a rumor
In April 2024 the U.S. Department of Transportation issued the Refunds and Other Consumer Protections final rule. It is now 14 CFR Part 260. For a scheduled flight to, from, or within the United States, a cancellation or a significant delay or change can trigger a full refund of the fare plus taxes and ancillary fees when the passenger does not take the new itinerary and does not accept a voucher, credit, or other substitute.
The refund is supposed to be automatic. Credit-card refunds have a seven-business-day clock. Other payment methods have twenty calendar days. Carriers must tell the passenger that cash is an option before they pitch miles.
DOT later carved a narrow exception. A July 8, 2026 notice of enforcement discretion, extending a December 5, 2025 pause, says the Department will not treat a mere flight-number change as a cancellation if the passenger is rebooked and the trip has no significant change or delay. Three hours or more on a domestic departure or arrival still counts. A different airport still counts. A class downgrade still counts. The exception is the number on the ticket, not the time on the board.
The volume is not a vibe
Bureau of Transportation Statistics TranStats, marketing-carrier view, January through June: 85,998 cancelled operations in 2026, or 2.23 percent of 3,856,905 flights. Same window in 2025: 59,609 cancellations, 1.56 percent. Arrival delays sat at 823,345 flights, 21.35 percent. On-time share slipped to 76.14 percent from 76.67 percent a year earlier.
Refunds are already the loudest complaint line. DOT’s April 2026 Air Travel Consumer Report logged 7,278 complaint cases. Refunds ranked first at 2,296. Flight schedule was second at 1,323. On August 1, 2025 the Department opened ACERS, the new Aviation Complaint, Enforcement, and Reporting System. The intake pipe exists. Most passengers never find it because the airline app offers a credit first.
A DOT Office of Inspector General audit published in 2025 noted that OACP took more than 139,000 refund complaints between 2020 and 2022, against 1,568 refund complaints in all of 2019. The Bureau assessed more than $155 million in civil penalties across 14 airlines for slow refunds, while still relying on carrier self-certification for the offsets. The enforcement story is not theoretical. The noticing job is still on the passenger.
Stop treating these as separate products
The X idea mill splits this into four micro names. One app reads a confirmation email. One flags EU261-style delay hours. One drafts a DOT complaint. One tracks unused travel credits that expire. Cute. Wrong cut.
The passenger does not wake up wanting a “consumer-protection copilot.” They wake up because the board flipped and the app is offering $150 in wallet credit against a $640 fare. The category is the same leakage pattern as unused SaaS seats and short-paid claims: money left, the file is a PDF in Gmail, and nobody owns the next click.
Greg Isenberg’s Duo list put a tow-truck intake and an on-site adjuster on opposite screens. Same primitive. The object in the hand is the proof. The other pane is the rule. Combine the itinerary-as-data exhaust with the delay-board photo and you have one checker, not two startups.
The wedge is a free checker. Not a platform.
Do not start with a travel profile. Start with the email they already have.
Paste the confirmation. Paste the delay SMS. Upload the photo of the gate screen. Thirty seconds later: cash owed, voucher trap, or not significant. If it is fine, you still captured a labeled itinerary. If it is not fine, you draft the carrier request or the DOT filing — and a person hits send.
That is the only honest offer. Pure upside for the passenger. You get paid when the cash posts, or on a cut of recovered ancillaries: bag fees for bags that never rode, seat fees on a cancelled segment, Wi-Fi that was not provided. Part 260 already names those ancillary refunds. Almost nobody files them because the receipt is three emails deep.
Do not let the model file the complaint. ACERS and carrier portals are irreversible enough. The model drafts. A human owns the send. Same rule as a customs protest or a medical claim letter.
Why this is buildable now
Two years ago the input was slop. Airline PDFs, codeshare itineraries, and screenshots of a split board were a weekend of data entry. Multimodal models can pull a PNR, a flight number, and a new departure time off a photo. They still invent policy. They do not need to be trusted with the card. They need to be trusted with the first pass against a published rule: three hours domestic, different airport, cancelled and not accepted, ancillary not provided.
The other half of why now is the rule plus the cancellation bump. Automatic refunds are on the books. Cancellations in the first half of 2026 ran well above the same stretch of 2025. The voucher button is still the default UI. That gap is the company.
How the company actually compounds
The first dollar is the refund. That is not the business. The business is the labeled corpus.
After a few thousand pastes you know which carriers convert a three-hour delay into a travel credit at the highest rate. You know which codeshare legs drop the refund obligation into a foreign operator that the passenger never contracted with. You know which bag-fee SKUs never auto-refund even when the segment dies. That scoreboard is a B2B product for OTAs, TMCs, and card issuers. They already sit on the itinerary feed. They do not sit on the outcome map.
Consumer volume trains the classifier. Enterprise contracts pay for the map. Do not sell the map before cash has posted to real people. A dashboard of “possible passenger savings” is how this idea dies in a pitch deck.
What not to build
Do not build another trip organizer that wants calendar access on day one. You will lose to TripIt on the people who already care, and you will never reach the person staring at a red board in Terminal B.
Do not pretend a language model is a DOT lawyer. Part 260 has definitions. Significant change is not a vibe. The July 2026 discretion on renumbered flights is a real carve-out. Get that wrong and you train customers to ignore you.
Do not brand this as agentic travel ops. Brand the outcome. Cash that should have come back, before the voucher ate it.
A build order that will survive contact
Week 1–2: one checker. Itinerary in, verdict out. No account required to see the first answer.
Week 3–4: a carrier request and an ACERS draft with a human signer. Contingency fee only.
Month 2: add the second document in the same drawer — bag-fee receipt, seat-fee receipt, hotel that was booked because the inbound died.
Month 3: publish the first ugly internal scoreboard. Which carriers, which delay bands, which ancillary SKUs stall. That scoreboard is the seed of the B2B SKU.
If you cannot get a stranger to paste one confirmation email this week, you do not have a company. You have a thesis.
Why this is worth writing, and building
Most idea-mill posts describe a feature. This one describes a shift in who does the tedious work of noticing. The noticing used to require a travel agent, a weekend, and a willingness to sit on hold. It now requires a model that can read the page and a person who will sign the filing.
Recovery businesses endure because the customer has nothing to lose. Most software asks for a seat fee before it has proven a dollar. This one pays for itself on the first posted refund or it does not deserve a second conversation.
Someone will own the system of record for delays that should have been cash. The threads will keep proposing a new .ai name for each document type. Ignore the names. Check first. Keep the map.
Will Tygart — Tygart Media. This is the idea-mill series.
This morning, about 7:10 AM PDT on 14 September 2026, the knowledge cluster showed a fresh spike: roughly 3,222 requests in an hour, and six POST hits on wp-login.php. Same box. Same shape as the 11–13 September run. Slightly hotter on volume. Cooler on the login door.
That is the whole alert. It is not a breach report. It is not a reason to open the firewall. It is two numbers that most dashboards smash into one word — “attack” — and then the operator starts changing things they cannot undo cleanly.
Mixed spike. A mixed spike is a short window where total request volume jumps while a sensitive path such as wp-login.php only sees a handful of POSTs. The volume is usually crawlers, scanners, or cheap probes. The login count is the part that can become hostile. Treat them as two events until the logs prove they are one.
What does a 3,222 request-per-hour spike actually mean?
It means the box was busy. It does not mean someone is in the admin. On this stack, an hour in the low thousands is loud enough to page a human and too coarse to name a cause. AI crawlers, feed fetchers, uptime checks, and junk scanners all land in the same request counter. We already showed that GA4 misses crawler traffic and that server logs are the only honest desk for that layer in Server Log Analysis for AI Search.
The 11 September field note left this card open. That write-up recorded an earlier pulse on the same cluster at about 1:51 PT: roughly 2,487 requests per hour and nine wp-login POSTs. The instruction then was a read-only log pull and a one-paragraph verdict. No firewall change, no plugin change, no credential change without a named gate. That card is the parent of this morning. See The 1 MB Limit Ate the Clips.
Why are six wp-login POSTs the number that matters?
Because that path is the door. A GET to wp-login.php is usually a probe. A POST is a credential attempt. Six POSTs in an hour is not a brute-force campaign. A campaign that is actually trying passwords does not stop at six. It stacks POSTs until a rate limit, a WAF, or a 429 answers.
Six against 3,222 is the tell. Login is about two-tenths of one percent of the hour. If the spike were “someone hammering wp-login,” the login count would be the spike. Here the spike is everything else, and the door got a light knock.
Window
Requests / hour
wp-login POSTs
What it looks like so far
11 September 2026, ~1:51 PT (public card)
~2,487
9
Open patch. Verdict not written yet.
14 September 2026, ~7:10 AM PDT
~3,222
6
Same shape, hotter volume, fewer POSTs.
Those two rows are first-party. They come from the ops cards and this morning’s alert. They are not a full log dump. They are enough to stop the sentence “we are under attack” from shipping as fact.
How do you tell bot noise from a hostile login event?
You do not tell from a single request-per-hour number. You tell from five columns that have to sit on one page: top source networks, paths, methods, status codes, and whether any POST to an auth endpoint returned a success path instead of a fail, a 403, a 429, or a challenge.
If volume is high and wp-login.php / xmlrpc.php POSTs are near zero, start with crawler or scanner noise.
If POSTs to the login door climb while other paths stay flat, start with credential stuffing or a cheap brute-force kit.
If one network owns both the volume and the POSTs, treat that network as the subject of the verdict, not the whole internet.
If status codes are 200 on a login POST, do not celebrate. WordPress often returns 200 on a failed login because it re-renders the form. You still need the auth result, not the HTTP code alone.
If you cannot see whether rate limiting or the WAF fired, you do not have a close. You have a draft.
That list is the desk, not a product. It is the same discipline we use when we refuse to treat Bing AI citations as sessions in How to Read Bing Webmaster Tools AI Citations. Wrong unit, wrong decision.
What is the one-paragraph verdict from this morning’s numbers alone?
Provisional, read-only: this morning looks like bot noise with opportunistic login probes, not a concentrated hostile event. The volume rose from the mid-2,000s last week to the low-3,000s. The login door went from nine POSTs to six. That is the opposite of a campaign that is finding a seam. Nothing in the alert says a login reached a successful auth. Nothing in the alert says the WAF or a rate limit fired. Until those two facts are in the log extract, the box stays as-is.
What to do from this paragraph: pull the hour. Rank source networks, paths, methods, and status codes. Confirm whether any login POST crossed into an authenticated session. Write the close in one paragraph. Do not touch firewall, plugins, credentials, DNS, or WAF from the spike number alone.
Why does this belong on an AEO and GEO desk?
Because the same operators who publish for answer engines also run the origin those engines crawl. A spike that is actually GPTBot or a citation crawler is the retrieval layer working. A spike that is actually wp-login.php is the origin under cheap pressure. If you flatten both into “bots,” you will rate-limit the crawler you spent a year trying to attract. We mapped that split in The AI Crawler Hierarchy and in Google vs Bing vs OpenAI.
SEO still needs the URL up. AEO still needs a clean block a snippet can lift. GEO still needs a page a model will cite without inventing a second sentence. None of those layers survive an origin that treats every request burst as an incident and starts flipping controls. The cited-answer work on this site — Your Website Doesn’t Need More Traffic. It Needs to Be the Answer. — assumes the box that serves the sentence stays boring.
What we would not claim
That we have this morning’s full access log in this article. We have the alert counts. The path table and the auth result are the next pull, not this page.
That six POSTs means zero risk. It means the door was tried. It does not mean the door opened.
That 3,222 requests per hour is a universal threshold. It is the number on this box, this hour.
That hiding wp-login.php is the fix. Obscurity is not the close, and this post is not a plugin recommendation.
That any named source network belongs in a public URL. Publishing attacker addresses helps the next scanner more than it helps the reader.
What we would do again
Keep the two counts separate on the card. Request volume on the left. Auth-path POSTs on the right. Write the verdict in one paragraph before anyone is allowed to change a control. Leave the change list empty until the named gate says yes. Publish the method, not the address list.
The 11 September card said a spike is not automatically an attack and it is not automatically “leave it.” It is a log plus a verdict. This morning’s numbers did not close the log. They did close the panic sentence. The door was quiet. The weather was not.
FAQ
Is a WordPress request spike the same thing as a brute-force attack?
No. A request spike is total traffic in a window. A brute-force event is repeated credential POSTs against an auth path such as wp-login.php or xmlrpc.php. This morning’s hour had both a spike and six login POSTs. Those are adjacent facts, not proof they are the same campaign.
How many wp-login POSTs should trigger a change?
There is no public magic number that authorizes a firewall, plugin, credential, DNS, or WAF change on this stack. The trigger is a log extract that shows concentrated POSTs, a repeated source network, and either a successful auth or a clear miss by the existing limiters. Six POSTs in an hour does not clear that bar.
Can AI crawlers cause a 3,000-request hour?
Yes. On this network we have already logged hours where a single AI crawler family mapped tags, feeds, and endpoints at four-figure rates. That traffic belongs in the server log, not in GA4. Confirm the user-agent and the path list before you treat the hour as hostile.
Should you publish the source IP addresses from a spike?
No. A public post can carry the counts, the method, and the verdict. It should not carry a live target list. The addresses live in the private log pull.
Sources: Tygart Media ops alert, knowledge cluster, ~7:10 AM PDT, 14 September 2026 (about 3,222 requests/hour and 6 wp-login POSTs). Prior public card in The 1 MB Limit Ate the Clips (~2,487 requests/hour and 9 wp-login POSTs, ~1:51 PT). Method context: server log analysis for AI search, AI crawler hierarchy. Will Tygart, Tygart Media, 14 September 2026.
This is a live Monday morning snapshot of local storm-type events across the United States as of Monday, September 14, 2026. Overnight the organized wind corridor that ran the upper Ohio Valley into New York is down. No Storm Prediction Center watches are currently valid. The Day 1 Convective Outlook issued 0746 AM CDT holds a Slight Risk of severe thunderstorms across parts of eastern Nebraska into western and central Iowa this afternoon and evening. Large hail, severe gusts, and a few tornadoes all appear possible. The Weather Prediction Center overlays a Moderate Risk of excessive rainfall on central and southwestern Iowa, with a broader Slight Risk from eastern Nebraska through the Midwest and a separate Slight Risk over the Southwest monsoon corridor.
These are county- and ZIP-scale thunderstorms and flash-flood pulses, not a U.S. mainland hurricane landfall. Restoration exposure today is wind and hail on the Nebraska–Iowa Slight, interior water where Iowa cells train south of I-80 tonight, and leftover tree-and-roof work from Sunday evening in Ohio, Pennsylvania, West Virginia, and New York. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.
What is live this morning
SPC lists no current convective watches. The most recently issued watch was number 667 earlier in the week; Sunday’s Ohio Valley–Northeast slight-risk corridor produced local severe thunderstorm warnings and wind damage but did not carry an overnight watch into Monday morning.
The 1300 UTC Day 1 outlook (valid 1300Z Monday through 1200Z Tuesday) draws the Slight Risk from roughly Grand Island and Hastings east-northeast through Omaha and Lincoln into western and central Iowa, including the Des Moines metro on the eastern edge. A Marginal Risk wraps a wider ring from the Dakotas and Minnesota south through Kansas. Elevated convection is already ongoing this morning across the central Plains and mid Missouri Valley on a strong low-level jet. SPC expects that band to stay mostly sub-severe and weaken late morning, then a new surface-based corridor to fire along or just ahead of a cold front across eastern Nebraska by late afternoon.
WPC’s Day 1 Excessive Rainfall Outlook, updated 0733 UTC, is the louder product this morning: Moderate Risk over portions of central and southwestern Iowa, with locally 3 to 6 inches possible south of I-80 toward Des Moines and points southwest. A broad Slight Risk still covers much of the Midwest from eastern Nebraska through southern Minnesota and the Door Peninsula, plus a separate Slight over eastern Arizona, New Mexico, and southwestern Colorado.
Hotspot 1 — Eastern Nebraska into western and central Iowa
This is today’s organized severe desk. A mid-level shortwave and 50–70-plus kt mid-level jet move east-northeast across the northern Plains. Rich low-level moisture is forecast to stream north into eastern Nebraska and western Iowa after morning convection clears. SPC allows a narrow corridor of 2,000–3,000+ J/kg MLCAPE if surface temperatures reach the low to mid 80s by late afternoon. Initial storms should be supercellular enough for large hail. Mode is expected to transition quickly to clusters and line segments. A 40–50 kt nocturnal low-level jet supports ample storm-relative helicity this evening; a sustained surface-based supercell would conditionally be capable of a strong tornado. That is the official language, not a guarantee that one occurs.
Cities and counties to watch: Lincoln, Omaha, Council Bluffs, Sioux City, Des Moines, Ames, and the I-80 belt from Grand Island through western Iowa. Watch issuance, if it comes, is an afternoon product — not a morning one.
Restoration read: hail and wind first on the Nebraska side; water second once the same storms cluster over Iowa after dark. Stage tarps and generators before 4 p.m. local. If a warning includes both wind and heavy rain, treat the ZIP as a dual ticket by morning.
Hotspot 2 — Central and southwestern Iowa flood overlay
WPC introduced a small Moderate Risk for D1 in coordination with the Des Moines office. HREF blended mean QPF runs 3–5 inches over the area encompassing Des Moines and points south and southwest. Neighborhood probabilities for more than 3 inches are 60–80 percent in that pocket, with 25–30 percent for more than 5 inches. Three-hour flash-flood guidance exceedance sits 50–70 percent. The main concerns are urban footprints and low-water crossings south of I-80. Heavy rain is expected to linger into early Tuesday morning.
A broader Slight still covers eastern Nebraska into southern Minnesota. Isolated flash-flood concerns this morning ride the progressive elevated band; the more appreciable footprint is the evening and overnight wave.
Restoration read: this is tonight’s water ticket. Extraction and drying clocks start the same night water is inside. Do not wait for a river flood warning if streets and finished basements are already taking the 1-inch-per-hour cores.
Hotspot 3 — Sunday just-hit and Southwest scatter
Overnight LSRs from the 1200 UTC Sunday–Monday window show the Ohio Valley–Northeast slight-risk corridor verified as wind, not tornadoes. Preliminary reports include a roof ripped off a home and multiple trees down in Fox Township, Carroll County, Ohio; trees and wires across Lawrence, Butler, Crawford, McKean, and Clearfield counties in Pennsylvania; trees on structures and roads in Washington County, Ohio, and Wood County, West Virginia; and additional tree and wire damage in Onondaga, Oneida, Franklin, Fulton, and Saratoga counties in New York. Isolated 1.00-inch hail fell near Monarch and Raynesford, Montana, and 2 south of Sterling, Nebraska, after midnight. A 61 mph gust was measured near Patagonia, Arizona.
Today the Southwest stays a flood-and-outflow desk. WPC keeps a Slight Risk of excessive rainfall over eastern Arizona, much of New Mexico, and southwestern Colorado on monsoon-style cells, burn scars, and slot canyons. SPC does not carry 5 percent severe probabilities there, but isolated strong gusts and small to near-severe hail are possible where heating is strongest. Eastern North Carolina sits under a cold front with only a low-end isolated wind/hail mention.
Just hit
Sunday’s upper Ohio Valley–central New York Slight Risk is yesterday’s ticket: trees, wires, and isolated roof work from eastern Ohio through northwest Pennsylvania into central New York. Watch 667 from Saturday is long expired. There is no named tropical cyclone threatening U.S. land this morning. National Hurricane Center discussion shows no Atlantic tropical cyclones; Tropical Storm Norbert and a weakening eastern Pacific depression are well offshore and not a mainland or Hawaii landfall problem today.
Pulse table
Region
Main threats
SPC / NWS / WPC level
Status this morning
Eastern NE / western–central IA
Large hail, damaging wind, few tornadoes possible
SPC Slight (1300Z)
Afternoon–evening; no watch yet
SW / central Iowa south of I-80
Flash flood, 3–6″ local totals
WPC Moderate excessive rainfall
Evening into Tuesday morning
OH / PA / WV / NY from Sunday
Trees, wires, isolated roof damage
LSRs; watches expired
Aftermath
Eastern CO / western–northern KS
Isolated severe gusts, high-based cells
SPC Marginal
Afternoon scatter
AZ / NM / SW CO
Flash flood, strong outflow
WPC Slight
Afternoon–evening cells
Atlantic / Gulf vs. U.S. mainland
No landfalling tropical cyclone
NHC quiet on the mainland
Quiet
What this means for restoration teams
Eastern Nebraska this evening is hail and wind: roofs, siding, screens, and vehicles. Western and central Iowa is the dual ticket — the same storms that throw hail west of the Missouri River can train 3-plus inches of rain over Des Moines and counties southwest of I-80 after dark. A brief tornado, if one occurs, is a narrow swath. Staff it as a local damage survey, not a regional outbreak.
Sunday’s Ohio–Pennsylvania–New York wind is already on the books: tree-on-structure, service drops, and isolated roof peel. Photograph remaining damage in daylight if it is safe, then move crews toward the Nebraska–Iowa corridor rather than chasing last night’s counties unless a specific claim is already open.
What this is not
This is not a regional derecho and not a U.S. mainland hurricane landfall. The work today, if it verifies, will be scattered: a hail swath through an eastern Nebraska county, a flooded intersection south of I-80 in Iowa, leftover trees in Ohio or New York. That is the local-storm pattern this desk should staff.
Looking ahead
SPC Day 2 is a Marginal Risk as the same trough lifts toward the Upper Great Lakes. Day 3 currently carries no severe area. WPC language keeps heavy rain lingering into early Tuesday over the same Iowa footprint. Watch the afternoon Storm Tracker rather than assuming the 1300Z Slight is the last line of the day — a watch can still go up if the warm sector destabilizes as drawn.
Sources and how to verify
Primary sources: NOAA Storm Prediction Center 1300 UTC Day 1 Convective Outlook for Monday, September 14, 2026 (Gleason/Lyons); SPC current watch page (no watches valid as of 1010 UTC); SPC preliminary local storm reports for the 13/1200Z–14/1159Z window; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0733 UTC; National Hurricane Center Atlantic and East Pacific discussions this morning.
