PUBLICLY LISTED↗
EVIX
Virtual Internet Exchange
Check PeeringDB for the current public peering LAN details.
Exchange details ↗ OPEN PEERING POLICY
SETTLEMENT-FREE PEERING POLICY.
AS218321 (CLOGGEDPIPE) welcomes responsible network operators, CDNs, research networks, and packet connoisseurs. We support public route-server and bilateral peering where technical connectivity permits.
POLICYOPEN
NETWORKAS218321
ROUTING VALIDATIONRPKI INVALID → REJECT*
TRAFFIC RATIONO FIXED REQUIREMENT
* Policy statement; prospective peers should confirm current filtering behavior and operational readiness with our NOC. All interconnections remain subject to technical feasibility.
01 / INTERCONNECTION
Where to Peer
Only confirmed, active interconnections should be used for live BGP provisioning. Statuses below are intentionally conservative.
REQUESTED↗
Piter-IX
Amsterdam
Connection requested; bilateral session details are not yet published.
Exchange details ↗UNDER DISCUSSION↗
Frys-IX
Netherlands
Interconnection under discussion; do not configure a session yet.
Exchange details ↗Session endpoint details: The remote IPv4/IPv6 addresses depend on the particular IXP LAN. We intentionally do not publish made-up peering IPs. Request verified coordinates before configuring a bilateral session.
02 / INTERCONNECTION PRINCIPLES
How We Peer
Zero transit bills between friends. Clean routing tables between everybody.
01
Public route-server peering
Exchange routes using IXP multilateral route servers when AS218321 and the requesting network are both participants and route-server policies permit it.
MULTILATERAL02
Bilateral BGP sessions
Direct IPv4/IPv6 BGP sessions on a mutually reachable IXP LAN. Provide your ASN, peering addresses, and preferred exchange to coordinate.
DIRECT IXP03
Private interconnects
Dedicated PNIs and cross-connects may be evaluated where both parties share a facility and have suitable capacity. Optics, costs, and handoff details are negotiated.
BY ARRANGEMENT03 / TECHNICAL REQUIREMENTS
The Plumbing Code
Production peering requires a little more than two routers agreeing to talk.
PROTOCOL
BGP & addressing
BGP-4 with multiprotocol IPv4/IPv6 unicast support and 4-octet ASN capability. Use independent AFI/SAFI sessions as supported by the exchange and platform.
SECURITY
RPKI Route Origin Validation
RPKI-invalid routes are not accepted under the stated policy. RPKI NotFound is not the same as Invalid; ROA publication is strongly encouraged. Confirm current enforcement with the NOC.
ROUTING
IRR and prefix registration
Maintain accurate route/route6 objects, origin ASNs, and a current AS-SET where applicable. Disclose your authoritative filtering source when requesting a session.
HYGIENE
Filtering and anti-spoofing
Follow BCP 38 / BCP 84. No unwanted default routes, reserved/bogon space, unauthorized prefixes, or inadvertent route leaks. Expect prefix filtering on both sides.
OPERATIONS
BFD and session stability
BFD is optional and enabled only by agreement. Unstable sessions or harmful announcements may be rate-limited, filtered, or suspended. Max-prefix thresholds are negotiated per session.
CONTACT
Responsive NOC
Maintain current PeeringDB and operational contacts. Escalate leaks, hijacks, and reachability incidents to [email protected].
04 / ROUTING DIRECTORY
IP Resource Directory
Resource inventory is not a live BGP RIB. More-specific IPv6 announcements may differ from aggregate allocations.
| RESOURCE | FAMILY | CAPACITY | NOTES | VALIDATION | |
|---|---|---|---|---|---|
| 169.40.33.0/24 | IPv4 | 256 addresses | IPv4 resource | Check live ↗ | |
| 2a0e:97c0:260::/44 | IPv6 | 16 × /48 | IPv6 allocation; individual /48s may be advertised | Check live ↗ | |
| 2a13:9500:1f6::/48 | IPv6 | 65,536 × /64 | IPv6 resource | Check live ↗ |
Verification: Route visibility, ROA validity, maximum length, and IRR entries must be checked against current authoritative data. No static “RPKI VALID” badge is shown because it can become stale.
05 / TRAFFIC ENGINEERING
BGP Large Communities
RFC 8092 format accommodates our four-octet ASN: 218321:function:parameter.
Design proposal — not an active service contract. The values below are a reserved namespace for planned policy implementation. Do not attach them to production advertisements expecting a particular action until the peering team confirms support on your specific session.
| LARGE COMMUNITY | ACTION | SCOPE | BEHAVIOR (WHEN ENABLED) |
|---|---|---|---|
| 218321:0:0 | Do not export | Export control | Keep eligible routes within AS218321. |
| 218321:666:0 | RTBH | Mitigation | Blackhole authorized /32 or /128 destinations only, subject to verification. |
| 218321:100:110 | Local preference 110 | Eligible peers | Request elevated preference where the peer-specific policy permits it. |
| 218321:100:100 | Local preference 100 | Eligible peers | Request the standard preference where supported. |
| 218321:100:90 | Local preference 90 | Eligible peers | Request lower preference for a backup path. |
| 218321:1001:0 | Prepend 1× | Export policy | Proposed single additional AS218321 prepend on eligible exports. |
| 218321:1002:0 | Prepend 2× | Export policy | Proposed two additional prepends. |
| 218321:1003:0 | Prepend 3× | Export policy | Proposed three additional prepends. |
| 218321:1000:0 | Learned from transit | Internal informational | Proposed classification assigned by AS218321. |
| 218321:2000:0 | Learned from IXP | Internal informational | Proposed classification assigned by AS218321. |
| 218321:3000:0 | Learned from PNI | Internal informational | Proposed classification assigned by AS218321. |
Community requests are always constrained by authorization, prefix filters, route ownership, and per-peer agreements. RTBH is never an unrestricted third-party blackhole API.
06 / OPERATOR TOOLKIT
BGP Config & Request Generator
Generate a conservative starting point. The config is not a replacement for your platform's route policies or a live peering agreement.
Safety defaults: No placeholder IPs are silently used. Nothing is generated until both local and remote addresses are supplied. Exports default to deny-all until you explicitly add owned prefixes. Validate against your router version before deployment.
# Complete the required session details above.
For IOS-XR, Junos and RouterOS the generator emits conservative policy skeletons; adjust to your operating-system release and existing route origination rules. A BGP session establishing does not prove that intended routes are correctly imported or exported.
07 / NETWORK PROFILE
Coordinates & Contacts
Useful identifiers for peering coordination and routing incidents.
Autonomous System
- ASN
- AS218321 ↗
- AS Name
- CLOGGEDPIPE
- Network
- Clogged Pipe Network
- Operator
- Dekkapok LLC · Dekkapok Engineering
- Peering policy
- Open, subject to mutual connectivity
- AS-SET
- Confirm authoritative object with NOC
- Prefix limits
- Negotiated per session
- PeeringDB
- peeringdb.com/asn/218321 ↗
Operations directory
For peering requests, cross-connect planning, and strange packets exploring your autonomous system.
- Peering
- [email protected]
- Abuse
- [email protected]
- Routing details
- bgp.tools ↗
- Looking glass
- Network console ↗
Contact addresses are published here for coordination; mailbox coverage and response times are not guaranteed by this page.
08 / NONBINDING PACKET PHILOSOPHY
The Unwritten Peering By-laws
Humor only. Not part of our technical requirements, SLA, or peering agreement.
The Presumption of DNS
In the event of packet loss, everyone is entitled to blame DNS for 15 minutes before checking the BGP neighbor state.
Scenic Detour Rights
Packets may contemplate the philosophical implications of their AS_PATH. Actual routing remains governed by production policy.
MTU Philosophical Harmony
Jumbo frames may receive a stern lecture from the network engineer. PMTUD remains strongly encouraged.
No Physical Plumber Liability
We do not repair kitchen sinks or clogged drains. We only congest digital pipes, and ideally not on purpose.
LET'S CONNECT BGP SESSIONS
Ready to peer with AS218321?
We've got congestion to share.
Send us your ASN, preferred exchange, and contact details. We'll coordinate verified session endpoints.