Network · data from 2026-11-12

AS139202 Power Media

Registry name: POWERMEDIA-AS-AP - Power Media, BD · PeeringDB

1IPv4 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

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS139202, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS139202, 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.139.196.0/24	Valid	RIR databaseAPNIC	673 100%	67
2001:df0:8e80::/48	Valid	RIR databaseAPNIC	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS139202: AS139202:AS-POWERMEDIA. 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 (AS139202 isn't in the set, or no route object for AS139202 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.

Name	Database	ASNs	Sets	Route objects	AS139202 in it	Not covered
AS139202:AS-POWERMEDIA	APNIC4 member sets in no database: AS-149994, AS-152698, AS-DTIIG-139901, AS138004:AS-PEERING	2,123	31	187,767	Yes	0

Name

Database

ASNs

Sets

Route objects

AS139202 in it

Not covered

AS139202:AS-POWERMEDIA

APNIC4 member sets in no database: AS-149994, AS-152698, AS-DTIIG-139901, AS138004:AS-PEERING

2,123

187,767

Yes

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 member4
Route object: not announced1

Change	Prefix or set	Detail
AS-SET: missing member	AS139202:AS-POWERMEDIA	AS139202:AS-POWERMEDIA (APNIC) lists AS-149994; no IRR database read has it.
AS-SET: missing member	AS139202:AS-POWERMEDIA	AS139202:AS-POWERMEDIA (APNIC) lists AS-152698; no IRR database read has it.
AS-SET: missing member	AS139202:AS-POWERMEDIA	AS139202:AS-POWERMEDIA (APNIC) lists AS-DTIIG-139901; no IRR database read has it.
AS-SET: missing member	AS139202:AS-POWERMEDIA	AS139202:AS-POWERMEDIA (APNIC) lists AS138004:AS-PEERING; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: missing member

AS139202:AS-POWERMEDIA

AS139202:AS-POWERMEDIA (APNIC) lists AS-149994; no IRR database read has it.

AS-SET: missing member

AS139202:AS-POWERMEDIA

AS139202:AS-POWERMEDIA (APNIC) lists AS-152698; no IRR database read has it.

AS-SET: missing member

AS139202:AS-POWERMEDIA

AS139202:AS-POWERMEDIA (APNIC) lists AS-DTIIG-139901; no IRR database read has it.

AS-SET: missing member

AS139202:AS-POWERMEDIA

AS139202:AS-POWERMEDIA (APNIC) lists AS138004:AS-PEERING; no IRR database read has it.

Route objects not announced

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


103.139.196.0/23	APNIC	Valid

103.139.196.0/23

APNIC

Valid

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.