bgpreport

Network · data from 2026-11-12

AS402899 PTLHL - Prestige

Registry name: PTLHL - Prestige, US · not in PeeringDB

15IPv4 routes 93.3% RPKI valid · 93.3% with a route object
8IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS402899, seen from no peer

Announced routes

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

68.164.48.0/24 Invalid: origin None 1 0%low visibility 1
176.102.171.0/24 Valid Other IRR onlyRADB 672 100% 66
83.245.42.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
179.254.195.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
187.14.133.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
189.30.65.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
187.15.232.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
187.55.10.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
189.12.148.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
189.30.88.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
79.180.18.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
189.12.156.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
199.101.171.0/24 Valid RIR databaseARIN, RADB 667 99% 67
2a09:240::/29 Valid RIR databaseRIPE 635 100% 67
2a10:ed80::/29 Valid RIR databaseRIPE 633 100% 67
2a10:f180::/29 Valid RIR databaseRIPE 633 100% 67
2a12:1300::/29 Valid RIR databaseRIPE 633 100% 69
2a03:f100::/29 Valid RIR databaseRIPE 632 99% 67
2a05:b600::/29 Valid RIR databaseRIPE 632 99% 67
2a09:fe80::/29 Valid RIR databaseRIPE 632 99% 67
2a09:c0::/29 Valid RIR databaseRIPE 631 99% 67
187.14.155.0/24 Valid RIR databaseRADB, RIPE 3 0%low visibility 2
187.15.250.0/24 Valid RIR databaseRADB, RIPE 3 0%low visibility 2

AS-SET

AS402899 isn't in PeeringDB, where networks name their 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 21 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: origin68.164.48.0/24ROAs covering it name AS834, not AS402899. If AS402899 should announce it, add a ROA for AS402899.1 of 673
Route object: none68.164.48.0/24No route object for it. Add a route object with origin AS402899 in the RIR database for the space.1 of 673
Route object: RIR176.102.171.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

13.141.6.0/24RADB, RIPEValid
13.141.10.0/24RADB, RIPEValid
65.86.196.0/24ARIN, RADBValid
69.33.228.0/24ARIN, RADBValid
87.84.20.0/24RADB, RIPEValid
90.96.113.0/24RADB, RIPEValid
152.234.141.0/24RADB, RIPEValid
160.21.149.0/24RADB, RIPEValid
168.199.150.0/24RADB, RIPEValid
177.201.196.0/24RADB, RIPEValid
179.69.113.0/24RADB, RIPEValid
187.15.196.0/24RADB, RIPEValid
187.15.224.0/24RADBInvalid: origin
189.30.68.0/24RADB, RIPEValid
189.30.103.0/24RADB, RIPEValid
200.138.40.0/24RADB, RIPEValid
200.180.173.0/24RADB, RIPEValid
2a10:3240::/29RIPEValid

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.