bgpreport

Network · data from 2026-11-12

AS53661 PPI - PPI

Registry name: PPI - PPI, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53661, 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.
199.59.184.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.185.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.186.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.187.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.188.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.189.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.190.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.64.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.65.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.66.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.67.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.69.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.70.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.71.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
199.59.191.0/24 No ROA RIR databaseARIN, RADB 669 99% 68

AS-SET

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

  • ROA: none15
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none199.59.184.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.185.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.186.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.187.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.188.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.189.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.190.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.64.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.65.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.66.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.67.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.69.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.70.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.115.71.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.671 of 673
ROA: none199.59.191.0/24No ROA covers it. Add a ROA for AS53661, maxLength 24.669 of 673

Route objects not announced

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

199.59.184.0/21ARINNo ROA
199.115.64.0/21ARIN, RADBNo ROA
199.115.68.0/24ARIN, RADBNo ROA
2620:45::/48ARINNo ROA

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.