bgpreport

Network · data from 2026-11-12

AS150046 Xpress Fiber

Registry name: XPRESSBGP-AS-IN - Xpress Fiber Private Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150046, 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.163.60.0/24 No ROA None 671 100% 67
103.163.127.0/24 No ROA Other origin only 671 100% 67
2001:df6:1780::/48 No ROA Other origin only 634 100% 67
103.157.69.0/24 Valid RIR databaseAPNIC 672 100% 67
103.191.114.0/24 Valid RIR databaseAPNIC 672 100% 67
103.191.115.0/24 Valid RIR databaseAPNIC 672 100% 67
103.147.128.0/24 Valid RIR databaseAPNIC 671 100% 67
103.158.111.0/24 Valid RIR databaseAPNIC 671 100% 67
2001:df0:ffc0::/48 Valid RIR databaseAPNIC 634 100% 67
2001:df5:8240::/48 Valid RIR databaseAPNIC, RADB 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS150046: AS150046:AS-CUSTOMERS. 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 (AS150046 isn't in the set, or no route object for AS150046 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 objectsAS150046 in itNot covered
AS150046:AS-CUSTOMERS RADB 2169 Yes 3

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

  • ROA: none3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.163.60.0/24No ROA covers it. Add a ROA for AS150046, maxLength 24.671 of 673
Route object: none103.163.60.0/24No route object for it. Add a route object with origin AS150046 in the RIR database for the space.671 of 673
ROA: none103.163.127.0/24No ROA covers it. Add a ROA for AS150046, maxLength 24.671 of 673
Route object: none103.163.127.0/24Route objects for it name AS140171. Add a route object with origin AS150046 in the RIR database for the space.671 of 673
ROA: none2001:df6:1780::/48No ROA covers it. Add a ROA for AS150046, maxLength 48.634 of 636
Route object: none2001:df6:1780::/48Route objects for it name AS140171. Add a route object with origin AS150046 in the RIR database for the space.634 of 636

Route objects not announced

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

103.191.114.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.