bgpreport

Network · data from 2026-11-12

AS11527 X0R - Xproxies

Registry name: X0R - Xproxies, US · not in PeeringDB

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

Announced routes

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

23.132.244.0/24 No ROA RIR databaseARIN 668 99% 68
2604:120::/32 No ROA RIR databaseARIN 634 100% 67

AS-SET

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

  • ROA: none2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none23.132.244.0/24No ROA covers it. Add a ROA for AS11527, maxLength 24.668 of 673
ROA: none2604:120::/32No ROA covers it. Add a ROA for AS11527, maxLength 32.634 of 636

Route objects not announced

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

23.132.84.0/24ARINNo ROA
23.143.16.0/24ARINNo ROA
134.195.104.0/22ARINNo ROA
155.103.96.0/22ARINNo ROA
155.103.96.0/24ARINNo ROA
155.103.97.0/24ARINNo ROA
155.103.98.0/24ARINNo ROA
155.103.99.0/24ARINNo ROA
199.45.24.0/22ARINNo ROA
199.45.24.0/24ARINNo ROA
199.45.25.0/24ARINNo ROA
199.45.26.0/24ARINNo ROA
199.45.27.0/24ARINNo ROA
2605:6f40::/32ARINNo ROA
2607:ef40::/32ARINNo 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.