bgpreport

Network · data from 2026-11-12

AS37229 Atlantique Telecom Togo

Registry name: ATLANTIQUE TELECOM TOGO - ATLANTIQUE TELECOM TOGO, TG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37229, 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.
41.78.136.0/22 No ROA Other IRR onlyRADB 673 100% 67
41.78.136.0/24 No ROA Other IRR onlyRADB 673 100% 67
41.78.137.0/24 No ROA Other IRR onlyRADB 673 100% 67
41.78.138.0/24 No ROA Other IRR onlyRADB 673 100% 67
41.78.139.0/24 No ROA Other IRR onlyRADB 672 100% 67
102.212.92.0/22 No ROA RIR databaseAFRINIC 673 100% 67
102.212.93.0/24 No ROA RIR databaseAFRINIC 673 100% 67
102.212.94.0/24 No ROA RIR databaseAFRINIC 673 100% 67
102.212.95.0/24 No ROA RIR databaseAFRINIC 673 100% 67
102.212.92.0/24 No ROA RIR databaseAFRINIC 672 100% 67

AS-SET

AS37229'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 15 are in fix.csv.

  • ROA: none10
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none41.78.136.0/22No ROA covers it. Add a ROA for AS37229, maxLength 22.673 of 673
Route object: RIR41.78.136.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.78.136.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.673 of 673
Route object: RIR41.78.136.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.78.137.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.673 of 673
Route object: RIR41.78.137.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.78.138.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.673 of 673
Route object: RIR41.78.138.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.78.139.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.672 of 673
Route object: RIR41.78.139.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.212.92.0/22No ROA covers it. Add a ROA for AS37229, maxLength 22.673 of 673
ROA: none102.212.93.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.673 of 673
ROA: none102.212.94.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.673 of 673
ROA: none102.212.95.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.673 of 673
ROA: none102.212.92.0/24No ROA covers it. Add a ROA for AS37229, maxLength 24.672 of 673

Route objects not announced

Every route object with origin AS37229 is announced.

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.