bgpreport

Network · data from 2026-11-12

AS136174 The Professional Communications

Registry name: TPCPL-AS-AP - The Professional Communications Pvt Ltd, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136174, 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.184.0.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.46.142.0/24 Valid RIR databaseAPNIC 672 100% 67
103.46.143.0/24 Valid RIR databaseAPNIC 672 100% 67
103.122.158.0/24 Valid RIR databaseAPNIC 672 100% 67
103.122.159.0/24 Valid RIR databaseAPNIC 672 100% 67
103.209.52.0/24 Valid RIR databaseAPNIC 672 100% 67
103.209.53.0/24 Valid RIR databaseAPNIC 672 100% 67
203.215.165.0/24 Valid RIR databaseAPNIC 672 100% 67
103.184.1.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
2404:c040::/32 Valid RIR databaseAPNIC 631 99% 67
203.215.180.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS136174: AS136174:AS-PEERS. 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 (AS136174 isn't in the set, or no route object for AS136174 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 objectsAS136174 in itNot covered
AS136174:AS-PEERS 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 1 are in fix.csv.

  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
AS-SET: not foundAS136174:AS-PEERSPeeringDB names AS136174:AS-PEERS; no IRR database read has it.

Route objects not announced

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