bgpreport

Network · data from 2026-11-12

AS16262 DATACHEAP-LLC-AS Datacheap LLC

Registry name: DATACHEAP-LLC-AS Datacheap LLC, RU · not in PeeringDB

11IPv4 routes 54.5% RPKI valid · 81.8% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS16262, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16262, 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.
45.10.174.6/32 No ROA Nonecovered by 45.10.174.0/24 6 1%low visibility 4
45.10.174.10/32 No ROA Nonecovered by 45.10.174.0/24 6 1%low visibility 4
45.10.174.0/24 No ROA RIR databaseRIPE 672 100% 67
45.150.238.0/24 No ROA RIR databaseRIPE 672 100% 67
45.150.239.0/24 No ROA RIR databaseRIPE 672 100% 67
87.251.73.0/24 Valid RIR databaseRIPE 673 100% 67
192.162.240.0/21 Valid RIR databaseRIPE 673 100% 67
195.211.100.0/22 Valid RIR databaseRIPE 673 100% 67
46.8.52.0/24 Valid RIR databaseRIPE 672 100% 67
46.8.53.0/24 Valid RIR databaseRIPE 672 100% 67
46.8.153.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS16262 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 19 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none45.10.174.6/32No ROA covers it. Add a ROA for AS16262, maxLength 32.6 of 673
Route object: none45.10.174.6/32No route object for it. A route object for 45.10.174.0/24 with origin AS16262 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS16262 in the RIR database for the space.6 of 673
ROA: none45.10.174.10/32No ROA covers it. Add a ROA for AS16262, maxLength 32.6 of 673
Route object: none45.10.174.10/32No route object for it. A route object for 45.10.174.0/24 with origin AS16262 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS16262 in the RIR database for the space.6 of 673
ROA: none45.10.174.0/24No ROA covers it. Add a ROA for AS16262, maxLength 24.672 of 673
ROA: none45.150.238.0/24No ROA covers it. Add a ROA for AS16262, maxLength 24.672 of 673
ROA: none45.150.239.0/24No ROA covers it. Add a ROA for AS16262, maxLength 24.672 of 673

Route objects not announced

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

192.162.240.0/24RIPEInvalid: maxLength
192.162.241.0/24RIPEInvalid: maxLength
192.162.242.0/24RIPEInvalid: maxLength
192.162.243.0/24RIPEInvalid: maxLength
192.162.244.0/24RIPEInvalid: maxLength
192.162.245.0/24RIPEInvalid: maxLength
192.162.246.0/24RIPEInvalid: maxLength
192.162.247.0/24RIPEInvalid: maxLength
195.211.100.0/24RIPEInvalid: maxLength
195.211.101.0/24RIPEInvalid: maxLength
195.211.102.0/24RIPEInvalid: maxLength
195.211.103.0/24RIPEInvalid: maxLength

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.