bgpreport

Network · data from 2026-11-12

AS263399 AS263399 - GUTEMBERG GONCALVES BARBALHO - ME

Registry name: AS263399 - GUTEMBERG GONCALVES BARBALHO - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263399, 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:15a0::/34 No ROA Nonecovered by 2804:15a0::/32 25 4%low visibility 11
2804:15a0:4000::/34 No ROA Nonecovered by 2804:15a0::/32 25 4%low visibility 11
2804:15a0:8000::/34 No ROA Nonecovered by 2804:15a0::/32 25 4%low visibility 11
2804:15a0:c000::/34 No ROA Nonecovered by 2804:15a0::/32 25 4%low visibility 11
177.222.224.0/22 No ROA Other IRR onlyRADB, TC 670 100% 66
2804:15a0::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS263399 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:15a0::/34No ROA covers it. Add a ROA for AS263399, maxLength 34.25 of 636
Route object: none2804:15a0::/34No route object for it. A route object for 2804:15a0::/32 with origin AS263399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263399 in the RIR database for the space.25 of 636
ROA: none2804:15a0:4000::/34No ROA covers it. Add a ROA for AS263399, maxLength 34.25 of 636
Route object: none2804:15a0:4000::/34No route object for it. A route object for 2804:15a0::/32 with origin AS263399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263399 in the RIR database for the space.25 of 636
ROA: none2804:15a0:8000::/34No ROA covers it. Add a ROA for AS263399, maxLength 34.25 of 636
Route object: none2804:15a0:8000::/34No route object for it. A route object for 2804:15a0::/32 with origin AS263399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263399 in the RIR database for the space.25 of 636
ROA: none2804:15a0:c000::/34No ROA covers it. Add a ROA for AS263399, maxLength 34.25 of 636
Route object: none2804:15a0:c000::/34No route object for it. A route object for 2804:15a0::/32 with origin AS263399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263399 in the RIR database for the space.25 of 636
ROA: none177.222.224.0/22No ROA covers it. Add a ROA for AS263399, maxLength 22.670 of 673
Route object: RIR177.222.224.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:15a0::/32No ROA covers it. Add a ROA for AS263399, maxLength 32.636 of 636
Route object: RIR2804:15a0::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.222.227.0/24RADBNo ROA
2801:80:22f0::/48RADBNo 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.