bgpreport

Network · data from 2026-11-12

AS263638 AS263638 - Prefeitura de Cuiaba

Registry name: AS263638 - Prefeitura de Cuiaba, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263638, 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.
186.236.240.0/20 No ROA Other IRR onlyTC 2 0%low visibility 2

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none186.236.240.0/20No ROA covers it. Add a ROA for AS263638, maxLength 20.2 of 673
Route object: RIR186.236.240.0/20Route object only in TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

186.236.240.0/22RADBNo ROA
186.236.240.0/23RADB, TCNo ROA
186.236.240.0/24RIPE-NONAUTHNo ROA
186.236.241.0/24RIPE-NONAUTHNo ROA
186.236.242.0/23RADB, TCNo ROA
186.236.242.0/24RIPE-NONAUTHNo ROA
186.236.243.0/24RIPE-NONAUTHNo ROA
186.236.244.0/23RADBNo ROA
186.236.244.0/24RIPE-NONAUTHNo ROA
186.236.245.0/24RIPE-NONAUTHNo ROA
186.236.246.0/23RADBNo ROA
186.236.246.0/24RIPE-NONAUTHNo ROA
186.236.247.0/24RIPE-NONAUTHNo ROA
2801:80:7e0::/48TCNo 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.