bgpreport

Network · data from 2026-11-12

AS211043 Dedifix

Registry name: Dedifix Dedifix BV, NL · PeeringDB

10IPv4 routes 90.0% RPKI valid · 90.0% 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
2Route objects not announced registered with origin AS211043, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS211043, 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.
89.46.123.0/24 Invalid: origin Other origin only 2 0%low visibility 2
85.203.52.0/24 Valid RIR databaseRIPE 673 100% 67
92.240.150.0/24 Valid RIR databaseRIPE 673 100% 67
185.51.55.0/24 Valid RIR databaseRIPE 673 100% 67
185.102.171.0/24 Valid RIR databaseRIPE 673 100% 67
185.227.34.0/24 Valid RIR databaseRIPE 673 100% 67
185.243.4.0/24 Valid RIR databaseRIPE 673 100% 67
194.31.96.0/24 Valid RIR databaseRIPE 673 100% 67
45.67.98.0/24 Valid RIR databaseRIPE 672 100% 67
46.244.99.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS211043'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.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin89.46.123.0/24ROAs covering it name AS209181, not AS211043. If AS211043 should announce it, add a ROA for AS211043.2 of 673
Route object: none89.46.123.0/24Route objects for it name AS209181. Add a route object with origin AS211043 in the RIR database for the space.2 of 673

Route objects not announced

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

23.230.41.0/24ARIN, RADBValid
178.173.232.0/24RIPEInvalid: origin

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.