bgpreport

Network · data from 2026-11-12

AS215228 NETPOOL TECHNOLOGIES PRIVATE LIMITED

Registry name: NETPOOL NETPOOL TECHNOLOGIES PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215228, 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.216.168.0/24 No ROA Other origin only 672 100% 67
2001:df5:ad80::/48 No ROA Other origin only 2 0%low visibility 2
151.243.146.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
162.141.0.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
178.92.73.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
2a13:9500:1ae::/48 Valid RIR databaseRIPE 2 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS215228: AS215228:AS-MEMBERS. 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 (AS215228 isn't in the set, or no route object for AS215228 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 objectsAS215228 in itNot covered
AS215228:AS-MEMBERS In no IRR database read today.

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.

  • ROA: none2
  • Route object: none2
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.216.168.0/24No ROA covers it. Add a ROA for AS215228, maxLength 24.672 of 673
Route object: none103.216.168.0/24Route objects for it name AS135198. Add a route object with origin AS215228 in the RIR database for the space.672 of 673
ROA: none2001:df5:ad80::/48No ROA covers it. Add a ROA for AS215228, maxLength 48.2 of 636
Route object: none2001:df5:ad80::/48Route objects for it name AS140181. Add a route object with origin AS215228 in the RIR database for the space.2 of 636
AS-SET: not foundAS215228:AS-MEMBERSPeeringDB names AS215228:AS-MEMBERS; no IRR database read has it.

Route objects not announced

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

2a13:9500:178::/48RIPEValid

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.