bgpreport

Network · data from 2026-11-12

AS263154 Avancar

Registry name: AS263154 - AVANCAR INTERNET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263154, 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.
138.59.238.0/24 No ROA Nonecovered by 138.59.236.0/22 1 0%low visibility 1
138.59.239.0/24 No ROA Nonecovered by 138.59.236.0/22 1 0%low visibility 1
170.254.199.0/24 No ROA Nonecovered by 170.254.196.0/22 1 0%low visibility 1
138.59.236.0/22 No ROA Other IRR onlyTC 669 99% 67
177.93.168.0/21 No ROA Other IRR onlyTC 669 99% 67
170.247.44.0/22 No ROA Other IRR onlyTC 668 99% 67
170.254.196.0/22 No ROA Other IRR onlyTC 668 99% 67
2804:178c::/32 No ROA Other IRR onlyRADB, TC 632 99% 67

AS-SET

AS263154'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 16 are in fix.csv.

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none138.59.238.0/24No ROA covers it. Add a ROA for AS263154, maxLength 24.1 of 673
Route object: none138.59.238.0/24No route object for it. A route object for 138.59.236.0/22 with origin AS263154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263154 in the RIR database for the space.1 of 673
ROA: none138.59.239.0/24No ROA covers it. Add a ROA for AS263154, maxLength 24.1 of 673
Route object: none138.59.239.0/24No route object for it. A route object for 138.59.236.0/22 with origin AS263154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263154 in the RIR database for the space.1 of 673
ROA: none170.254.199.0/24No ROA covers it. Add a ROA for AS263154, maxLength 24.1 of 673
Route object: none170.254.199.0/24No route object for it. A route object for 170.254.196.0/22 with origin AS263154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263154 in the RIR database for the space.1 of 673
ROA: none138.59.236.0/22No ROA covers it. Add a ROA for AS263154, maxLength 22.669 of 673
Route object: RIR138.59.236.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.93.168.0/21No ROA covers it. Add a ROA for AS263154, maxLength 21.669 of 673
Route object: RIR177.93.168.0/21Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none170.247.44.0/22No ROA covers it. Add a ROA for AS263154, maxLength 22.668 of 673
Route object: RIR170.247.44.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none170.254.196.0/22No ROA covers it. Add a ROA for AS263154, maxLength 22.668 of 673
Route object: RIR170.254.196.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:178c::/32No ROA covers it. Add a ROA for AS263154, maxLength 32.632 of 636
Route object: RIR2804:178c::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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