bgpreport

Network · data from 2026-11-12

AS51299 RGTN Redworks B.V.

Registry name: RGTN Redworks B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51299, 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.
2607:6fc0::/32 No ROA None 636 100% 69
131.143.173.0/24 Valid RIR databaseARIN 673 100% 66
185.158.144.0/22 Valid RIR databaseRIPE 673 100% 67
185.158.144.0/23 Valid RIR databaseRIPE 673 100% 67
185.158.146.0/23 Valid RIR databaseRIPE 673 100% 67
194.61.85.0/24 Valid RIR databaseARIN 673 100% 66
194.61.87.0/24 Valid RIR databaseRIPE 673 100% 67
2a07:ae00::/32 Valid RIR databaseRIPE 635 100% 67
2a07:ae01::/32 Valid RIR databaseRIPE 635 100% 67
2a07:ae00::/31 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2607:6fc0::/32No ROA covers it. Add a ROA for AS51299, maxLength 32.636 of 636
Route object: none2607:6fc0::/32No route object for it. Add a route object with origin AS51299 in the RIR database for the space.636 of 636

Route objects not announced

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

199.5.173.0/24ARINValid
2a07:ae00::/29RIPENo ROA

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.