bgpreport

Network · data from 2026-11-12

AS48219 ThreeData-AS 3DATA LLC

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48219, 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.217.125.0/24 No ROA RIR databaseRIPE 673 100% 66
91.227.154.0/24 No ROA RIR databaseRIPE 673 100% 66
91.238.227.0/24 No ROA RIR databaseRIPE 673 100% 66
130.49.142.0/24 No ROA RIR databaseRIPE 673 100% 66
141.101.178.0/24 No ROA RIR databaseRIPE 673 100% 66
153.80.186.0/24 No ROA RIR databaseRIPE 673 100% 66
178.170.171.0/24 No ROA RIR databaseRIPE 673 100% 66
178.170.206.0/24 No ROA RIR databaseRIPE 673 100% 66
178.170.237.0/24 No ROA RIR databaseRIPE 673 100% 66
185.2.32.0/24 No ROA RIR databaseRIPE 673 100% 66
185.224.31.0/24 No ROA RIR databaseRIPE 673 100% 66
188.72.75.0/24 No ROA RIR databaseRIPE 673 100% 66
217.78.231.0/24 No ROA RIR databaseRIPE 673 100% 66
37.230.236.0/24 No ROA RIR databaseRIPE 672 100% 66
45.8.108.0/24 No ROA RIR databaseRIPE 672 100% 66
45.8.111.0/24 No ROA RIR databaseRIPE 672 100% 66
46.243.166.0/24 No ROA RIR databaseRIPE 672 100% 66
46.243.167.0/24 No ROA RIR databaseRIPE 672 100% 66
91.216.49.0/24 Valid RIR databaseRIPE 673 100% 66
91.223.137.0/24 Valid RIR databaseRIPE 673 100% 66
141.101.246.0/24 Valid RIR databaseRIPE 673 100% 66
185.2.35.0/24 Valid RIR databaseRIPE 673 100% 66
189.74.105.0/24 Valid RIR databaseRIPE 673 100% 66
37.230.143.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

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

  • ROA: none18
ChangePrefix or setDetailFull-table peers
ROA: none91.217.125.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none91.227.154.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none91.238.227.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none130.49.142.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none141.101.178.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none153.80.186.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none178.170.171.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none178.170.206.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none178.170.237.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none185.2.32.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none185.224.31.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none188.72.75.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none217.78.231.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.673 of 673
ROA: none37.230.236.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.672 of 673
ROA: none45.8.108.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.672 of 673
ROA: none45.8.111.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.672 of 673
ROA: none46.243.166.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.672 of 673
ROA: none46.243.167.0/24No ROA covers it. Add a ROA for AS48219, maxLength 24.672 of 673

Route objects not announced

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