Network
How tiemannite is built and how it routes. Everything below the policy comes straight from PeeringDB, RIPEstat and the routers themselves.
Routers
| Router | City | Facility | Role |
|---|---|---|---|
| rtr-ens1 | Enschede | InterDC | Transit and peering |
Exchanges
| Exchange | City | Address | Route servers | Port |
|---|---|---|---|---|
| ENS-IX | Enschede | 2001:7f8:160::21:8369:1 | Yes |
No IPv4 on any exchange.
From PeeringDB, October 29, 2026.
Facilities
No facilities in PeeringDB yet.
Upstreams
| Upstream | ASN | Router | Via |
|---|---|---|---|
| bgp.rodeo | AS202585 | rtr-ens1 |
Prefixes
| Prefix | Origin | RPKI |
|---|---|---|
| 2001:67c:2888::/48 IPv6 | AS218369 | Valid |
From RIPEstat, October 29, 2026.
Routing policy
What happens to a route that comes in
Every route passes through these filters in this order. The first filter that rejects it ends its journey.
- BogonsPrefixes from private, documentation and reserved space are dropped, and so are my own prefixes when they come back from outside.
- Prefix lengthIPv6 longer than /48 goes no further.
- RPKIInvalid is dropped, valid and unknown pass. The router validates on its own (Routinator) and filters again as soon as the ROAs change.
- IRROn bilateral peering sessions only prefixes covered by the peer's AS-SET get through. I build the list with bgpq4.
- Max prefixEvery session has a fixed limit, well above what the neighbour lists in PeeringDB. Above it the session restarts.
- LabelsCommunities with my AS number are removed. Then the route gets a label with its source.
- Accepted
What goes out
- Only my own prefixes. I carry transit for no one.
- Route collectors such as bgp.tools get the full table, with all paths. No traffic flows over those sessions, they are only there to look at.
AS-SET: AS218369:AS-TIEMANNITE
BGP communities
Large communities only (RFC 8092), because a 32-bit AS number does not fit in a standard community.
Source of a route
Added to every route as it comes in. Visible in the looking glass.
| Community | Meaning |
|---|---|
| 218369:1:1 | From tiemannite itself |
| 218369:1:2 | From a customer |
| 218369:1:3 | From a peer, bilateral or via a route server |
| 218369:1:4 | From a transit provider |
Actions
I do not have action communities (no-export, prepending) yet. Communities with my AS number that you send are removed. If you need one, send me an email.
Sessions
5 sessions on 1 router, 5 established.
rtr-ens1
| Peer | Name | Type | Where | Family | Status | Since | Routes in / out |
|---|---|---|---|---|---|---|---|
| AS202585 | bgp.rodeo | Upstream | IPv6 | Established | 2026-10-23 | 257155 / 1 | |
| AS202585 | bgp.rodeo | Upstream | IPv6 | Established | 2026-10-23 | 257155 / 1 | |
| AS215549 | ENS-IX route-server | Route server | ENS-IX | IPv6 | Established | 2026-10-23 | 48 / 1 |
| AS205079 | ziesel.network | Bilateral | ENS-IX | IPv6 | Established | 2026-10-23 | 3 / 1 |
| AS212232 | BGP.Tools Route Collector | Collector | IPv6 | Established | 2026-10-27 | 0 / 514362 |
Straight from the routers, October 29 at 03:09 AM UTC.