bgpreport

Network · data from 2026-11-12

AS139515 ZITA

Registry name: ZITATEL-AS-IN - ZITA TELECOM PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139515, 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.71.108.0/23 Valid RIR databaseAPNIC 672 100% 67
103.182.106.0/23 Valid RIR databaseAPNIC 672 100% 67
103.182.107.0/24 Valid RIR databaseAPNIC 672 100% 67
163.223.42.0/23 Valid RIR databaseAPNIC 672 100% 67
2001:df2:9bc0::/48 Valid RIR databaseAPNIC 636 100% 69
103.182.106.0/24 Valid RIR databaseAPNIC 50 7%low visibility 31
103.71.108.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.71.109.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
163.223.42.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
163.223.43.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29

AS-SET

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

  • AS-SET: missing member5
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS139515:AS-ZITATELAS139515:AS-ZITATEL (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS139515:AS-ZITATELAS139515:AS-ZITATEL (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS139515:AS-ZITATELAS139515:AS-ZITATEL (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS139515:AS-ZITATELAS139515:AS-ZITATEL (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS139515:AS-ZITATELAS139515:AS-ZITATEL (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

Every route object with origin AS139515 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.