bgpreport

Network · data from 2026-11-12

AS262483 Prefeitura Municipal de Campo Grande

Registry name: AS262483 - Prefeitura Municipal de Campo Grande, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262483, 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.
2801:80:220:5::/64 No ROA Nonecovered by 2801:80:220::/48 3 0%low visibility 3
177.53.207.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.53.204.0/24 No ROA Other IRR onlyRADB 663 99% 66
2801:80:220::/48 No ROA Other IRR onlyALTDB, RADB, TC 628 99% 67
177.53.204.0/22 No ROA Other IRR onlyALTDB, RADB, TC 63 9%low visibility 31
177.53.205.0/24 No ROA Other IRR onlyRADB 3 0%low visibility 4

AS-SET

AS262483'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 18 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2801:80:220:5::/64No ROA covers it. Add a ROA for AS262483, maxLength 64.3 of 636
Route object: none2801:80:220:5::/64No route object for it. A route object for 2801:80:220::/48 with origin AS262483 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262483 in the RIR database for the space.3 of 636
ROA: none177.53.207.0/24No ROA covers it. Add a ROA for AS262483, maxLength 24.671 of 673
Route object: RIR177.53.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.53.204.0/24No ROA covers it. Add a ROA for AS262483, maxLength 24.663 of 673
Route object: RIR177.53.204.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none2801:80:220::/48No ROA covers it. Add a ROA for AS262483, maxLength 48.628 of 636
Route object: RIR2801:80:220::/48Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.628 of 636
ROA: none177.53.204.0/22No ROA covers it. Add a ROA for AS262483, maxLength 22.63 of 673
Route object: RIR177.53.204.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.63 of 673
ROA: none177.53.205.0/24No ROA covers it. Add a ROA for AS262483, maxLength 24.3 of 673
Route object: RIR177.53.205.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

177.53.204.0/23RADBNo ROA
177.53.206.0/23RADBNo ROA
177.53.206.0/24RADBNo ROA
2801:80:220::/64RADBNo ROA
2801:80:220:1::/64RADBNo ROA
2801:80:220:2::/64RADBNo 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.