asn.dev

Internet exchange

British Virgin Islands Internet Exchange Point

active Road Town, British Virgin Islands EIS

Recorded members 26 addresses on file
Connected ports 8 across all participants
Peak traffic 354 bps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Road Town, British Virgin Islands
Region
Latin America
Airport code
EIS
Status
Active
PCH record updated
2026-08-08

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
206.71.15.0/24IPv4Active8
2001:504:93::/64IPv6Active8

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

26 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS42WoodyNet, Inc.206.71.15.4Open
AS42WoodyNet, Inc.2001:504:93:0:206:71:15:4Open
AS3856Packet Clearing House, Inc.2001:504:93:0:206:71:15:5Open
AS3856Packet Clearing House, Inc.206.71.15.5Open
AS11139Cable & Wireless Dominica2001:504:93:0:206:71:15:7Selective
AS11139Cable & Wireless Dominica206.71.15.11Selective
AS11139Cable & Wireless Dominica2001:504:93:0:206:71:15:11Selective
AS11139Cable & Wireless Dominica206.71.15.7Selective
AS60890CentralNic Ltd2001:504:93:0:206:71:15:16No
AS60890CentralNic Ltd206.71.15.16No
AS199330CentralNic Ltd206.71.15.15Closed
AS199330CentralNic Ltd2001:504:93:0:206:71:15:15Closed
AS396357Digicel BVI Limited206.71.15.8Open
AS396357Digicel BVI Limited2001:504:93:0:206:71:15:8Open
AS14694Telecommunications Regulatory Commission2001:504:93:0:206:71:15:254Open
AS14694Telecommunications Regulatory Commission206.71.15.10Open
AS14694Telecommunications Regulatory Commission206.71.15.254Open
AS14694Telecommunications Regulatory Commission2001:504:93:0:206:71:15:10Open
AS22069CCT Global Communications2001:504:93:0:206:71:15:6Selective
AS22069CCT Global Communications206.71.15.6Selective
AS401400MCNET-SOLUTIONS206.71.15.40Open
AS401400MCNET-SOLUTIONS2001:504:93::a5:401:400Open
AS393430TELECOM REGULATORY COMMISSION206.71.15.252Open
AS393430TELECOM REGULATORY COMMISSION2001:504:93:0:206:71:15:251Open
AS393430TELECOM REGULATORY COMMISSION2001:504:93:0:206:71:15:252Open
AS393430TELECOM REGULATORY COMMISSION206.71.15.251Open

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.