bgpreport

Network · data from 2026-11-12

AS41718 CHINA GREAT FIRE WALL NETWORK

Registry name: VITRINATV-AS Vitrina TV LLC, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41718, 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.
193.27.224.0/24 No ROA RIR databaseRIPE 669 99% 67
193.27.225.0/24 No ROA RIR databaseRIPE 669 99% 67
191.44.35.0/24 Valid RIR databaseRIPE 673 100% 66
191.44.34.0/24 Valid RIR databaseRIPE 671 100% 68
194.156.120.0/24 Valid RIR databaseRIPE 671 100% 68
194.156.121.0/24 Valid RIR databaseRIPE 669 99% 67
195.216.153.0/24 Valid RIR databaseRIPE 669 99% 67

AS-SET

AS41718's PeeringDB record names no 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none193.27.224.0/24No ROA covers it. Add a ROA for AS41718, maxLength 24.669 of 673
ROA: none193.27.225.0/24No ROA covers it. Add a ROA for AS41718, maxLength 24.669 of 673

Route objects not announced

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