bgpreport

Network · data from 2026-11-12

AS328722 Ciudad

Registry name: Ciudad Infrastructure Limited - Ciudad Infrastructure Limited, NG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328722, 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.
156.226.2.0/24 Invalid: origin Other origin only 84 12% 34
102.203.33.0/24 No ROA RIR databaseAFRINIC 673 100% 66
102.207.246.0/24 No ROA RIR databaseAFRINIC 673 100% 67
102.203.32.0/24 No ROA RIR databaseAFRINIC 671 100% 68
102.207.244.0/24 No ROA RIR databaseAFRINIC 671 100% 66
102.207.245.0/24 No ROA RIR databaseAFRINIC 671 100% 68
102.207.247.0/24 No ROA RIR databaseAFRINIC 671 100% 68
102.221.238.0/24 No ROA RIR databaseAFRINIC 671 100% 68
102.221.239.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.221.236.0/24 Valid RIR databaseAFRINIC 671 100% 68
102.221.237.0/24 Valid RIR databaseAFRINIC 671 100% 68

AS-SET

AS328722'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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none7
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin156.226.2.0/24ROAs covering it name AS17561, not AS328722. If AS328722 should announce it, add a ROA for AS328722.84 of 673
Route object: none156.226.2.0/24Route objects for it name AS17561. Add a route object with origin AS328722 in the RIR database for the space.84 of 673
ROA: none102.203.33.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.673 of 673
ROA: none102.207.246.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.673 of 673
ROA: none102.203.32.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.671 of 673
ROA: none102.207.244.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.671 of 673
ROA: none102.207.245.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.671 of 673
ROA: none102.207.247.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.671 of 673
ROA: none102.221.238.0/24No ROA covers it. Add a ROA for AS328722, maxLength 24.671 of 673

Route objects not announced

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

102.207.244.0/22AFRINICNo ROA
102.221.236.0/22AFRINIC, RADBNo ROA
102.221.236.0/23AFRINICValid

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.