We offer Transit-Sessions free of charge on Dedicated Servers and Housing/Colocation.
For VPS, there is a 20€ BGP-Setup fee.
For IPv4, 5€ monthly for the /29 Transfernet may be charged, IPv6 is free.
We can push a fulltable and/or default route.
On Setup, you get a Transfernet and 4 BGP-Sessions per Protocol (for 2 customer routers to each 2 Realtox-Media core routers). Usually a /64 (IPv6) or /29 (IPv4).
Sessions are per default bfd-enabled unless otherwise requested.
You can view you bgp session status, all connection information (IPs, ASNs, Session parameters like bfd,multihop) and current filter status in the Network panel under "BGP-Session Management".
We only allow rpki valid/unknown + irr valid prefixes.
Unless otherwise specified, we filter based on your ASN's allowed Prefixes. If you wish, we can also do AS-SET based Filtering if you want downstream-support. For this, please maintain a clean AS-SET with your ASN and Downstreams in it. No upstreams or huge other AS-SETs or unrelated ASNs/AS-SETs.
We automatically apply prefix-limits that are set in the PeeringDB-Entry of your ASN if pressent, else it defaults to 10.
We reload our filters daily, from experience most transit providers don't take too long to apply them. Routes are usually with high visability in the DFZ over at least 2-3 upstreams within <24 hours. Else, feel free to write us.
Below a list of common bgp (large-)communities. If you require something more fine-tuned, feel free to reach out.
Routes send by us carry on or more of the following communities.
| Community | Description |
|---|---|
207252:0:1 |
Learned via Transit |
207252:0:[AS] |
Learned from specific Transit ASN* |
207252:1:1 |
Learned from Customers/Downstreams |
207252:1:2 |
... in Düsseldorf |
207252:1:3 |
... in Frankfurt |
207252:2:1 |
Learned via IXP/Public Peering |
207252:3:1 |
Learned via PNI/Private Peering |
207252:10:1 |
Originating in Düsseldorf |
207252:10:2 |
Originating in Frankfurt |
We accept the following communities from customers
| Community | le | Description |
|---|---|---|
207252:100:1 |
IRR** | Do not announce to transit |
207252:100:[AS] |
IRR** | Do not announce to specific Transit ASN* |
207252:104:[AS] **** |
IRR** | Do not send traffic engineering communities to specific Transit ASN* |
207252:11[n]:[AS] |
IRR** | Prepend n times () to specific Transit ASN* |
207252:201:1 |
IRR** | Do not announce to IXP/Public Peering |
207252:202:1 |
IRR** | Do not announce to PNI/Private Peering |
207252:300::1 |
IRR** | permanent DDoS-Protection, Disables all other Transit |
207252:300::2 |
32 | permanent SmartMitigate for specific IP/Prefix*** |
207252:207252:10 |
IRR** | Drop route |
207252:207252:666 |
32 | Blackhole, maps to peer-specific communities |
Each route that gets pushed to transit providers is assigned into one "group". First come, first serve. Other communities get ignored.
1: 207252:100:1, 207252:100:[AS] ..do not announce
2: 207252:300::1 ..ddos mitigation only
3: 207252:104:[AS] ..skip traffic engineering
4: 207252:11[n]:[AS] ..prependings
5: remaining irr+rpki valids
* either 203446=Smartnet,24961=myLoc,3214=xtom,50629=lwlcom
** denotates the max. Length that is IRR+RPKI valid. Must be le24.
*** only works in combination with 207252:300::1
**** blocks prepends, in-peer-network advertisment limits/region limitations etc that are per default set by us. Most of them have good reasons to be present (e.g. congestion on peer's network, bad routes, etc). Use only when knowing what you are doing with caution and best consult us before using.