bgpreport

Network · data from 2026-11-12

AS205184 Adjust GmbH fra14

Registry name: ADJUST-DE Adjust GmbH, DE · PeeringDB

6IPv4 routes 100.0% RPKI valid · 83.3% with a route object
3IPv6 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
3Route objects not announced registered with origin AS205184, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS205184, 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.230.38.0/24 Valid None 671 100% 68
23.19.48.0/22 Valid RIR databaseRIPE 671 100% 68
185.84.200.0/23 Valid RIR databaseRIPE 670 100% 68
185.129.40.0/22 Valid RIR databaseRIPE 670 100% 68
185.230.36.0/23 Valid RIR databaseRIPE 670 100% 68
2a0b:14c0:6::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:14c0:1::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:14c0::/48 Valid RIR databaseRIPE 432 68% 66
185.151.204.0/24 Valid RIR databaseRIPE 426 63% 66

AS-SET

AS205184'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 4 are in fix.csv.

  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none185.230.38.0/24No route object for it. Add a route object with origin AS205184 in the RIR database for the space.671 of 673

Route objects not announced

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

173.208.60.0/23ARINValid
185.151.204.0/22RIPENo ROA
2001:470:443::/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.