Network parameters
Peering fabric
- Location
- Vinters Connect, Maidstone
- Topology
- Shared Layer 2
- MTU
- 1500 bytes
- IPv4 LAN
- 185.0.24.0/24
- IPv6 LAN
- 2001:7f8:aa::/64
Route servers
- ASN
- 218849
- Mode
- Transparent; original next hop preserved
- IPv4 peers
- 185.0.24.1
185.0.24.2 - IPv6 peers
- 2001:7f8:aa::1
2001:7f8:aa::2 - Route origination
- No prefixes originated
Technical addresses last verified 13 September 2026. Loading IXP Manager data.
Public network resources
Route server filtering
RPKI origin validation and IRR filtering both apply. The checks below run in order on routes received from members.
| Check | Policy |
|---|---|
| 01 Next hop | Must match the member’s peering LAN address. |
| 02 Bogon filtering | Reserved, private, documentation and peering LAN prefixes are rejected. |
| 03 Prefix length | IPv4: /8 to /24. IPv6: /12 to /48. |
| 04 AS path | The first ASN must match the member. Private or reserved ASNs and paths above the length limit are rejected. |
| 05 RPKI | INVALID routes are rejected. VALID and UNKNOWN routes proceed to IRR filtering. Data refreshes every 120 seconds. |
| 06 IRR as-set | Prefixes must be covered by the registered as-set. Filters refresh every 15 minutes. An empty update or a reduction exceeding 30% retains the previous filter for review. |
| 07 Maximum prefixes | Limits are agreed per member and address family. Contact the NOC to request changes. |
Technical support
For session faults, routing questions or prefix-limit changes, contact noc@kent.exchange. Include your ASN, peering addresses and a description of the issue.