bgpreport

Network · data from 2026-11-12

AS135207 Cloudnet Communications

Registry name: CLOUDNET-AS - Cloudnet Communications Pvt Ltd, IN · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
9Route objects not announced registered with origin AS135207, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS135207, 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.123.48.0/24 Valid RIR databaseAPNIC 673 100% 67
103.123.49.0/24 Valid RIR databaseAPNIC 672 100% 67
103.215.148.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.215.149.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.215.150.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.215.151.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
2401:fe40::/48 Valid RIR databaseAPNIC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS135207: AS135207:AS-CLOUDNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS135207 isn't in the set, or no route object for AS135207 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS135207 in itNot covered
AS135207:AS-CLOUDNET APNIC 162916 Yes 0

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

  • Route object: not announced9

Route objects not announced

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

103.78.20.0/24APNICInvalid: origin
103.78.21.0/24APNICInvalid: origin
103.87.64.0/24APNICInvalid: origin
103.87.65.0/24APNICInvalid: origin
103.123.48.0/23APNICValid
2401:fe40::/32APNICNo ROA
2401:fe40:1::/48APNICValid
2401:fe40:2::/48APNICValid
2401:fe40:3::/48APNICValid

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.