bgpreport

Network · data from 2026-11-12

AS267367 GIGASETE TELECOM

Registry name: AS267367 - GIGASETE TELECOM LTDA - ME, BR · PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
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
4Route objects not announced registered with origin AS267367, seen from no peer

Announced routes

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

45.234.148.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
2804:4c60::/32 No ROA Other IRR onlyRADB, TC 635 100% 70
2804:4c60::/33 No ROA Other IRR onlyTC 363 57% 65
2804:4c60:8000::/33 No ROA Other IRR onlyTC 363 57% 65
45.234.148.0/23 No ROA Other IRR onlyTC 210 31% 56
45.234.150.0/23 No ROA Other IRR onlyTC 210 31% 56
45.234.148.0/24 No ROA Other IRR onlyTC 166 25% 52
45.234.149.0/24 No ROA Other IRR onlyTC 166 25% 52
45.234.150.0/24 No ROA Other IRR onlyTC 163 24% 51
45.234.151.0/24 No ROA Other IRR onlyTC 163 24% 51

AS-SET

AS267367'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 24 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.234.148.0/22No ROA covers it. Add a ROA for AS267367, maxLength 22.672 of 673
Route object: RIR45.234.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:4c60::/32No ROA covers it. Add a ROA for AS267367, maxLength 32.635 of 636
Route object: RIR2804:4c60::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:4c60::/33No ROA covers it. Add a ROA for AS267367, maxLength 33.363 of 636
Route object: RIR2804:4c60::/33Route object only in TC. Add it in the RIR database for the space.363 of 636
ROA: none2804:4c60:8000::/33No ROA covers it. Add a ROA for AS267367, maxLength 33.363 of 636
Route object: RIR2804:4c60:8000::/33Route object only in TC. Add it in the RIR database for the space.363 of 636
ROA: none45.234.148.0/23No ROA covers it. Add a ROA for AS267367, maxLength 23.210 of 673
Route object: RIR45.234.148.0/23Route object only in TC. Add it in the RIR database for the space.210 of 673
ROA: none45.234.150.0/23No ROA covers it. Add a ROA for AS267367, maxLength 23.210 of 673
Route object: RIR45.234.150.0/23Route object only in TC. Add it in the RIR database for the space.210 of 673
ROA: none45.234.148.0/24No ROA covers it. Add a ROA for AS267367, maxLength 24.166 of 673
Route object: RIR45.234.148.0/24Route object only in TC. Add it in the RIR database for the space.166 of 673
ROA: none45.234.149.0/24No ROA covers it. Add a ROA for AS267367, maxLength 24.166 of 673
Route object: RIR45.234.149.0/24Route object only in TC. Add it in the RIR database for the space.166 of 673
ROA: none45.234.150.0/24No ROA covers it. Add a ROA for AS267367, maxLength 24.163 of 673
Route object: RIR45.234.150.0/24Route object only in TC. Add it in the RIR database for the space.163 of 673
ROA: none45.234.151.0/24No ROA covers it. Add a ROA for AS267367, maxLength 24.163 of 673
Route object: RIR45.234.151.0/24Route object only in TC. Add it in the RIR database for the space.163 of 673

Route objects not announced

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

2804:4c60::/34TCNo ROA
2804:4c60:4000::/34TCNo ROA
2804:4c60:8000::/34TCNo ROA
2804:4c60:c000::/34TCNo 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.