Policy
Maintenance Policy
Liberty Security Services, LLC — AS21990
How we give notice of work that may affect traffic to or from 206.109.108.0/23, where notices appear, and how to be told without having to remember to look.
Notice periods
| Class | Notice | What it covers |
|---|---|---|
| Planned | 7 days | Scheduled work with a known window — software upgrades, hardware replacement, circuit or carrier changes, configuration work that risks a session |
| Emergency | Best effort, before the work where possible | Work that cannot wait 7 days without greater risk than doing it now — a security fix under active exploitation, a failing component, an upstream requiring immediate action |
| Unplanned | Notice after the fact | An outage. Nobody schedules these, and a policy that pretends otherwise is decoration. We post what happened and when it was resolved. |
Emergency work is genuinely best effort, and we would rather say that than publish a number we would break. If a router is being actively exploited, the fix goes in and the notice follows. What we commit to is that the notice exists either way — work that happened without a notice is the failure, not work that happened without seven days of it.
Changing or cancelling a notice
A changed window is a new notice, with a fresh 7 days — not an edit to the old one. Quietly moving a window is how somebody who read the original ends up surprised, and it is the reason this rule is written down rather than left to judgement.
Cancelling is different: a cancellation is posted against the existing notice, because there is no risk in learning late that something is not happening.
Where notices appear
| The status board | as21990.net/#status — current issues and scheduled work, in short form |
| Atom feed | as21990.net/maintenance.xml — the same notices, with full detail and UTC timestamps, in any feed reader |
| Customers affected by a specific piece of work are told directly. The board and the feed are the public record, not a substitute for that. |
Subscribing
Add https://as21990.net/maintenance.xml to any feed reader. There is no mailing list to join, no account to create, and nothing that requires giving us an address.
The feed is hosted off our own network, deliberately. This site does not run inside 206.109.108.0/23, so it survives an outage of the network it reports on. A status page that goes down with the thing it is meant to report on is worse than none, because its silence is indistinguishable from good news.
The same fact sets the limit: because it cannot see our network, it does not detect anything. Every entry is posted by a person. For live routing state, the four independent sources on our main page are the honest answer.
Timestamps
Notices carry both a local Eastern time and UTC. The feed uses RFC 3339 UTC throughout, because a maintenance window written in local time is the one that gets read wrong across a daylight-saving boundary.
What counts as affecting you
We post work that risks reachability of the address space we originate, or that will tear down a BGP session. We do not post routine work with no traffic risk — a feed padded with events that never affected anybody is a feed people stop reading, and then the one that mattered goes unread with it.
Questions about a notice
Email noc@as21990.net, quoting the window. Outside staffed hours that address reaches the engineer on call.