bgpreport

Network · data from 2026-11-12

AS216070 rcstechnologies RCS Technologies FZE LLC

Registry name: rcstechnologies RCS Technologies FZE LLC, AE · not in PeeringDB

32IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
0Route objects not announced registered with origin AS216070, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS216070, 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.
5.178.108.0/24 Valid RIR databaseRIPE 672 100% 67
31.77.70.0/24 Valid RIR databaseRIPE 672 100% 67
89.125.21.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.22.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.23.0/24 Valid RIR databaseRIPE 672 100% 67
89.125.215.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.216.0/24 Valid RIR databaseRIPE 672 100% 67
89.125.217.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.218.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.220.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.221.0/24 Valid RIR databaseRIPE 672 100% 66
89.125.222.0/24 Valid RIR databaseRIPE 672 100% 67
136.0.75.0/24 Valid RIR databaseARIN 672 100% 67
144.225.50.0/24 Valid RIR databaseARIN 672 100% 67
144.225.239.0/24 Valid RIR databaseARIN 672 100% 67
153.52.71.0/24 Valid RIR databaseRIPE 672 100% 67
153.52.98.0/24 Valid RIR databaseRIPE 672 100% 67
153.52.104.0/24 Valid RIR databaseRIPE 672 100% 67
153.52.120.0/24 Valid RIR databaseRIPE 672 100% 67
176.126.174.0/24 Valid RIR databaseRIPE 672 100% 67
179.253.161.0/24 Valid RIR databaseRIPE 672 100% 67
179.253.165.0/24 Valid RIR databaseRIPE 672 100% 67
179.253.172.0/24 Valid RIR databaseRIPE 672 100% 67
179.253.178.0/24 Valid RIR databaseRIPE 672 100% 67
179.253.183.0/24 Valid RIR databaseRIPE 672 100% 67
179.253.191.0/24 Valid RIR databaseRIPE 672 100% 67
179.254.113.0/24 Valid RIR databaseRIPE 672 100% 67
201.10.86.0/24 Valid RIR databaseRIPE 672 100% 67
217.9.12.0/24 Valid RIR databaseRIPE 672 100% 67
5.144.183.0/24 Valid RIR databaseRIPE 671 100% 67
5.178.106.0/24 Valid RIR databaseRIPE 671 100% 67
89.125.219.0/24 Valid RIR databaseRIPE 671 100% 68
2a06:2842::/32 Valid RIR databaseRIPE 635 100% 69
2a06:2840::/32 Valid RIR databaseRIPE 634 100% 67
2a06:2841::/32 Valid RIR databaseRIPE 634 100% 67
2a06:2843::/32 Valid RIR databaseRIPE 634 100% 67
2a13:4980::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS216070 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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