Already have an account? Sign in instead.
You stay signed in for 30 days on this browser.
Continue with Google Continue with MicrosoftNo account yet? Create a free one.
We sent a six-digit code.
It expires in ten minutes, works once, and only in this browser. Five wrong tries void it. Send another code.
Your account is live and the Cloudflare checks are off for this browser.
Alert repetition
An alert originator may “repeat” an alert by releasing the alert anew—i.e., re-originating the alert—at least one minute subsequent to the time the message was initially released by the originator, as reflected in the repeat alert's JJJHHMM header code. Because alerts take time to activate across the EAS alert distribution chain, alert originators should consider an interval between the original and re-originated alert that is long enough to account for this process. If the re-originated alert is intended to reflect a valid time period consistent with the original, the valid time period code (the +TTTT header code identified in § 11.31(c)) set for the re-originated alert should be adjusted to account for the elapsed time between the original and re-originated alerts. Alert originators should be aware that repeating alerts routinely may cause alert fatigue among the public.
Syfert holds no separate history line for this section. Where this code prints a source or history note, it appears with the text, usually at the end.
Edition shown: eCFR text as of Sept. 29, 2026. Syfert holds no earlier or later version of this section.