bgpreport

Network · data from 2026-11-12

AS211407 PT Perwira Media Solusi

Registry name: AS_Perwira_Media PT Perwira Media Solusi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211407, 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.

191.222.34.0/24 Invalid: origin None 110 16% 50
191.222.35.0/24 Invalid: origin None 110 16% 50
151.244.238.0/24 Invalid: origin None 16 2%low visibility 13
31.56.78.213/32 Invalid: maxLength Nonecovered by 31.56.78.0/24 1 0%low visibility 1
41.216.186.87/32 Invalid: maxLength Nonecovered by 41.216.186.0/24 1 0%low visibility 1
41.216.186.222/32 Invalid: maxLength Nonecovered by 41.216.186.0/24 1 0%low visibility 1
41.216.186.246/32 Invalid: maxLength Nonecovered by 41.216.186.0/24 1 0%low visibility 1
41.216.190.100/32 Invalid: maxLength Nonecovered by 41.216.190.0/24 1 0%low visibility 1
41.216.190.122/32 Invalid: maxLength Nonecovered by 41.216.190.0/24 1 0%low visibility 1
103.118.175.0/24 Valid Other IRR onlyRADB 670 100% 67
5.181.178.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
31.56.78.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
103.195.65.0/24 Valid RIR databaseAPNIC 673 100% 69
143.20.10.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
151.243.30.0/24 Valid RIR databaseRADB, RIPE 672 100% 68
151.244.119.0/24 Valid RIR databaseRADB, RIPE 672 100% 68
31.57.178.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
31.58.158.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
82.39.222.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
82.41.42.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
141.11.241.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
151.242.116.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
191.101.190.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
38.109.212.0/24 Valid RIR databaseARIN 669 99% 67
45.149.93.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
45.158.10.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
41.216.186.0/24 Valid RIR databaseAFRINIC, RADB 662 98% 69
41.216.190.0/24 Valid RIR databaseAFRINIC 662 98% 69
41.216.191.0/24 Valid RIR databaseAFRINIC 662 98% 69

AS-SET

PeeringDB's irr_as_set for AS211407: AS211407:AS-PERWIRA. 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 (AS211407 isn't in the set, or no route object for AS211407 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 objectsAS211407 in itNot covered
AS211407:AS-PERWIRA RIPE 134124 Yes 9

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

  • ROA: origin3
  • ROA: maxLength6
  • Route object: none9
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin191.222.34.0/24ROAs covering it name AS141968, not AS211407. If AS211407 should announce it, add a ROA for AS211407.110 of 673
Route object: none191.222.34.0/24No route object for it. Add a route object with origin AS211407 in the RIR database for the space.110 of 673
ROA: origin191.222.35.0/24ROAs covering it name AS141968, not AS211407. If AS211407 should announce it, add a ROA for AS211407.110 of 673
Route object: none191.222.35.0/24No route object for it. Add a route object with origin AS211407 in the RIR database for the space.110 of 673
ROA: origin151.244.238.0/24ROAs covering it name AS834, AS199925, not AS211407. If AS211407 should announce it, add a ROA for AS211407.16 of 673
Route object: none151.244.238.0/24No route object for it. Add a route object with origin AS211407 in the RIR database for the space.16 of 673
ROA: maxLength31.56.78.213/32ROA 31.56.78.0/24 AS211407 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.56.78.213/32.1 of 673
Route object: none31.56.78.213/32No route object for it. A route object for 31.56.78.0/24 with origin AS211407 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211407 in the RIR database for the space.1 of 673
ROA: maxLength41.216.186.87/32ROA 41.216.186.0/24 AS211407 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 41.216.186.87/32.1 of 673
Route object: none41.216.186.87/32No route object for it. A route object for 41.216.186.0/24 with origin AS211407 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211407 in the RIR database for the space.1 of 673
ROA: maxLength41.216.186.222/32ROA 41.216.186.0/24 AS211407 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 41.216.186.222/32.1 of 673
Route object: none41.216.186.222/32No route object for it. A route object for 41.216.186.0/24 with origin AS211407 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211407 in the RIR database for the space.1 of 673
ROA: maxLength41.216.186.246/32ROA 41.216.186.0/24 AS211407 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 41.216.186.246/32.1 of 673
Route object: none41.216.186.246/32No route object for it. A route object for 41.216.186.0/24 with origin AS211407 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211407 in the RIR database for the space.1 of 673
ROA: maxLength41.216.190.100/32ROA 41.216.190.0/24 AS211407 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 41.216.190.100/32.1 of 673
Route object: none41.216.190.100/32No route object for it. A route object for 41.216.190.0/24 with origin AS211407 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211407 in the RIR database for the space.1 of 673
ROA: maxLength41.216.190.122/32ROA 41.216.190.0/24 AS211407 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 41.216.190.122/32.1 of 673
Route object: none41.216.190.122/32No route object for it. A route object for 41.216.190.0/24 with origin AS211407 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211407 in the RIR database for the space.1 of 673
Route object: RIR103.118.175.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

2602:fac2:12::/48ARINValid
2602:fac2:13::/48ARINValid
2a0a:6040:1200::/40RIPEValid

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.