bgpreport

Network · data from 2026-11-12

AS60380 PIXELX-AS Michael Rottmann trading as Pixel X e.K.

Registry name: PIXELX-AS Michael Rottmann trading as Pixel X e.K., DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60380, 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.
185.141.100.0/22 No ROA RIR databaseRIPE 673 100% 66
195.3.248.0/22 No ROA RIR databaseRIPE 673 100% 66
2a0d:aa80::/29 No ROA RIR databaseRIPE 634 100% 67
81.209.248.0/21 Valid RIR databaseRIPE 673 100% 66
83.125.6.0/23 Valid RIR databaseRIPE 673 100% 66
83.133.240.0/20 Valid RIR databaseRIPE 673 100% 66
80.86.184.0/24 Valid RIR databaseRIPE 672 100% 66
80.86.188.0/23 Valid RIR databaseRIPE 672 100% 66
83.133.178.0/23 Valid RIR databaseRIPE 672 100% 66
2001:7f0:3000::/46 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS60380 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none185.141.100.0/22No ROA covers it. Add a ROA for AS60380, maxLength 22.673 of 673
ROA: none195.3.248.0/22No ROA covers it. Add a ROA for AS60380, maxLength 22.673 of 673
ROA: none2a0d:aa80::/29No ROA covers it. Add a ROA for AS60380, maxLength 29.634 of 636

Route objects not announced

Every route object with origin AS60380 is announced.

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.