bgpreport

Network · data from 2026-11-12

AS51722 PIXOOF TEKNOLOJI ANONIM SIRKETI

Registry name: AS-PIXOOF PIXOOF TEKNOLOJI ANONIM SIRKETI, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51722, 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.
5.180.45.0/24 Valid None 671 100% 67
31.40.196.0/24 Valid RIR databaseRIPE 671 100% 67
62.3.12.0/24 Valid RIR databaseRIPE 671 100% 67
94.131.108.0/24 Valid RIR databaseRIPE 671 100% 67
94.131.123.0/24 Valid RIR databaseRIPE 671 100% 67
103.231.75.0/24 Valid RIR databaseRIPE 671 100% 67
131.222.220.0/24 Valid RIR databaseRIPE 671 100% 67
153.56.180.0/24 Valid RIR databaseRIPE 671 100% 67
185.153.182.0/24 Valid RIR databaseRIPE 671 100% 67
185.234.66.0/24 Valid RIR databaseRIPE 671 100% 67
193.46.56.0/24 Valid RIR databaseRIPE 671 100% 67
194.55.136.0/24 Valid RIR databaseRIPE 671 100% 67
195.85.201.0/24 Valid RIR databaseRIPE 671 100% 67
45.12.143.0/24 Valid RIR databaseRIPE 670 100% 67
45.89.52.0/24 Valid RIR databaseRIPE 670 100% 67
78.135.73.0/24 Valid RIR databaseRIPE 670 100% 67
153.56.211.0/24 Valid RIR databaseRIPE 669 99% 67
153.52.129.0/24 Valid RIR databaseRIPE 653 97% 67
153.52.130.0/24 Valid RIR databaseRIPE 653 97% 67
45.136.5.0/24 Valid RIR databaseRIPE 644 96% 67
2a0e:36c6:2000::/48 Valid RIR databaseRIPE 634 100% 67
2a03:f7c0::/29 Valid RIR databaseRIPE 633 100% 67
2a06:ddc0::/29 Valid RIR databaseRIPE 633 100% 67
2a0b:7780::/29 Valid RIR databaseRIPE 633 100% 67
2a0b:da00::/29 Valid RIR databaseRIPE 633 100% 67
2a0b:e9c0::/29 Valid RIR databaseRIPE 633 100% 67
2a0c:5c0::/29 Valid RIR databaseRIPE 633 100% 67
2a0c:77c0::/29 Valid RIR databaseRIPE 633 100% 67
2a0c:aa40::/29 Valid RIR databaseRIPE 633 100% 67
2a0d:2dc0::/29 Valid RIR databaseRIPE 633 100% 67
2a0d:3880::/29 Valid RIR databaseRIPE 633 100% 67
2a0a:37c1::/32 Valid RIR databaseRIPE 631 99% 67

AS-SET

AS51722'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 11 are in fix.csv.

  • Route object: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none5.180.45.0/24No route object for it. Add a route object with origin AS51722 in the RIR database for the space.671 of 673

Route objects not announced

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

155.103.70.0/24ARINValid
155.103.71.0/24ARINValid
194.116.236.0/24RIPEValid
195.85.205.0/24RIPEValid
2602:fa5d::/48ARINValid
2602:fa5d:6::/48ARINValid
2602:fa5d:7::/48ARINValid
2602:fa5d:8::/48ARINValid
2602:fa5d:9::/48ARINValid
2602:fa5d:10::/48ARINValid

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.