bgpreport

Network · data from 2026-11-12

AS204765 PG8GLOBAL PG8 Global LLC

Registry name: PG8GLOBAL PG8 Global LLC, US · not in PeeringDB

38IPv4 routes 65.8% RPKI valid · 65.8% with a route object
0IPv6 routes
12RPKI invalid 12 origin · 0 maxLength
1No ROA 13 with no route object for this origin
13Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS204765, seen from no peer

Announced routes

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

141.140.15.0/24 Invalid: origin Other origin only 13 2%low visibility 9
162.141.91.0/24 Invalid: origin Other origin only 13 2%low visibility 9
167.148.222.0/24 Invalid: origin Other origin only 13 2%low visibility 9
167.148.2.0/24 Invalid: origin None 9 1%low visibility 5
167.148.122.0/24 Invalid: origin Other origin only 9 1%low visibility 5
172.98.211.0/24 Invalid: origin Other origin only 9 1%low visibility 5
64.81.178.0/24 Invalid: origin Other origin only 8 1%low visibility 6
136.0.107.0/24 Invalid: origin Other origin only 8 1%low visibility 6
64.83.76.0/24 Invalid: origin Other origin only 6 1%low visibility 4
162.141.153.0/24 Invalid: origin Other origin only 6 1%low visibility 4
66.235.96.0/22 Invalid: origin Other origin only 3 0%low visibility 3
148.135.171.0/24 Invalid: origin Other origin only 2 0%low visibility 2
211.149.44.0/22 No ROA Other origin only 3 0%low visibility 3
64.69.127.0/24 Valid RIR databaseARIN, RADB 667 99% 67
64.204.243.0/24 Valid RIR databaseARIN, RADB 667 99% 67
67.227.99.0/24 Valid RIR databaseARIN, RADB 667 99% 67
68.166.210.0/24 Valid RIR databaseARIN, RADB 667 99% 67
95.135.180.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
96.43.103.0/24 Valid RIR databaseARIN, RADB 667 99% 67
101.232.192.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.196.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.208.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.216.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.228.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.244.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.248.0/22 Valid RIR databaseAPNIC 667 99% 67
101.232.252.0/22 Valid RIR databaseAPNIC 667 99% 67
143.14.252.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
162.141.139.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
167.148.68.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
191.44.31.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
211.149.40.0/22 Valid RIR databaseAPNIC 667 99% 67
211.149.56.0/22 Valid RIR databaseAPNIC 667 99% 67
211.149.60.0/22 Valid RIR databaseAPNIC 667 99% 67
211.149.72.0/22 Valid RIR databaseAPNIC 667 99% 67
211.149.76.0/22 Valid RIR databaseAPNIC 667 99% 67
211.149.88.0/22 Valid RIR databaseAPNIC 667 99% 67
211.149.92.0/22 Valid RIR databaseAPNIC 667 99% 67

AS-SET

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

  • ROA: origin12
  • ROA: none1
  • Route object: none13
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin141.140.15.0/24ROAs covering it name AS834, AS53356, not AS204765. If AS204765 should announce it, add a ROA for AS204765.13 of 673
Route object: none141.140.15.0/24Route objects for it name AS834. Add a route object with origin AS204765 in the RIR database for the space.13 of 673
ROA: origin162.141.91.0/24ROAs covering it name AS147281, not AS204765. If AS204765 should announce it, add a ROA for AS204765.13 of 673
Route object: none162.141.91.0/24Route objects for it name AS147281. Add a route object with origin AS204765 in the RIR database for the space.13 of 673
ROA: origin167.148.222.0/24ROAs covering it name AS64457, not AS204765. If AS204765 should announce it, add a ROA for AS204765.13 of 673
Route object: none167.148.222.0/24Route objects for it name AS64457. Add a route object with origin AS204765 in the RIR database for the space.13 of 673
ROA: origin167.148.2.0/24ROAs covering it name AS834, not AS204765. If AS204765 should announce it, add a ROA for AS204765.9 of 673
Route object: none167.148.2.0/24No route object for it. Add a route object with origin AS204765 in the RIR database for the space.9 of 673
ROA: origin167.148.122.0/24ROAs covering it name AS29802, not AS204765. If AS204765 should announce it, add a ROA for AS204765.9 of 673
Route object: none167.148.122.0/24Route objects for it name AS29802. Add a route object with origin AS204765 in the RIR database for the space.9 of 673
ROA: origin172.98.211.0/24ROAs covering it name AS834, not AS204765. If AS204765 should announce it, add a ROA for AS204765.9 of 673
Route object: none172.98.211.0/24Route objects for it name AS834. Add a route object with origin AS204765 in the RIR database for the space.9 of 673
ROA: origin64.81.178.0/24ROAs covering it name AS26407, not AS204765. If AS204765 should announce it, add a ROA for AS204765.8 of 673
Route object: none64.81.178.0/24Route objects for it name AS26407. Add a route object with origin AS204765 in the RIR database for the space.8 of 673
ROA: origin136.0.107.0/24ROAs covering it name AS3561, not AS204765. If AS204765 should announce it, add a ROA for AS204765.8 of 673
Route object: none136.0.107.0/24Route objects for it name AS3561. Add a route object with origin AS204765 in the RIR database for the space.8 of 673
ROA: origin64.83.76.0/24ROAs covering it name AS21769, AS147281, not AS204765. If AS204765 should announce it, add a ROA for AS204765.6 of 673
Route object: none64.83.76.0/24Route objects for it name AS147281. Add a route object with origin AS204765 in the RIR database for the space.6 of 673
ROA: origin162.141.153.0/24ROAs covering it name AS153786, not AS204765. If AS204765 should announce it, add a ROA for AS204765.6 of 673
Route object: none162.141.153.0/24Route objects for it name AS153786. Add a route object with origin AS204765 in the RIR database for the space.6 of 673
ROA: origin66.235.96.0/22ROAs covering it name AS5650, not AS204765. If AS204765 should announce it, add a ROA for AS204765.3 of 673
Route object: none66.235.96.0/22Route objects for it name AS5650. Add a route object with origin AS204765 in the RIR database for the space.3 of 673
ROA: origin148.135.171.0/24ROAs covering it name AS212669, not AS204765. If AS204765 should announce it, add a ROA for AS204765.2 of 673
Route object: none148.135.171.0/24Route objects for it name AS212669. Add a route object with origin AS204765 in the RIR database for the space.2 of 673
ROA: none211.149.44.0/22No ROA covers it. Add a ROA for AS204765, maxLength 22.3 of 673
Route object: none211.149.44.0/22Route objects for it name AS35913. Add a route object with origin AS204765 in the RIR database for the space.3 of 673

Route objects not announced

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

123.98.68.0/22APNICNo ROA
123.98.72.0/22APNICNo ROA
2a0c:b641:8b0::/44RIPEValid

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.