AS211398

 Peering

Peering

Peering Policy

Open

You must have a public RIR assigned ASN.

You must have your own public IPv4/IPv6 prefix(es) with LOA or RPKI/IRR

You must connect via IXP or Tunnel

You must have a 8x5 NOC contact

FAQ Q: Why is the RPKI/IRR policy strict

FAQ A: This policy is implemented, To protect AS211398 against networks hijacking IP space and/or announcing unassigned RIPE IP space.

FAQ Q: I can't get a ROA for my prefix(es), can i still peer?

FAQ A: Yes, if you can provide the correct LOA of your prefix(es)

Due to security reasons, the RPKI/IRR Policy goes as following

RPKI Description Action
VALID ✔ ROA / AS Match Accept ✔
UNKNOWN ⍰ No ROA Reject  ❌
INVALID ✔ ROA / AS Mismatch Reject  ❌
IRR Description Action
VALID ✔ IRR / AS Match Accept ✔
UNKNOWN ⍰ No IRR Reject  ❌
INVALID ✔ IRR / AS Mismatch Reject  ❌

Transit Policy

Selective

You must follow the same rules as peers (above)

You must be a non-profit or personal network

You agree that a Fair Use Policy applies

Request will be reviewed on case-by-case basis

And again please note that this request process is very selective on a case-by-case basis

You agree with our prohibited services policy:

Service Description Allowed
TOR Anything TOR related NO  ❌
VPN Public VPN's NO  ❌
Torrents Anything torrent related NO  ❌
Unlawfull  Anything unlawful NO  ❌

Request peering or transit

Send peering requests noc@as211398.net

Or request via the form below

Peering request

Official ASN Org. name
Public RIR assigned ASN
ex. "Personal ASN", "Hosting Business ASN", ..
ex. "Webhosting", "VPN", "WISP"
Connect via IX, Tunnel, VLAN
For IX: IX IP, ....
Format: (ex. +1 (725) XX...)
Format: (ex. +1 (725) XX...)
RPKI and IRR: All VALID RPKI prefixes will be accepted, INVALID or UNKNOWN prefixes will be rejected.
LOA:  Provide your LOA('s) of your prefixes for manual filtering.
Choose files