Overview
MinakiLabs operates AS396500 with ARIN direct allocations:
- IPv4: 23.187.152.0/24
- IPv6: 2602:F82D::/36
Both prefixes are RPKI-valid with route objects registered in ARIN's IRR.
We are not an ISP. We sell public IPv4 addressing and BGP transit delivered over tunnels to machines behind NAT or CGNAT.
Facility Presence
TunnelNet IP Hubs (anycast, 23.187.152.0/24)
| Hub | Provider | Location |
|-----|----------|----------|
| mono-1 | Vultr | Chicago, IL |
| ewr-1 | Vultr | Newark, NJ |
| mci-1 | iFog | Kansas City, MO (peered, pending filter) |
TunnelNet Transit Hubs
| Hub | Upstream | ASN | Location |
|-----|----------|-----|----------|
| — | Servperso | AS34872 | Düsseldorf, DE |
| — | HYEHOST | AS47272 | Ashburn, VA |
Peering Policy
Policy: Open
We peer openly at any shared facility or internet exchange. We do not require a contract or traffic commitment.
Requirements
- Valid ASN registered with an RIR
- Up-to-date PeeringDB record
- Prefixes covered by valid ROAs (RPKI)
- Route objects in an IRR database
What we filter
- Prefixes longer than /24 (IPv4) or /48 (IPv6)
- Prefixes not covered by a valid ROA
- Bogons, default routes, and our own prefixes
- AS paths containing private or reserved ASNs
Contact for peering
Email support@minakilabs.com with your ASN and preferred facility or exchange.
Route Filtering and Validation
All BGP sessions enforce:
- RPKI validation — RPKI-invalid routes are rejected
- IRR-based prefix filtering — import filters built from IRR route objects
- Max-prefix limits — sessions are torn down if the prefix count exceeds the agreed limit
Limitations
- Hub failover takes minutes, not seconds — WireGuard rekey dominates recovery time
- No published availability number — will be published once there is enough operational history to measure
- Transit is single-homed per customer today — no multi-hub announcement yet
- We are a small network. We do not overstate our scale.
Contact