ARIN region · North America
AS21990
Liberty Security Services, LLC
AS21990 is the autonomous system operated by Liberty Security Services, LLC for its own network infrastructure and customer services. This page is the authoritative public reference for our address space, routing policy, and peering requests. We maintain an open peering policy and welcome settlement-free interconnection under a signed mutual peering agreement, subject to the interconnection constraints set out below.
- ASN
- AS21990
- Prefixes
- 1 · /23
- RPKI
- Signed & valid
- Peering policy
- Open
- Agreement
- Required
Registry record
Who we are, on the record
Every field below is verifiable in a public registry. Links go straight to the authoritative source so you never have to take our word for it.
- ASN
- AS21990
- ASN name
- LIBERTYSECURITY-1
- Legal entity
- Liberty Security Services, LLC
- ARIN Org ID
- LSSL-7
- RIR
- ARIN — American Registry for Internet Numbers
- ASN registered
- 2025-10-27
- PeeringDB
- peeringdb.com/net/40787
- ARIN Whois / RDAP
- search.arin.net/rdap/?query=AS21990
Address space
Prefixes we originate
If you see a prefix originated by AS21990 that is not on this list, it is not ours — please report it to our NOC.
| Prefix | Allocation | Addresses | RPKI ROA | IRR | Registered |
|---|---|---|---|---|---|
| 206.109.108.0/23 | Direct allocation · ARIN | 512 | Valid · maxLength 23 | ARIN, RADB | 2025-12-03 |
Routing policy & security
How we route, and how we keep it clean
AS21990 follows current routing-security norms. Our commitments below are the ones peers and upstreams are entitled to hold us to.
RPKI
All prefixes we originate are covered by a Route Origin Authorization in the ARIN trust anchor. We drop RPKI-invalid routes received from peers and customers.
ROA published
IRR objects
Route objects for our space are registered in ARIN and RADB. Peers may build filters from either.
Filtering
- Prefixes shorter than /8 or longer than /24 are rejected
- Bogons and unallocated space are rejected in both directions
- Max-prefix limits applied on every eBGP session
- We do not accept or propagate a default route from peers
Session parameters
- MD5 authentication available on request
- BFD available on request
- No route servers required — direct sessions welcome
Peering
How to peer with AS21990
AS21990 reaches the internet through transit today, and that meets our current needs. Our peering policy is open — no minimum traffic volume, no minimum number of shared locations, no ratio requirement — and we ask for a signed mutual agreement. We expect to take colocation space in future; until we do there is no cross-connect to order, so read the interconnection note below before sending a request.
- General policy
- Open
- Peering agreement
- Required — mutual bilateral agreement, signed before turn-up
- Multiple locations
- Not required
- Ratio requirement
- None
- Minimum traffic
- None
- Traffic levels
- 100–1000 Mbps peak
- Geographic scope
- Hudson Valley, NY Capital Region, and NY metro
- Edge location
- Lake Katrine, NY — Ulster County, Hudson Valley
- Exchange points
- None at present
- Carrier-neutral colo
- None at present — see Interconnection below
-
Check our PeeringDB record
Confirm we share a facility or exchange point. Our record is peeringdb.com/net/40787 and is kept current.
-
Send a peering request
Email
peering@as21990.netwith your ASN, PeeringDB link, where you propose to interconnect, your peering addresses, and expected prefix counts. -
Sign the peering agreement
We send our standard mutual peering agreement. It is short, settlement-free, and covers notice periods, traffic expectations, and abuse handling — it does not create a payment obligation for either side.
-
We configure and confirm
We build the session with max-prefix limits derived from your PeeringDB record and filters built from your IRR AS-SET, then send you our side of the details.
-
Turn up and verify
Both sides confirm the session is established and prefixes are exchanged as expected. Ongoing changes go through the NOC address below.
Peering agreement
We require a signed mutual peering agreement before any session is turned up. It is settlement-free and mutual — the point is a written record of notice periods, abuse escalation, and what each side may expect.
What to send us
- Your ASN and PeeringDB URL
- IRR AS-SET we should filter on
- Where you propose to interconnect
- Peering addresses
- Expected prefix counts and max-prefix values
- NOC contact for the session
Interconnection
Our edge routers sit in our own facility in Lake Katrine, New York. We reach the internet through transit and are not present in a carrier-neutral colocation building or on an exchange fabric today, so there is nowhere to order a cross-connect to us.
Colocation presence is planned. Until then, interconnection is by private arrangement over a dedicated circuit — ask us early and we will tell you honestly whether it is workable.
Upstream transit
AS21990 reaches the rest of the internet through these networks. This is our production path today, not an interconnection option.
| ASN | Network | Relationship | Verified |
|---|---|---|---|
| AS701 | Verizon Business (UUNET) | Upstream transit | 2026-08 |
| AS32723 | Archtop Fiber | Upstream transit | 2026-08 |
Contact
Reaching the right desk
Role addresses are monitored during business hours unless noted. For anything affecting live traffic, use the NOC address.
| Purpose | Address | Hours | Status |
|---|---|---|---|
| Network operations | noc@as21990.net | 24 × 7 | Live |
| Peering requests | peering@as21990.net | Business hours | Live |
| Abuse reports | abuse@as21990.net | Business hours | Live |
| General & customer service | Customerservice@LSSASAP.com | Business hours | Live |
| Telephone | +1 845-418-3577 ext. 4 | Business hours | Live |
All role addresses above are live. They should also be entered as points of contact in ARIN and in the PeeringDB record, so automated tooling and other operators reach the right desk without having to read this page first.