bgpreport

Network · data from 2026-11-12

AS61950 Nossa Telecom

Registry name: AS61950 - Nossa Telecom Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61950, 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.
200.142.190.0/23 No ROA Nonecovered by 200.142.188.0/22 670 100% 67
200.142.191.0/24 No ROA Nonecovered by 200.142.188.0/22 670 100% 67
2804:18bc:c000::/34 No ROA Nonecovered by 2804:18bc::/32 635 100% 67
200.142.189.0/24 No ROA Other IRR onlyRADB 663 99% 67
2804:18bc:4000::/34 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS61950'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 12 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.142.190.0/23No ROA covers it. Add a ROA for AS61950, maxLength 23.670 of 673
Route object: none200.142.190.0/23No route object for it. A route object for 200.142.188.0/22 with origin AS61950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61950 in the RIR database for the space.670 of 673
ROA: none200.142.191.0/24No ROA covers it. Add a ROA for AS61950, maxLength 24.670 of 673
Route object: none200.142.191.0/24No route object for it. A route object for 200.142.188.0/22 with origin AS61950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61950 in the RIR database for the space.670 of 673
ROA: none2804:18bc:c000::/34No ROA covers it. Add a ROA for AS61950, maxLength 34.635 of 636
Route object: none2804:18bc:c000::/34No route object for it. A route object for 2804:18bc::/32 with origin AS61950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61950 in the RIR database for the space.635 of 636
ROA: none200.142.189.0/24No ROA covers it. Add a ROA for AS61950, maxLength 24.663 of 673
Route object: RIR200.142.189.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none2804:18bc:4000::/34No ROA covers it. Add a ROA for AS61950, maxLength 34.633 of 636
Route object: RIR2804:18bc:4000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

200.142.188.0/22RADBNo ROA
2804:18bc::/32RADBNo 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.