bgpreport

Network · data from 2026-11-12

AS62010 ThreeDATA-AS 3DATA LLC

Registry name: ThreeDATA-AS 3DATA LLC, RU · not in PeeringDB

8IPv4 routes 12.5% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS62010, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62010, 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.
91.208.136.0/24 No ROA RIR databaseRIPE 673 100% 66
141.101.239.0/24 No ROA RIR databaseRIPE 673 100% 66
178.170.166.0/24 No ROA RIR databaseRIPE 673 100% 66
178.170.234.0/24 No ROA RIR databaseRIPE 673 100% 66
188.72.78.0/24 No ROA RIR databaseRIPE 673 100% 66
195.128.158.0/24 No ROA RIR databaseRIPE 673 100% 66
45.8.110.0/24 No ROA RIR databaseRIPE 672 100% 66
46.243.174.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

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

  • ROA: none7
ChangePrefix or setDetailFull-table peers
ROA: none91.208.136.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.673 of 673
ROA: none141.101.239.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.673 of 673
ROA: none178.170.166.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.673 of 673
ROA: none178.170.234.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.673 of 673
ROA: none188.72.78.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.673 of 673
ROA: none195.128.158.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.673 of 673
ROA: none45.8.110.0/24No ROA covers it. Add a ROA for AS62010, maxLength 24.672 of 673

Route objects not announced

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