bgpreport

Network · data from 2026-11-12

AS50214 QWARTA QWARTA LLC

Registry name: QWARTA QWARTA LLC, RU · not in PeeringDB

14IPv4 routes 57.1% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
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
4Route objects not announced registered with origin AS50214, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50214, 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.

88.151.114.0/24 No ROA RIR databaseRIPE 673 100% 67
95.183.36.0/22 No ROA RIR databaseRIPE 673 100% 67
193.3.184.0/24 No ROA RIR databaseRIPE 673 100% 67
193.232.121.0/24 No ROA RIR databaseRIPE 673 100% 67
195.42.122.0/23 No ROA RIR databaseRIPE 673 100% 67
91.198.211.0/24 No ROA RIR databaseRIPE 668 99% 67
2a11:5bc0::/29 No ROA RIR databaseRIPE 634 100% 69
95.181.171.0/24 Valid RIR databaseRIPE 673 100% 67
185.12.124.0/24 Valid RIR databaseRIPE 673 100% 67
185.12.125.0/24 Valid RIR databaseRIPE 673 100% 67
185.12.126.0/24 Valid RIR databaseRIPE 673 100% 67
185.12.127.0/24 Valid RIR databaseRIPE 673 100% 67
194.226.139.0/24 Valid RIR databaseRIPE 673 100% 67
95.181.169.0/24 Valid RIR databaseRIPE 672 100% 67
95.181.154.0/24 Valid RIR databaseRIPE 668 99% 67

AS-SET

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

  • ROA: none7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none88.151.114.0/24No ROA covers it. Add a ROA for AS50214, maxLength 24.673 of 673
ROA: none95.183.36.0/22No ROA covers it. Add a ROA for AS50214, maxLength 22.673 of 673
ROA: none193.3.184.0/24No ROA covers it. Add a ROA for AS50214, maxLength 24.673 of 673
ROA: none193.232.121.0/24No ROA covers it. Add a ROA for AS50214, maxLength 24.673 of 673
ROA: none195.42.122.0/23No ROA covers it. Add a ROA for AS50214, maxLength 23.673 of 673
ROA: none91.198.211.0/24No ROA covers it. Add a ROA for AS50214, maxLength 24.668 of 673
ROA: none2a11:5bc0::/29No ROA covers it. Add a ROA for AS50214, maxLength 29.634 of 636

Route objects not announced

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

185.12.124.0/22RIPENo ROA
185.233.82.0/23RIPENo ROA
2a02:eb00::/29RIPENo ROA
2a11:5bc0::/48RIPENo ROA

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.