bgpreport

Network · data from 2026-11-12

AS271603 CARDOSO COM E SERVICOS DE INTERNET

Registry name: AS271603 - GIGANET TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271603, 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:7e1c:20::/44 No ROA Nonecovered by 2804:7e1c::/32 631 99% 67
2804:7e1c:10::/44 No ROA Nonecovered by 2804:7e1c::/32 630 99% 67
190.3.164.0/22 No ROA Other IRR onlyRADB, TC 670 100% 67
190.3.164.0/24 No ROA Other IRR onlyRADB 670 100% 67
190.3.165.0/24 No ROA Other IRR onlyRADB 670 100% 67
190.3.167.0/24 No ROA Other IRR onlyRADB 670 100% 67
190.3.166.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:7e1c::/32 No ROA Other IRR onlyRADB, TC 636 100% 67
2804:7e1c:8000::/33 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

AS271603'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 18 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none2804:7e1c:20::/44No ROA covers it. Add a ROA for AS271603, maxLength 44.631 of 636
Route object: none2804:7e1c:20::/44No route object for it. A route object for 2804:7e1c::/32 with origin AS271603 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271603 in the RIR database for the space.631 of 636
ROA: none2804:7e1c:10::/44No ROA covers it. Add a ROA for AS271603, maxLength 44.630 of 636
Route object: none2804:7e1c:10::/44No route object for it. A route object for 2804:7e1c::/32 with origin AS271603 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271603 in the RIR database for the space.630 of 636
ROA: none190.3.164.0/22No ROA covers it. Add a ROA for AS271603, maxLength 22.670 of 673
Route object: RIR190.3.164.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none190.3.164.0/24No ROA covers it. Add a ROA for AS271603, maxLength 24.670 of 673
Route object: RIR190.3.164.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none190.3.165.0/24No ROA covers it. Add a ROA for AS271603, maxLength 24.670 of 673
Route object: RIR190.3.165.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none190.3.167.0/24No ROA covers it. Add a ROA for AS271603, maxLength 24.670 of 673
Route object: RIR190.3.167.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none190.3.166.0/24No ROA covers it. Add a ROA for AS271603, maxLength 24.666 of 673
Route object: RIR190.3.166.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:7e1c::/32No ROA covers it. Add a ROA for AS271603, maxLength 32.636 of 636
Route object: RIR2804:7e1c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:7e1c:8000::/33No ROA covers it. Add a ROA for AS271603, maxLength 33.631 of 636
Route object: RIR2804:7e1c:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

Every route object with origin AS271603 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.