Peering Information
gobler.net operates under a single Autonomous System Number. All prefixes advertised are originated by ASes listed in our AS-SET. Our primary IRR is RIPE.
| aut-num | AS48374 |
| as-set | AS-GOBLER |
You might find additional information at peeringdb.
For peering inqureries please contact peering at gobler.net
For operational issues please contact noc at gobler.net
Public Peering
Currently gobler.net exchange traffic at the following Internet exchange points.
| Exchange | IPv4 | IPv6 |
|---|---|---|
| Netnod Copenhagen | 212.237.192.233 | 2001:7f8:d:202::233 |
| Netnod Copenhagen | 212.237.193.233 | 2001:7f8:d:203::233 |
| NL-IX Copenhagen | 193.239.118.95 | 2001:7f8:13::a504:8374:1 |
Private Peering
We will consider private peering if, public peering is not possible and/or traffic volumes is high enough.
Peering Policy
We run an open policy and generally we will peer. We have a few restrictions and most networks will be able to comply.
- Network engineering wise, it have to make sense.
- The exchange of routes will be over BGPv4.
- Each party annouce the routes that are registered for the Autonomous Systems listed in the party's as-set.
- AS Numbers, AS Sets and routes shall be registered with a recognized IRR.
- Neither party will send traffic to destinations not announced by the other party through the other party's Internet Network.
- Neither party will establish a default route directed towards the other.
- The peering is based on good will and best effort. Neither party is liable to the other party for losses or damage from interruption of peering for any period of time.
- Both parties acknowledge that this peering agreement is not legally binding, nor is it intended to be.