bgpreport

Network · data from 2026-11-12

AS264158 RQNET

Registry name: AS264158 - E QUARESMA NETO PROVEDORES EIRELI - ME, BR · PeeringDB

9IPv4 routes 0.0% RPKI valid · 100.0% with a route object
4IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
13No 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 AS264158, seen from no peer

Announced routes

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

168.121.162.0/23 No ROA Other IRR onlyTC 671 100% 66
168.121.163.0/24 No ROA Other IRR onlyRADB, TC 670 100% 66
138.97.93.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
138.97.92.0/24 No ROA Other IRR onlyRADB, TC 667 99% 67
138.97.94.0/23 No ROA Other IRR onlyTC 667 99% 67
168.121.160.0/24 No ROA Other IRR onlyRADB, TC 666 99% 67
168.121.161.0/24 No ROA Other IRR onlyRADB, TC 665 99% 67
138.97.94.0/24 No ROA Other IRR onlyRADB, TC 662 98% 67
138.97.95.0/24 No ROA Other IRR onlyRADB, TC 660 98% 67
2804:2360:f000::/36 No ROA Other IRR onlyNTTCOM 636 100% 67
2804:2360::/32 No ROA Other IRR onlyALTDB, NTTCOM, RADB, TC 631 99% 67
2804:2360::/33 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:2360:8000::/33 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS264158'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 35 are in fix.csv.

  • ROA: none13
  • Route object: RIR13
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none168.121.162.0/23No ROA covers it. Add a ROA for AS264158, maxLength 23.671 of 673
Route object: RIR168.121.162.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none168.121.163.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.670 of 673
Route object: RIR168.121.163.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none138.97.93.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.669 of 673
Route object: RIR138.97.93.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none138.97.92.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.667 of 673
Route object: RIR138.97.92.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none138.97.94.0/23No ROA covers it. Add a ROA for AS264158, maxLength 23.667 of 673
Route object: RIR138.97.94.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
ROA: none168.121.160.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.666 of 673
Route object: RIR168.121.160.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none168.121.161.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.665 of 673
Route object: RIR168.121.161.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
ROA: none138.97.94.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.662 of 673
Route object: RIR138.97.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.662 of 673
ROA: none138.97.95.0/24No ROA covers it. Add a ROA for AS264158, maxLength 24.660 of 673
Route object: RIR138.97.95.0/24Route object only in RADB, TC. Add it in the RIR database for the space.660 of 673
ROA: none2804:2360:f000::/36No ROA covers it. Add a ROA for AS264158, maxLength 36.636 of 636
Route object: RIR2804:2360:f000::/36Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636
ROA: none2804:2360::/32No ROA covers it. Add a ROA for AS264158, maxLength 32.631 of 636
Route object: RIR2804:2360::/32Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:2360::/33No ROA covers it. Add a ROA for AS264158, maxLength 33.631 of 636
Route object: RIR2804:2360::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:2360:8000::/33No ROA covers it. Add a ROA for AS264158, maxLength 33.631 of 636
Route object: RIR2804:2360:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

138.97.92.0/22ALTDB, RADB, TCNo ROA
138.97.92.0/23TCNo ROA
168.121.160.0/22ALTDB, NTTCOM, RADB, TCNo ROA
168.121.160.0/23TCNo ROA
168.121.162.0/24RADB, TCNo ROA
2804:2360::/34RADB, TCNo ROA
2804:2360:4000::/34RADB, TCNo ROA
2804:2360:8000::/34RADB, TCNo ROA
2804:2360:c000::/34RADB, TCNo 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.