bgpreport

Network · data from 2026-11-12

AS262622 DAVOI ISP-PROVEDOR DE SOL.E ACESSO A INTERNET-LTDA

Registry name: AS262622 - DAVOI ISP-PROVEDOR DE SOL.E ACESSO A INTERNET-LTDA, BR · PeeringDB

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

Announced routes

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

177.86.41.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
138.186.80.0/22 No ROA Other IRR onlyRADB, TC 667 99% 67
138.186.82.0/23 No ROA Other IRR onlyRADB, TC 667 99% 67
177.86.40.0/22 No ROA Other IRR onlyRADB, TC 667 99% 67
201.148.172.0/22 No ROA Other IRR onlyRADB, TC 667 99% 67
201.148.172.0/23 No ROA Other IRR onlyRADB, TC 667 99% 67
138.186.80.0/23 No ROA Other IRR onlyRADB, TC 666 99% 67
177.86.40.0/23 No ROA Other IRR onlyRADB, TC 666 99% 67
177.86.42.0/23 No ROA Other IRR onlyRADB, TC 662 98% 67
201.148.173.0/24 No ROA Other IRR onlyRADB, TC 662 98% 67
201.148.174.0/23 No ROA Other IRR onlyRADB, TC 662 98% 67
2804:730::/32 No ROA Other IRR onlyRADB, TC 630 99% 67

AS-SET

AS262622'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 64 are in fix.csv.

  • ROA: none12
  • Route object: RIR12
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
ROA: none177.86.41.0/24No ROA covers it. Add a ROA for AS262622, maxLength 24.671 of 673
Route object: RIR177.86.41.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none138.186.80.0/22No ROA covers it. Add a ROA for AS262622, maxLength 22.667 of 673
Route object: RIR138.186.80.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none138.186.82.0/23No ROA covers it. Add a ROA for AS262622, maxLength 23.667 of 673
Route object: RIR138.186.82.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none177.86.40.0/22No ROA covers it. Add a ROA for AS262622, maxLength 22.667 of 673
Route object: RIR177.86.40.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none201.148.172.0/22No ROA covers it. Add a ROA for AS262622, maxLength 22.667 of 673
Route object: RIR201.148.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none201.148.172.0/23No ROA covers it. Add a ROA for AS262622, maxLength 23.667 of 673
Route object: RIR201.148.172.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none138.186.80.0/23No ROA covers it. Add a ROA for AS262622, maxLength 23.666 of 673
Route object: RIR138.186.80.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none177.86.40.0/23No ROA covers it. Add a ROA for AS262622, maxLength 23.666 of 673
Route object: RIR177.86.40.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none177.86.42.0/23No ROA covers it. Add a ROA for AS262622, maxLength 23.662 of 673
Route object: RIR177.86.42.0/23Route object only in RADB, TC. Add it in the RIR database for the space.662 of 673
ROA: none201.148.173.0/24No ROA covers it. Add a ROA for AS262622, maxLength 24.662 of 673
Route object: RIR201.148.173.0/24Route object only in RADB, TC. Add it in the RIR database for the space.662 of 673
ROA: none201.148.174.0/23No ROA covers it. Add a ROA for AS262622, maxLength 23.662 of 673
Route object: RIR201.148.174.0/23Route object only in RADB, TC. Add it in the RIR database for the space.662 of 673
ROA: none2804:730::/32No ROA covers it. Add a ROA for AS262622, maxLength 32.630 of 636
Route object: RIR2804:730::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

138.186.80.0/24RADB, TCNo ROA
138.186.81.0/24RADB, TCNo ROA
138.186.82.0/24RADB, TCNo ROA
138.186.83.0/24RADB, TCNo ROA
177.86.40.0/24RADB, TCNo ROA
177.86.42.0/24RADB, TCNo ROA
177.86.43.0/24RADB, TCNo ROA
201.148.172.0/24RADB, TCNo ROA
201.148.174.0/24RADB, TCNo ROA
201.148.175.0/24RADB, TCNo ROA
2804:730::/33RADBNo ROA
2804:730::/34RADBNo ROA
2804:730::/35RADBNo ROA
2804:730::/36RADBNo ROA
2804:730:1000::/36RADBNo ROA
2804:730:2000::/35RADBNo ROA
2804:730:2000::/36RADBNo ROA
2804:730:3000::/36RADBNo ROA
2804:730:4000::/34RADBNo ROA
2804:730:4000::/35RADBNo ROA
2804:730:4000::/36RADBNo ROA
2804:730:5000::/36RADBNo ROA
2804:730:6000::/35RADBNo ROA
2804:730:6000::/36RADBNo ROA
2804:730:7000::/36RADBNo ROA
2804:730:8000::/33RADBNo ROA
2804:730:8000::/34RADBNo ROA
2804:730:8000::/35RADBNo ROA
2804:730:8000::/36RADBNo ROA
2804:730:9000::/36RADBNo ROA
2804:730:a000::/35RADBNo ROA
2804:730:a000::/36RADBNo ROA
2804:730:b000::/36RADBNo ROA
2804:730:c000::/34RADBNo ROA
2804:730:c000::/35RADBNo ROA
2804:730:c000::/36RADBNo ROA
2804:730:d000::/36RADBNo ROA
2804:730:e000::/35RADBNo ROA
2804:730:e000::/36RADBNo ROA
2804:730:f000::/36RADBNo 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.