bgpreport

Network · data from 2026-11-12

AS135687 Qwistel Network Service

Registry name: QWISTELN-AS-IN - Qwistel Network Service Private Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135687, 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.
38.246.198.0/24 Valid Nonecovered by 38.246.198.0/23 671 100% 67
38.246.199.0/24 Valid Nonecovered by 38.246.198.0/23 671 100% 67
38.246.198.0/23 Valid RIR databaseARIN 672 100% 67
103.127.130.0/24 Valid RIR databaseAPNIC 672 100% 67
103.174.243.0/24 Valid RIR databaseAPNIC 672 100% 67
103.176.16.0/24 Valid RIR databaseAPNIC 672 100% 67
103.176.17.0/24 Valid RIR databaseAPNIC 672 100% 67
2001:df7:4c80::/48 Valid RIR databaseAPNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS135687: AS135687:AS-QWISTELN. 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 (AS135687 isn't in the set, or no route object for AS135687 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 objectsAS135687 in itNot covered
AS135687:AS-QWISTELN APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7147320,801 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 7 are in fix.csv.

  • Route object: none2
  • AS-SET: missing member5
ChangePrefix or setDetailFull-table peers
Route object: none38.246.198.0/24No route object for it. A route object for 38.246.198.0/23 with origin AS135687 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135687 in the RIR database for the space.671 of 673
Route object: none38.246.199.0/24No route object for it. A route object for 38.246.198.0/23 with origin AS135687 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135687 in the RIR database for the space.671 of 673
AS-SET: missing memberAS135687:AS-QWISTELNAS135687:AS-QWISTELN (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS135687:AS-QWISTELNAS135687:AS-QWISTELN (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS135687:AS-QWISTELNAS135687:AS-QWISTELN (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS135687:AS-QWISTELNAS135687:AS-QWISTELN (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS135687:AS-QWISTELNAS135687:AS-QWISTELN (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

Every route object with origin AS135687 is announced.

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.