bgpreport

Network · data from 2026-11-12

AS9064 IIRUC-DIGICOM-SA Internet City Doi SA

Registry name: IIRUC-DIGICOM-SA Internet City Doi SA, RO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9064, 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.
193.226.145.0/24 Invalid: origin Other origin only 84 12% 37
193.226.150.0/24 Invalid: origin Other origin only 84 12% 37
194.102.201.0/24 No ROA RIR databaseRIPE 673 100% 66
194.102.93.0/24 Valid RIR databaseRIPE 673 100% 66
194.102.118.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS9064 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 5 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin193.226.145.0/24ROAs covering it name AS5606, not AS9064. If AS9064 should announce it, add a ROA for AS9064.84 of 673
Route object: none193.226.145.0/24Route objects for it name AS5588, AS5606. Add a route object with origin AS9064 in the RIR database for the space.84 of 673
ROA: origin193.226.150.0/24ROAs covering it name AS5606, not AS9064. If AS9064 should announce it, add a ROA for AS9064.84 of 673
Route object: none193.226.150.0/24Route objects for it name AS5588, AS5606. Add a route object with origin AS9064 in the RIR database for the space.84 of 673
ROA: none194.102.201.0/24No ROA covers it. Add a ROA for AS9064, maxLength 24.673 of 673

Route objects not announced

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