bgpreport

Network · data from 2026-11-12

AS219275 ProjectX TA Consulting & Services GmbH

Registry name: ProjectX TA Consulting & Services GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219275, 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.
153.52.80.0/24 Invalid: origin Other origin only 35 5%low visibility 20
13.143.200.0/24 Valid RIR databaseRIPE 673 100% 67
153.76.218.0/24 Valid RIR databaseRIPE 673 100% 67
62.192.152.0/24 Valid RIR databaseRIPE 669 99% 67
87.58.221.0/24 Valid RIR databaseRIPE 669 99% 67
194.152.137.0/24 Valid RIR databaseRIPE 669 99% 67

AS-SET

AS219275 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin153.52.80.0/24ROAs covering it name AS219429, not AS219275. If AS219275 should announce it, add a ROA for AS219275.35 of 673
Route object: none153.52.80.0/24Route objects for it name AS219429. Add a route object with origin AS219275 in the RIR database for the space.35 of 673

Route objects not announced

Every route object with origin AS219275 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.