bgpreport

Network · data from 2026-11-12

AS271771 JARINU NETWORK TELECOMUNICACAO LTDA

Registry name: AS271771 - JARINU NETWORK TELECOMUNICACAO LTDA, BR · PeeringDB

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

Announced routes

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

2804:80c0::/33 No ROA Nonecovered by 2804:80c0::/32 635 100% 67

AS-SET

AS271771'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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:80c0::/33No ROA covers it. Add a ROA for AS271771, maxLength 33.635 of 636
Route object: none2804:80c0::/33No route object for it. A route object for 2804:80c0::/32 with origin AS271771 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271771 in the RIR database for the space.635 of 636

Route objects not announced

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

2804:80c0::/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.