bgpreport

Network · data from 2026-11-12

AS36881 Multitel Servicos de Telecomunicacoes

Registry name: Multitel Servicos de Telecomunicacoes - Multitel Servicos de Telecomunicacoes, AO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36881, 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.
169.239.109.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
169.239.111.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
196.32.192.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
196.32.193.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
196.32.194.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
196.32.195.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
196.32.196.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
196.32.197.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
169.239.108.0/24 No ROA RIR databaseAFRINIC, RADB 669 99% 67
169.239.110.0/24 No ROA RIR databaseAFRINIC, RADB 669 99% 67
196.32.198.0/24 No ROA RIR databaseAFRINIC, RADB 669 99% 67
196.32.199.0/24 No ROA RIR databaseAFRINIC, RADB 669 99% 67

AS-SET

AS36881'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 21 are in fix.csv.

  • ROA: none12
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none169.239.109.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none169.239.111.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none196.32.192.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none196.32.193.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none196.32.194.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none196.32.195.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none196.32.196.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none196.32.197.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.672 of 673
ROA: none169.239.108.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.669 of 673
ROA: none169.239.110.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.669 of 673
ROA: none196.32.198.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.669 of 673
ROA: none196.32.199.0/24No ROA covers it. Add a ROA for AS36881, maxLength 24.669 of 673

Route objects not announced

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

156.0.254.0/24RADBNo ROA
196.32.192.0/21RIPE-NONAUTHNo ROA
196.46.21.0/24RADBNo ROA
196.216.161.0/24RADBNo ROA
196.216.198.0/23RADBNo ROA
196.216.248.0/23RADBNo ROA
196.216.248.0/24RADBNo ROA
196.216.249.0/24RADBNo ROA
196.223.19.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.