bgpreport

Network · data from 2026-11-12

AS16413 TELEBERMUDA - Telebermuda International Limited

Registry name: TELEBERMUDA - Telebermuda International Limited, BM · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
2No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS16413, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16413, 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.

38.69.208.0/21 Invalid: origin Other origin only 3 0%low visibility 3
76.8.32.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
206.53.176.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67

AS-SET

AS16413 isn't in PeeringDB, where networks name their 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 21 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: origin38.69.208.0/21ROAs covering it name AS53863, not AS16413. If AS16413 should announce it, add a ROA for AS16413.3 of 673
Route object: none38.69.208.0/21Route objects for it name AS53863. Add a route object with origin AS16413 in the RIR database for the space.3 of 673
ROA: none76.8.32.0/20No ROA covers it. Add a ROA for AS16413, maxLength 20.673 of 673
Route object: RIR76.8.32.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.53.176.0/20No ROA covers it. Add a ROA for AS16413, maxLength 20.673 of 673
Route object: RIR206.53.176.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

64.74.241.0/24RADBNo ROA
206.53.177.0/24RADBNo ROA
206.53.178.0/24RADBNo ROA
206.53.179.0/24RADBNo ROA
206.53.180.0/24RADBNo ROA
206.53.181.0/24RADBNo ROA
206.53.183.0/24RADBNo ROA
206.53.184.0/24RADBNo ROA
206.53.185.0/24RADBNo ROA
206.53.186.0/24RADBNo ROA
206.53.187.0/24RADBNo ROA
206.53.188.0/24RADBNo ROA
206.53.189.0/24RADBNo ROA
206.53.190.0/24RADBNo ROA
206.53.191.0/24RADBNo ROA

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.