bgpreport

Network · data from 2026-11-12

AS134855 ucom digital

Registry name: IPNETBROADBANDPVTLTD-AS-IN - IPNET BROADBAND PRIVATE LIMITED, 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
0Low visibility seen by under 10% of full-table peers
48Route objects not announced registered with origin AS134855, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134855, 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.244.35.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67

AS-SET

AS134855'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 49 are in fix.csv.

  • ROA: none1
  • Route object: not announced48
ChangePrefix or setDetailFull-table peers
ROA: none103.244.35.0/24No ROA covers it. Add a ROA for AS134855, maxLength 24.673 of 673

Route objects not announced

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

114.29.229.0/24APNICInvalid: origin
114.29.230.0/24APNICInvalid: origin
150.242.178.0/24RADBNo ROA
150.242.179.0/24RADBNo ROA
202.160.161.0/24APNICInvalid: origin
202.160.162.0/24APNICInvalid: origin
202.160.163.0/24APNICInvalid: origin
202.160.164.0/24APNICInvalid: origin
202.160.166.0/24APNICInvalid: origin
202.160.167.0/24APNICInvalid: origin
202.160.168.0/24APNICInvalid: origin
202.160.171.0/24APNICInvalid: origin
202.160.173.0/24APNICInvalid: origin
202.160.174.0/24APNIC, RADBValid
202.160.175.0/24APNICInvalid: origin
2403:1d00::/32APNICNo ROA
2403:1d00:3100::/48APNICNo ROA
2403:1d00:3101::/48APNICNo ROA
2403:1d00:3102::/48APNICNo ROA
2403:1d00:3103::/48APNICNo ROA
2403:1d00:3104::/48APNICNo ROA
2403:1d00:3105::/48APNICNo ROA
2403:1d00:3106::/48APNICNo ROA
2403:1d00:3107::/48APNICNo ROA
2403:1d00:3108::/48APNICNo ROA
2403:1d00:3109::/48APNICNo ROA
2403:1d00:310a::/48APNICNo ROA
2403:1d00:310b::/48APNICNo ROA
2403:1d00:310c::/48APNICNo ROA
2403:1d00:310d::/48APNICNo ROA
2403:1d00:310e::/48APNICNo ROA
2403:1d00:310f::/48APNICNo ROA
2403:1d00:3200::/48APNICNo ROA
2403:1d00:3201::/48APNICNo ROA
2403:1d00:3202::/48APNICNo ROA
2403:1d00:3203::/48APNICNo ROA
2403:1d00:3204::/48APNICNo ROA
2403:1d00:3205::/48APNICNo ROA
2403:1d00:3206::/48APNICNo ROA
2403:1d00:3207::/48APNICNo ROA
2403:1d00:3208::/48APNICNo ROA
2403:1d00:3209::/48APNICNo ROA
2403:1d00:320a::/48APNICNo ROA
2403:1d00:320b::/48APNICNo ROA
2403:1d00:320c::/48APNICNo ROA
2403:1d00:320d::/48APNICNo ROA
2403:1d00:320e::/48APNICNo ROA
2403:1d00:320f::/48APNICNo 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.