Skip to main content

nColo Regional Provisioning

nColo provides Pro-tier users with routed public IPv4 prefixes. Unlike nSolo (which uses 1:1 NAT), nColo prefixes are pure Layer 3 routed — traffic flows directly to your router over WireGuard with no NAT translation.

This page describes how nColo prefixes are provisioned across Nekotopia's regional hub infrastructure.

Geographic Regions

Region Hubs Prefix Pool Origin Hub Status
AMER Ohio, Oregon, São Paulo 185.24.72.0/24 Ohio (us-east-2) Active
EMEA London, Frankfurt, Bahrain 185.65.116.0/24 London (eu-west-2) Active
APAC Singapore, Mumbai, Tokyo, Sydney 185.24.74.0/24 Singapore (ap-southeast-1) Active

All three prefix pools are BYOIP-provisioned in their respective AWS regions, advertised under AS213811 via BYOASN.

Hub-to-Region Mapping

AWS Region Hub Geo Region nColo Pool Role
us-east-2 Ohio AMER 185.24.72.0/24 Origin — owns the prefix pool
us-west-2 Oregon AMER 185.24.72.0/24 Delegated — routes via Ohio
sa-east-1 São Paulo AMER 185.24.72.0/24 Delegated — routes via Ohio
eu-west-2 London EMEA 185.65.116.0/24 Origin — owns the prefix pool
eu-central-1 Frankfurt EMEA 185.65.116.0/24 Delegated — routes via London
me-south-1 Bahrain EMEA 185.65.116.0/24 Delegated — routes via London
ap-southeast-1 Singapore APAC 185.24.74.0/24 Origin — owns the prefix pool
ap-south-1 Mumbai APAC 185.24.74.0/24 Delegated — routes via Singapore
ap-northeast-1 Tokyo APAC 185.24.74.0/24 Delegated — routes via Singapore
ap-southeast-2 Sydney APAC 185.24.74.0/24 Delegated — routes via Singapore

How It Works

Origin Hubs

Origin hubs (Ohio, London, Singapore) have the nColo infrastructure directly provisioned:

  • BYOIP prefix advertised from the local AWS region
  • MikroTik CHR with BGP peering to customers over WireGuard
  • Per-customer prefix filter (only accept the allocated prefix)
  • IGW gateway route table routing the prefix to the hub ENI

Delegated Hubs

Delegated hubs (Oregon, Frankfurt, etc.) do not have their own prefix pool. nColo traffic is policy-routed across the WireGuard mesh back to the origin hub for BYOIP egress. The customer still peers BGP with their local hub — the delegation is transparent.

Provisioning Flow

  1. User selects prefix size (/32, /31, /30, /29) in the dashboard
  2. System resolves user's hub to the correct regional origin hub
  3. Prefix allocated from NetBox IPAM under the regional pool
  4. Private ASN assigned from the region's ASN range
  5. MikroTik provisioned: WG allowed-address, BGP connection, prefix filter, QoS
  6. User receives BGP peering details and sample router configs

Hub Change Behaviour

Move Type Example What Happens
Same region Ohio → Oregon Prefix preserved. Deprovisioned from old hub, re-provisioned on new hub.
Cross region Ohio → London Prefix released (AMER → EMEA). User allocates a new prefix from EMEA pool.

nSolo (dedicated NAT IP) is always released on any hub change, as it is tied to the old hub's NAT infrastructure.

Prefix Pricing

Size IPs Price Per-IP
/32 1 $5/mo $5.00
/31 2 $9/mo $4.50
/30 4 $12/mo $3.00
/29 8 $20/mo $2.50

Pricing is the same across all regions. Self-service, honour-based (same model as bandwidth selection).

BGP Configuration

Each customer receives:

  • A private 4-byte ASN (e.g. 4200000001 for EMEA, 4200100001 for AMER, 4200200001 for APAC)
  • Hub peer ASN: AS64512
  • Hub peer IP: the WireGuard gateway of the local hub

The dashboard provides ready-to-paste configs for MikroTik RouterOS, FRRouting, and BIRD.

BYOIP Infrastructure

Region Prefix AWS Region IPAM Pool EC2 Pool ASN
EMEA 185.65.116.0/24 eu-west-2 ipam-pool-05345e5d2df4d7166 ipv4pool-ec2-0c0b4b0a21448be79 AS213811
AMER 185.24.72.0/24 us-east-2 ipam-pool-06905f53940df17e4 ipv4pool-ec2-01d3da50d8626f435 AS213811
APAC 185.24.74.0/24 ap-southeast-1 ipam-pool-08c5c1d00b22bd4f1 ipv4pool-ec2-044ee5c5992f681e0 AS213811

All prefixes are registered with RIPE NCC with appropriate geolocation (geoloc:) and geofeed entries. The geofeed CSV is served at https://www.nekotopia.io/geofeed.csv.

Reserve Capacity

The parent RIPE allocation 185.24.72.0/22 provides four /24 blocks:

Prefix Assignment Status
185.24.72.0/24 AMER (Ohio) Active
185.24.73.0/24 AMER expansion Reserved
185.24.74.0/24 APAC (Singapore) Active
185.24.75.0/24 APAC expansion Reserved
Back to top