Up high. Out far.
Always on expedition.
AS218836, a small dual-stack network with open peering policy.
The short version
Why this network exists
AS218836 exists to learn. I wanted to understand BGP properly rather than read about it, and to see the whole of what running a network involves: the address space, the routing policy, the filtering, the peering, and keeping it all working. There is no grand plan behind it. It should grow a bit, and eventually run services of my own behind it, but that is an ambition rather than a roadmap. That said, it is run properly. RPKI validation on every session, an IRR prefix filter built from each peer’s AS-SET and rebuilt daily, and a configuration nobody edits by hand.
This page is for operators thinking about peering. Requests go through PeeringDB rather than email: you sign in, pick the network you speak for and an exchange we both sit on, and I approve it by hand. From there the session is generated from your PeeringDB record, and addresses and prefix limits are re-read every four hours, so if you renumber at an exchange there is nothing to tell me.
Synced from PeeringDB
Where we are
Internet exchanges
| Exchange | Our address | Port | Route servers |
|---|---|---|---|
| AMS-IX | 2001:7f8:1:0:a500:21:8836:1 80.249.213.46 | 1G | yes |
| Clue-IX | 2001:7f8:154::21:8836:1 185.0.26.2 | 1G | no |
| Frys-IX | 2001:7f8:10f::3:56d4:128 185.1.161.86 | 1G | yes |
Facilities
| Facility | City | Country |
|---|---|---|
| NorthC Amsterdam 1 | Amsterdam | NL |
Last synced 2026-10-22 12:42 UTC. Everything on this page comes from our PeeringDB record, which is the only place it is maintained.
Open policy
Peering with AS218836
The policy is open. If we meet at an exchange, we can peer. There is no ratio requirement, no minimum traffic level and no contract.
What we ask
- A PeeringDB record that is kept current. It is where we read your addresses and prefix counts, on every run.
- RPKI-valid announcements, and AS paths that pass ASPA. Both are validated on import: an invalid route or an invalid path is rejected, unknown is accepted.
- An AS-SET on your PeeringDB record, and IRR objects matching what you announce. We build a prefix list from it with bgpq4 and rebuild daily. A route outside your AS-SET is still accepted, but marked and deprefered, so an IRR-covered path to the same prefix wins.
- No default route. Transit is possible on request: ask the NOC.
- A NOC contact that answers.
Our details
| ASN | AS218836 |
|---|---|
| Prefixes | 2001:678:1308::/48 157.173.71.0/24 |
| AS-SET | RIPE::AS218836:AS-EXPED |
| Max prefixes v6 | 10 |
| Max prefixes v4 | 10 |
| Traffic | IPv6 and IPv4 |
| NOC | noc@expeditioner.network |
| PeeringDB | net/43477 |
Everything here is on our PeeringDB record too, so you can configure your side without waiting for us.
Communities
Every route we accept is tagged with large communities saying where it came from, and anything you send in the 218836:*:* namespace is stripped on import. Of the well-known communities we honour GRACEFUL_SHUTDOWN, BLACKHOLE, NO_EXPORT and NO_ADVERTISE. Downstreams get action communities on top: no-export, prepending, announce-only, local preference and targeted blackholing. The full list is on its own page.
Requests are made by signing in with PeeringDB, so we can confirm you speak for the network you are asking about. You do not need an account here.