bgpreport

Network · data from 2026-11-12

AS133298 Netflow Broadband

Registry name: NETFLOW-AS-IN - Netflow broadband Pvt Ltd., IN · PeeringDB

5IPv4 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
2Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS133298, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133298, 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.157.128.0/24 Valid RIR databaseAPNIC 672 100% 66
101.1.28.0/23 Valid RIR databaseAPNIC 671 100% 66
2402:45e0::/32 Valid RIR databaseAPNIC 613 96% 68
103.157.129.0/24 Valid RIR databaseAPNIC 550 82% 66
101.1.28.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
101.1.29.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29

AS-SET

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

  • Route object: not announced9

Route objects not announced

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

43.241.64.0/22APNICNo ROA
43.241.64.0/23APNICNo ROA
43.241.64.0/24APNICInvalid: origin
43.241.65.0/24APNICInvalid: origin
43.241.66.0/23APNICNo ROA
43.241.66.0/24APNICInvalid: origin
43.241.67.0/24APNICInvalid: origin
103.99.8.0/23APNICNo ROA
103.157.128.0/23APNICValid

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.