Network · data from 2026-11-12

AS8014 Bahamas Telecommunications Company, LTD.

Registry name: BATELNET - Bahamas Telecommunications Corporation, BS · PeeringDB

24IPv4 routes 70.8% RPKI valid · 83.3% with a route object

0IPv6 routes

1RPKI invalid 0 origin · 1 maxLength

6No ROA 4 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

3Route objects not announced registered with origin AS8014, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS8014, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


204.236.71.0/24	Invalid: maxLength	Nonecovered by 204.236.64.0/21	21 3%low visibility	12
199.38.198.0/24	No ROA	Nonecovered by 199.38.198.0/23	671 100%	67
199.38.199.0/24	No ROA	Nonecovered by 199.38.198.0/23	671 100%	67
65.198.208.0/21	No ROA	Other IRR onlyRADB	673 100%	67
69.79.70.0/23	No ROA	Other IRR onlyRADB	673 100%	67
199.38.198.0/23	No ROA	Other IRR onlyRADB	673 100%	67
72.51.75.0/24	No ROA	Other IRR onlyRADB	672 100%	67
108.60.227.0/24	Valid	Nonecovered by 108.60.224.0/19	673 100%	67
63.245.112.0/20	Valid	Other IRR onlyRADB	673 100%	67
69.79.28.0/24	Valid	Other IRR onlyRADB	673 100%	67
104.166.32.0/20	Valid	Other IRR onlyRADB	673 100%	67
108.60.224.0/19	Valid	Other IRR onlyRADB	673 100%	67
204.236.64.0/21	Valid	Other IRR onlyRADB	673 100%	67
204.236.72.0/22	Valid	Other IRR onlyRADB	673 100%	67
204.236.76.0/22	Valid	Other IRR onlyRADB	673 100%	67
204.236.80.0/21	Valid	Other IRR onlyRADB	673 100%	67
204.236.88.0/21	Valid	Other IRR onlyRADB	673 100%	67
204.236.96.0/21	Valid	Other IRR onlyRADB	673 100%	67
204.236.104.0/21	Valid	Other IRR onlyRADB	673 100%	67
204.236.112.0/21	Valid	Other IRR onlyRADB	673 100%	67
204.236.120.0/21	Valid	Other IRR onlyRADB	673 100%	67
206.48.0.0/22	Valid	Other IRR onlyRADB	673 100%	67
216.137.0.0/21	Valid	Other IRR onlyNTTCOM	673 100%	67
216.137.8.0/21	Valid	Other IRR onlyNTTCOM	673 100%	67

204.236.71.0/24

Invalid: maxLength

Nonecovered by 204.236.64.0/21

21 3%low visibility

199.38.198.0/24

No ROA

Nonecovered by 199.38.198.0/23

671 100%

199.38.199.0/24

No ROA

Nonecovered by 199.38.198.0/23

671 100%

65.198.208.0/21

No ROA

Other IRR onlyRADB

673 100%

69.79.70.0/23

No ROA

Other IRR onlyRADB

673 100%

199.38.198.0/23

No ROA

Other IRR onlyRADB

673 100%

72.51.75.0/24

No ROA

Other IRR onlyRADB

672 100%

108.60.227.0/24

Valid

Nonecovered by 108.60.224.0/19

673 100%

63.245.112.0/20

Valid

Other IRR onlyRADB

673 100%

69.79.28.0/24

Valid

Other IRR onlyRADB

673 100%

104.166.32.0/20

Valid

Other IRR onlyRADB

673 100%

108.60.224.0/19

Valid

Other IRR onlyRADB

673 100%

204.236.64.0/21

Valid

Other IRR onlyRADB

673 100%

204.236.72.0/22

Valid

Other IRR onlyRADB

673 100%

204.236.76.0/22

Valid

Other IRR onlyRADB

673 100%

204.236.80.0/21

Valid

Other IRR onlyRADB

673 100%

204.236.88.0/21

Valid

Other IRR onlyRADB

673 100%

204.236.96.0/21

Valid

Other IRR onlyRADB

673 100%

204.236.104.0/21

Valid

Other IRR onlyRADB

673 100%

204.236.112.0/21

Valid

Other IRR onlyRADB

673 100%

204.236.120.0/21

Valid

Other IRR onlyRADB

673 100%

206.48.0.0/22

Valid

Other IRR onlyRADB

673 100%

216.137.0.0/21

Valid

Other IRR onlyNTTCOM

673 100%

216.137.8.0/21

Valid

Other IRR onlyNTTCOM

673 100%

AS-SET

AS8014's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 34 are in fix.csv.

ROA: maxLength1
ROA: none6
Route object: none4
Route object: RIR20
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	204.236.71.0/24	ROA 204.236.64.0/21 AS8014 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 204.236.71.0/24.	21 of 673
Route object: none	204.236.71.0/24	No route object for it. A route object for 204.236.64.0/21 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.	21 of 673
ROA: none	199.38.198.0/24	No ROA covers it. Add a ROA for AS8014, maxLength 24.	671 of 673
Route object: none	199.38.198.0/24	No route object for it. A route object for 199.38.198.0/23 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.	671 of 673
ROA: none	199.38.199.0/24	No ROA covers it. Add a ROA for AS8014, maxLength 24.	671 of 673
Route object: none	199.38.199.0/24	No route object for it. A route object for 199.38.198.0/23 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.	671 of 673
ROA: none	65.198.208.0/21	No ROA covers it. Add a ROA for AS8014, maxLength 21.	673 of 673
Route object: RIR	65.198.208.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	69.79.70.0/23	No ROA covers it. Add a ROA for AS8014, maxLength 23.	673 of 673
Route object: RIR	69.79.70.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	199.38.198.0/23	No ROA covers it. Add a ROA for AS8014, maxLength 23.	673 of 673
Route object: RIR	199.38.198.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	72.51.75.0/24	No ROA covers it. Add a ROA for AS8014, maxLength 24.	672 of 673
Route object: RIR	72.51.75.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: none	108.60.227.0/24	No route object for it. A route object for 108.60.224.0/19 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.	673 of 673
Route object: RIR	63.245.112.0/20	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	69.79.28.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	104.166.32.0/20	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	108.60.224.0/19	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.64.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.72.0/22	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.76.0/22	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.80.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.88.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.96.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.104.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.112.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	204.236.120.0/21	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	206.48.0.0/22	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	216.137.0.0/21	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673
Route object: RIR	216.137.8.0/21	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

204.236.71.0/24

ROA 204.236.64.0/21 AS8014 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 204.236.71.0/24.

21 of 673

Route object: none

204.236.71.0/24

No route object for it. A route object for 204.236.64.0/21 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.

21 of 673

ROA: none

199.38.198.0/24

No ROA covers it. Add a ROA for AS8014, maxLength 24.

671 of 673

Route object: none

199.38.198.0/24

No route object for it. A route object for 199.38.198.0/23 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.

671 of 673

ROA: none

199.38.199.0/24

No ROA covers it. Add a ROA for AS8014, maxLength 24.

671 of 673

Route object: none

199.38.199.0/24

671 of 673

ROA: none

65.198.208.0/21

No ROA covers it. Add a ROA for AS8014, maxLength 21.

673 of 673

Route object: RIR

65.198.208.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

69.79.70.0/23

No ROA covers it. Add a ROA for AS8014, maxLength 23.

673 of 673

Route object: RIR

69.79.70.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

199.38.198.0/23

No ROA covers it. Add a ROA for AS8014, maxLength 23.

673 of 673

Route object: RIR

199.38.198.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

72.51.75.0/24

No ROA covers it. Add a ROA for AS8014, maxLength 24.

672 of 673

Route object: RIR

72.51.75.0/24

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route object: none

108.60.227.0/24

No route object for it. A route object for 108.60.224.0/19 with origin AS8014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8014 in the RIR database for the space.

673 of 673

Route object: RIR

63.245.112.0/20

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

69.79.28.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

104.166.32.0/20

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

108.60.224.0/19

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.64.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.72.0/22

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.76.0/22

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.80.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.88.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.96.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.104.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.112.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

204.236.120.0/21

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

206.48.0.0/22

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

216.137.0.0/21

Route object only in NTTCOM. Add it in the RIR database for the space.

673 of 673

Route object: RIR

216.137.8.0/21

Route object only in NTTCOM. Add it in the RIR database for the space.

673 of 673

Route objects not announced

Route objects with origin AS8014 whose prefix no peer sees AS8014 announce. Many are kept on purpose (backup routes, space announced only in some places).


190.102.64.0/19	RADB	No ROA
206.48.0.0/23	RADB	Valid
206.48.2.0/23	RADB	Valid

190.102.64.0/19

RADB

No ROA

206.48.0.0/23

RADB

Valid

206.48.2.0/23

RADB

Valid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.