bgpreport

Network · data from 2026-11-12

AS43959 XTOM-PARK xTom GmbH

Registry name: XTOM-PARK xTom GmbH, DE · not in PeeringDB

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

Announced routes

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

2001:df4:dd80::/48 Valid RIR databaseAPNIC, RADB 633 100% 69
2a06:4fc0::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a06:57c0::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a07:46c0::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a07:e900::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a07:fa00::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0c:ed40::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0d:1fc0::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0d:3640::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0d:4340::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0d:4bc0::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0d:7540::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a0d:de80::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a10:2600::/29 Valid RIR databaseRADB, RIPE 633 100% 69
2a12:9d00::/29 Valid RIR databaseRADB, RIPE 633 100% 69

AS-SET

AS43959 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 24 are in fix.csv.

  • Route object: not announced24

Route objects not announced

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

45.14.64.0/24RADB, RIPEValid
45.14.65.0/24RADB, RIPEValid
45.14.66.0/24RADB, RIPEValid
45.14.67.0/24RADB, RIPEValid
92.60.43.0/24RADBValid
103.19.1.0/24APNICValid
103.121.208.0/24APNICInvalid: origin
103.121.209.0/24APNICInvalid: origin
103.155.232.0/24RADBValid
103.155.233.0/24RADBValid
103.201.128.0/24APNICInvalid: origin
2403:71c0::/48APNICInvalid: origin
2403:71c0:1000::/48APNICInvalid: origin
2403:71c0:3000::/48APNICInvalid: origin
2403:71c0:5000::/48APNICInvalid: origin
2403:71c0:6000::/48APNICInvalid: origin
2403:71c0:7000::/48APNICInvalid: origin
2403:71c0:8000::/48APNICInvalid: origin
2403:71c0:9000::/48APNICInvalid: origin
2403:71c0:ff00::/48APNICInvalid: origin
2a09:7::/36RIPEValid
2a09:7::/48RADBValid
2a0d:c7c1::/32RADBValid
2a0f:5701:fe11::/48ALTDB, RADB, RIPEValid

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.