Any peering is welcome. To make a peering request, just contact me via email: email@example.com (GPG is supported, 9AA2 8159 FCEB 3CD8 3BC2 1201 7E86 9146 6991 08C7).
- Extended message
- BFD session
- Implementation and updating of ROA policies (using rpki-client)
- No availability guarantee
- Email address or other contact method to contact
- Support for IPv6
- Latency under 500ms is mandatory
Desirable peering partner support (not mandatory):
- Extended message
- Latency under 40ms
- Implementation of BGP Communities
- Implementation of ROA checks and regular update of them
My servers are reachable via IPv6. Currently I am peering through GRE and SIT. But I am open for new solutions. My ASN for peering is 202952. My AS-SET is
We are able to provide transit. There are both some rules and restrictions.
- All transmitted content must be legal. (Germany area)
- It is forbidden to intentionally route large amounts of traffic over our AS if a better route is available.
- You are not allowed to set permanent static routes to our AS.
- Transit is offered only to non-commercial organizations or individuals.
- It is forbidden to forward traffic to us from networks that you are not allowed to use.
- There is no guarantee of availability or similar.
- By default, only 100 prefixes are accepted. If more prefixes are to be announced, this must be agreed upon beforehand.
- Route flapping may occur from our side, as our upstreams also pass route flapping to us.
The following tunnel types are supported: GRE, SIT, WireGuard, OpenVPN
However, I am also willing to try others: Just ask
This type is associated with more effort. Here transit is provided over several upstreams, which must be manually notified. The downstream is then connected to the following AS:
- All of Type 2
This type is offered to everyone and can be deployed immediately after a successful BGP session. The downstream is then connected to the following AS: