bgpreport

Network · data from 2026-11-12

AS135065 NIDOM-AS-AP - National Directorate of Information and Technology

Registry name: NIDOM-AS-AP - National Directorate of Information and Technology, TL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135065, 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.
103.208.36.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.208.37.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.208.38.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.208.39.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68

AS-SET

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

  • Route object: not announced18

Route objects not announced

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

103.208.36.0/22APNIC, RADBValid
2001:df0:7a00::/48RADBNo ROA
2001:df0:7a00::/49RADBNo ROA
2001:df0:7a00::/50RADBNo ROA
2001:df0:7a00::/51RADBNo ROA
2001:df0:7a00::/52RADBNo ROA
2001:df0:7a00::/53RADBNo ROA
2001:df0:7a00::/54RADBNo ROA
2001:df0:7a00::/55RADBNo ROA
2001:df0:7a00::/56RADBNo ROA
2001:df0:7a00::/57RADBNo ROA
2001:df0:7a00::/58RADBNo ROA
2001:df0:7a00::/59RADBNo ROA
2001:df0:7a00::/60RADBNo ROA
2001:df0:7a00::/61RADBNo ROA
2001:df0:7a00::/62RADBNo ROA
2001:df0:7a00::/63RADBNo ROA
2001:df0:7a00::/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.