bgpreport

Network · data from 2026-11-12

AS131459 Blu Ultraband Internet Services

Registry name: VCPL-IN - 88c, Race Course Road, Coimbatore 641018, IN · PeeringDB

17IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
4Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS131459, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131459, 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.

43.250.40.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
43.250.41.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
43.250.42.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
43.250.42.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
43.250.43.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.5.112.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
103.5.112.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.5.113.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.5.114.0/23 Valid RIR databaseAPNIC, RADB 673 100% 67
103.5.114.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.5.115.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.242.136.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.242.138.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.242.138.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
2402:900::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2402:900:1::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
103.5.112.0/22 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
2402:900:2::/48 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
103.242.136.0/22 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1
103.242.137.0/24 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS131459: AS131459:AS-BLUUIS. 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 (AS131459 isn't in the set, or no route object for AS131459 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 objectsAS131459 in itNot covered
AS131459:AS-BLUUIS RADB 2127 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 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

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

43.250.40.0/22APNIC, RADBValid
43.250.40.0/23APNIC, RADBValid
103.242.136.0/23APNIC, RADBValid
103.242.139.0/24APNIC, RADBValid
2402:900::/32APNIC, RADBValid
2402:900:3::/48RADBValid

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.