bgpreport

Network · data from 2026-11-12

AS136030 Redtone Telecommunications Pakistan

Registry name: REDTONE-AS-AP - Redtone Telecommunications Pakistan (Private) Limited, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136030, 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.
204.157.158.0/24 No ROA Other IRR onlyRADB 672 100% 67
206.42.122.0/24 No ROA Other IRR onlyRADB 672 100% 67
206.42.123.0/24 No ROA Other IRR onlyRADB 672 100% 67
206.42.125.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.125.71.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
43.225.99.0/24 Valid RIR databaseAPNIC 673 100% 67
103.235.78.0/24 Valid RIR databaseAPNIC 673 100% 67
180.149.215.0/24 Valid RIR databaseAPNIC 673 100% 66
180.149.216.0/24 Valid RIR databaseAPNIC 673 100% 66
180.149.217.0/24 Valid RIR databaseAPNIC 673 100% 66
43.225.98.0/24 Valid RIR databaseAPNIC 672 100% 67
103.85.128.0/24 Valid RIR databaseAPNIC 672 100% 67
103.104.192.0/24 Valid RIR databaseAPNIC 672 100% 67
103.104.193.0/24 Valid RIR databaseAPNIC 672 100% 67
103.104.194.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.104.195.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.36.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.37.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.38.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.127.39.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
160.22.140.0/24 Valid RIR databaseAPNIC 672 100% 67
180.149.214.0/24 Valid RIR databaseAPNIC 672 100% 66
180.149.218.0/24 Valid RIR databaseAPNIC 672 100% 66
180.149.220.0/24 Valid RIR databaseAPNIC 672 100% 66
180.149.221.0/24 Valid RIR databaseAPNIC 672 100% 66
180.149.222.0/24 Valid RIR databaseAPNIC 672 100% 66
103.85.131.0/24 Valid RIR databaseAPNIC 671 100% 67
103.255.150.0/24 Valid RIR databaseAPNIC 670 100% 66
2404:1940:2000::/36 Valid RIR databaseAPNIC 630 99% 67
2404:1940:3000::/36 Valid RIR databaseAPNIC 630 99% 67
103.165.176.0/24 Valid RIR databaseAPNIC 5 1%low visibility 4
103.101.232.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS136030's PeeringDB record names no AS-SET.

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

  • ROA: none5
  • Route object: RIR4
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none204.157.158.0/24No ROA covers it. Add a ROA for AS136030, maxLength 24.672 of 673
Route object: RIR204.157.158.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.42.122.0/24No ROA covers it. Add a ROA for AS136030, maxLength 24.672 of 673
Route object: RIR206.42.122.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.42.123.0/24No ROA covers it. Add a ROA for AS136030, maxLength 24.672 of 673
Route object: RIR206.42.123.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.42.125.0/24No ROA covers it. Add a ROA for AS136030, maxLength 24.671 of 673
Route object: RIR206.42.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.125.71.0/24No ROA covers it. Add a ROA for AS136030, maxLength 24.672 of 673

Route objects not announced

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

38.69.53.0/24ARINNo ROA
103.104.192.0/22APNIC, RADBValid
103.104.192.0/23APNICValid
103.104.194.0/23APNICValid
103.125.70.0/24RADBNo ROA
103.125.240.0/22RADBNo ROA
103.127.36.0/22APNICValid
115.167.50.0/24RADBNo ROA
115.167.64.0/24RADBNo ROA
115.167.65.0/24RADBNo ROA
115.167.66.0/24RADBNo ROA
115.167.66.48/29RADBNo ROA
115.167.66.160/29RADBNo ROA
115.167.66.168/29RADBNo ROA
115.167.67.0/24RADBNo ROA
115.167.124.0/24RADBNo ROA
139.190.30.0/24RADBNo ROA
139.190.235.0/24RADBNo ROA
204.157.155.0/24RADBNo ROA
204.157.159.0/24RADBNo ROA
2404:1940::/32APNIC, RADBValid

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.